[mol]

No need for improvement here, Serge. Creating a form within a form within a form is just bad coding style. Holger, instead of TForm, use TFrame. That's what they are there for.

-Uwe

[mol]

2000 components on one form using a TPageControl? High time to rethink your design choices. Why on earth are you using a TPageCtrl instead of TFrame? You can create and destroy the latter on demand and keep the footprint on your form really small.

-Uwe

[mol]

Try this:

https://stackoverflow.com/questions/7529524/keep-the-scrollbars-hidden-in-a-delphi-dbgrid-even-on-resize

[mol]

Those are ancient Delphi components. I didn't even know that they are still around.

http://www.silverpointdevelopment.com/sptbxlib/

[mol]

Try this one, Dick:

http://www.swissdelphicenter.ch/en/showcode.php?id=586

[mol]

Stephane,

use a manifest to make your application DPI aware: http://stackoverflow.com/search?q=%5Bdelphi%5D+dpi+aware+manifest

-Uwe

[mol]

'Support' wrote:

Thank you, I'll check it soon.

Serge, any news on this one?

-Uwe

[mol]

Okay, thanks.

[mol]

'Support' wrote:

Sorry, this property will be implemented in the february.

Great, thank you.

[mol]

Inno Setup, of course…

http://www.jrsoftware.org/isinfo.php

I would suggest to look at their Third-Party Files page as well – especially Inno Script Studio, which is a great GUI for Inno Setup.

-Uwe

[mol]

Serge, do you think you will implement this in 2016? It's been a “while” since I made this request…

Thanks

-Uwe

[mol]

Serge, any news on this?

-Uwe

[mol]

The obvious:

Code:

procedure TForm1.sFrameBar1Items0FrameDestroy(Sender: TObject;
var Frame: TCustomFrame; var CanDestroy: Boolean);
begin
CanDestroy := False;
end;

-Uwe

[mol]

Dick, you have to unblock the file before you can use it.

-Uwe

[mol]

'concrete' wrote:

…just for a small number of people who haven't learned a valuable lesson that you NEVER move to a new operating system until at least 6-12 months after release so that all the bugs and incompatibilities can be addressed?

Looks good on paper, doesn't it? Real life software business is different, though. You have to support Win 10 early on to stay ahead of the competition. Simple as that.

-Uwe

[mol]

Dick, I never claimed that AC is the one which is responsible, but since I've seen what a mess Win 10 is at the moment and knowing Microsoft, I'm sure that Serge will have to work around certain “features” (like the flawed animation thing) and bugs of Windows for many months to come. My point simply was that AC will never be a finished product as long as the operating system is evolving, and Serge will therefore be fully occupied with the Windows version of AC in the future.

-Uwe

[mol]

Hi Dick,

The problems are mainly with Win 10 at the moment, but there is a very good chance that AC will be impacted as well. Try this one for a start:

http://answers.microsoft.com/en-us/windows/forum/windows_10-start/bugs-when-working-in-tablet-mode/a967f27a-90a7-489e-a71d-271aaf3e56ba

Set the main form's BorderStyle to bsNone and/or the WindowsState to wsMaximized (you shouldn't do the latter, of course), and you will get the same results I've described in the link above. Leave the “Play animations in Windows” enabled in Win 10, and you will experience an extremely slow painting of TFrame's for example when they are created (and skinned) in the FormCreate event and automatically resized afterwards. Maximizing the form in the OnShow event by using ShowWindowAsync(Handle, SW_MAXIMIZE); doesn't help you as long as animations are enabled in Win 10. There's a visible flicker and flashing of the screen, and since AC is heavily involved during the paint process the negative effect is actually getting worse.

The list goes on, but much of it is hardware and/or driver related.

Hope this helps

-Uwe

[mol]

'concrete' wrote:

It does NOT require continuous 24-hours-per-day development

How do you know that the only source of income for Serge is AC? He probably has a daytime job as well and does programming on the side. And even if it's his fulltime job – nobody spends 24/7 on the development of a product. There's a life out there as well…

'concrete' wrote:

AlphaSkins is an old and mature product. It's very usable and stable.

Very true, but then comes Windows 10 along and your once stable version enters unknown territory again. I recently switched a few of my machines to Win 10 and believe me, it's no fun. Hardware not working, tablet mode buggy as hell, system dialogs different, and a ton of other issues – and then there is AC which has to master many of these annoying shortcomings. To cut a long story short: Serge has a lot of work simply keeping up with the development of the OS and hunting bugs, and then we haven't even talked about introducing new components into AC, supporting other 3rd party stuff, or enhance functionailty in general.

-Uwe

[mol]

Dick

As I said before: in my opinion it's simply a waste of precious resources that should better be invested in the ongoing development of the Delphi/Windows version. There are most likely so many hidden roadblocks that at some point in time, the project will simply be abandoned. Remember Kylix?

-Uwe

[mol]

'SzakiLaci' wrote:

…too many … windows-handle calls / messages not available under Lazarus.

Well, that comes as a surprise…

[Author]

Posts