Leaderboard

No, it doesn't: https://gist.github.com/wojteklu/73c6914cc446146b8b533c0988cf8d29

Surely I want. I just don't want to implement things that may be valuable to a single person in a special situation. There are way more things to implement that most likely bring benefit to a lot of people in several situations. My time for MMX is limited and I have to take care for what I spend it. Note that I already took this under consideration: Regarding your requests: This would only work on Forms and Datamodules. Frames and all other classes don't have such a global variable. Given that many people suggest to get rid of these global variables, it would be counterproductive to encourage their usage. Besides that this point is somewhat moot given my response to 1. Moving fields from private to public is not something that I would do without asking for consent, which will add some more user interaction to the process. It is easier to select the relevant field(s) in the class and move them to public with the available tools (like selecting public in the visibility dropdown). This all does not even tackle the fact that the resulting code shown is anything but clean.

That is why I always STRONGLY recommend to buy the source code with any third party library/component you use and to ONLY use the source code and not a single pre-built item. Rebuild what you need for your application, add a project for that purpose to your application project group. When a new Delphi release comes, most of the time a simple recompile is enough. This include the component package projects. The most common change to the source code is to add a simple conditional compilation related to compiler or runtime version. When you have full source code, you don't depend on component vendor when a new Delphi is released.

I would like to throw in a variation of this scheme. Instead of Postfixes for units I suggest separate folders named like the platform, similar (well, almost) to the IDE doing it with the library search paths. Adding a simple search path .\$(Platform) to the project may be sufficient. The platform specific units are named all the same but reside in their platform folders. Before anyone claims that this prohibits to include these units to the project: You cannot do this with the postfix units either. (Well, you could by IFDEFing the DPR, but this is strongly discouraged. You definitely cannot trick the dproj file for that.)

Switch to VirtualBox perhaps?

Hello all, this question isn't strictly Delphi related but rather Windows 11 / VMWare Workstation related. I develop under Windows 10 X64 in a VMWare virtual machine. I'd like to migrate this VM to Windows 11 but there are a few things that currently make this unfeasible IMHO: - before adding a virtual TPM module, VMWare insists on encrypting all virtual hard drives (*.vmdk files) of the VM. - The encryption key contains information of the host machine. The drives will only decrypt on the same host machine. - So if my notebook dies, I'm basically scr##ed because the VM won't run anywhere else. That's totally unacceptible to me. The whole purpose of virtualization is having virtual hardware so the VM's are independent of the host hardware and its life span. A backup of a VM shouldn't be worthless if my hardware breaks! I currently have VM's that were created on at least 3 different machines and they still run fine, thanks to a vmx entry uuid.action= "keep" that tells VMWare to maintain the machine identity even if the VM is moved to a different machine. So... What gives? Is there a viable workaround for this problem? I know about the undocumented managedvm.autoAddVTPM="software" vmx entry but let me warn you, that has dire side effects: instead of encrypting the vmdk files as a whole it will just encrypt the header area of the vmdk files. That is even worse because you can't undo it - the decryption password isn't revealed. And it's not documented if this header encryption is machine dependent or not.

Embarcadero produces patches for the most current version. If you own that version, you get the patch whether your subscription is current or not. Once the next full release happens though (roughly every 12-18 months) the prior release is extremely unlikely to ever get another patch of any sort. This isn't an official statement and I don't represent Embarcadero. It's just an observation of how they've behaved in the past.

For posting a draft message to GMail I don't need any JSON. I can just post the complete mail (eml-format) to https://www.googleapis.com/upload/gmail/v1/users/<email-adres>/drafts. You do need to set the header Authorization: Bearer with the correct access_token. Ps. My MimeType (with Synapse) is message/rfc822 and accept is application/json. I don't see that in your code. Small snippet from my code (as I said with Synapse). The CreatePlainEML creates a mail message which is compatible with Outlook Express and Thunderbird (I believe this is the rfc822 e-mail standard). With TMimemess and multiple TMimepart parts followed by the TMememess.EncodeMessage-function from Synapse. So there shouldn't be any need for posting JSON (only retrieving the result as JSON). I don't think TIdMessage creates a much different text but I'm not sure.

No.

Probably (no one) understands your question.

The hard thing with a new environment, eg: Sydney vs Alexandria, is to move all 3rd parties libraries (often to re-buy), but overall learn workaround on always present IDE issues. The time to discover a problem with an IDE and tool-chain and learn the right workarounds to continue to work is a long activity. Back from new created file project to old, in case of very critical issues are a very waste of time.

If you're planning on deploying iOS apps to the App Store, you will need at least macOS 10.15 so that you can use Xcode 12, the minimum required for deploying apps to the App Store. From April next year, this will change to Xcode 13, which requires Big Sur 11.3.

How would you like to have Ctrl-X - <select another tab> - Ctrl-V more comfortable?

I have updated the demo. The demo now includes saving and loading refresh tokens, as well as checking for expired access_tokens and refreshing them with the refresh_token. Have a look at https://github.com/geoffsmith82/GmailAuthSMTP/ Geoffrey