Leaderboard

Personally, I see no reason to add more options to obfuscate my code. I can do well enough with goto and with when I need to scratch that itch. And when I really want to spice things up, there is always absolute.

Yes, but imagine someone with 200% display scale with a magnifying glass trying to adjust something on a form because the form is half the size.

I am inclined to give some latitude to the devs on dfm dpi issues because they are fighting a very legacy system that goes back to the 80s. Multi-dpi support in Windows is problematic because of the base Win32 api. It's not like Mac where they chucked everything and went to floating point values, which is the real solution, but has the downside of throwing out billions of dollars worth of working code. (On Windows I mean. On Mac, since hardly anybody used it to do real work, it was no big deal to do it in the 90s.) Anyway, doesn't the "Low DPI" setting for the form designer solve the dfm issue? True, it means editing the form is scaled by the OS, but the rest of the IDE should be in the correct DPI. Am I wrong about this?

Why are you asking this question in a Delphi programming forum?

You try to reach programmer. If you want our attention, give us source code. Show us your approach. A PDF is not interesting.

They are not supported. But in our solution you can use any VCL conrtol on full client area (our or third-party with GDI drawing). With Aero Snap or Snap Layouts (native caption area) you can put on caption area only controls with specifc drawing, which prepeared to draw on DWM border.

That is because Win+D does not minimise windows. It brings the desktop window to the foreground. You can validate this by pressing Win+D again which will send the desktop to the back again, and all windows are just like before. What for Win+M? This will actively minimise the windows, and this should get handled by the OnMinimize event.

See the record helpers in https://github.com/pyscripter/Pcre-Jit-Delphi/blob/master/Demos/benchmark.dpr and the methods SetAdditionalPCREOptions

I guess I just have a different experience. In 30 years I have not had my system infected with a virus, I have not fallen for a phishing attack, and have never been infected with ransomware. The idea that I should install something like Webroot which would actively interfere with my ability to use my computer and do my job makes no sense to me given the that track record. BTW, I don't buy this line that Defender doesn't "perform well." But I don't think I'll get into that off-topic conversation. I will say that I am amused by this a little. You've identified software on your computer that is actively interfering with your ability to use it and do your work, but you have convinced yourself that it is somehow in your best interest. 🤷‍♂️

Bug fixes, bug fixes and after that: more bug fixes. Don't release until there are no more unresolved bug reports. Quit following hypes just for the hypes sake.

The one thing I'm still waiting for is per project packages/components that are automatically (un)loaded by the IDE, right from the code repository they're used in (i.e. machine independent). I can't believe we still don't have something like that after so many years.

I don't need any new features. I just need that the existing features work as intended. And there are many areas where existing features need to be made usable again (e.g. refactoring, code formatting, HighDPI). OK, one new feature would be nice: compiling for Raspberry Pi. But fixing the existing features needs to be done first.

You definitely have a misconception about how threads and timers work. Read the other answers and some documentation on the topic.

If you want the timer to run in the thread then the thread will not idle. You need to run your timer related code within the Execute method. To simplify, the Execute method is the one that runs in the background thread, thread constructor does not run in the background thread. You have some deep misconceptions about how threads work, but I cannot help you if you don't show your code. Right now you are doing everything wrong and you are not running any code in the background thread.

You say you need it to wake up at fixed intervals. That is exactly what Sleep(..) is for. Keep in mind that 10 milliseconds is a very, very short interval. If we are talking about Windows, then accuracy that low is not guaranteed. As far as I know, it has been improved in recent Windows versions, but generally, you cannot rely on the thread waking up again in exactly 10 milliseconds If you want the thread to wait for something else, you use an Event. You can have the thread wait for an event which is triggered from (for example) your main thread. See System.SyncObjs.pas for event classes.

The code within Execute method is what runs in the background thread. If you don't have any code there then you don't have a thread. If you want to run a timer in background thread, then you need to create that time in the Execute method , run a loop which handles messages and then release the times when thread terminates. There is plenty of code that needs to go in the Execute method. Background thread that is created by TThread class (at some point) will terminate when it exits the Execute method. Because there is nothing in the Execute method thread will terminate immediately when it runs. (since there is nothing there, it will On the other hand, your thread object instance will be alive until you free it. I cannot tell you more because you haven't shown any code you already have.

[SOLVED] I've put on app boot a on the main form : TFDPhysSQLiteDriverLink, with the property : EngineLinkage -> sIFDEStatic Maybee an idea do do that from code ?

What is the TApplication.MainFormOnTaskbar property set to? If MainFormOnTaskbar is True, then minimizing the MainForm will minimize the MainForm window to the Taskbar. In which case, checking TForm.WindowState or IsIconic(MainForm.Handle) should work. But if MainFormOnTaskbar is False, then minimizing the MainForm will hide the MainForm window and minimize the TApplication window to the Taskbar. In which case, checking IsIconic(Application.Handle) should work.