tomkrysl

Forum Replies Created

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • in reply to: DPI scaling problems with latest 14.36 #68265
    tomkrysl
    Participant

    I can make different exes and send you link via email.
    If you send me your email to my email (see my profile).
    I cannot send you sources.

    in reply to: DPI scaling problems with latest 14.36 #68257
    tomkrysl
    Participant

    Hello
    ok, thank you for info, I didn’t know about such huge changes.
    I just replaced the AC source and compiled my project again.
    No warning etc. has been issued.
    The only warning I’ve got was when I now recompiled the design packages in Delphi and reopened my form (stored skin obsolete).

    However, there are still problems with v14.36.
    I still use Delphi XE (but same is XE5). I dont (and wont) have newer Delphi.

    a)it is very slow.
    When I keep the defaults (Options.ScaleMode=smAuto,Options.PixelsPerInch=96) my app starts 10s instead of 5s with v13.16, is way too slow!
    When I set smOldMode it is even slower, 11s.
    When I keep smOldMode and comment out ACDPIAWARE the app starts 6.5s.
    These were tested at 96DPI (100% scaling in Win10), no size problems.

    b)size problems.
    I try to set 125% scaling in Win10.
    When I keep the defaults (smAuto,96 PPI) my app starts 17s(!!!) instead of 8s with v13.16, is waaay too slow and moreover it has incorrect size, is very big (I suspect it has 150% size instead of 125%).
    When I keep smOldMode and comment out ACDPIAWARE the app starts 9s and has correct size.

    c)painting problems.
    The 13.16 had some minor painting problems. Sometimes checkbox was not painted on pagecontrol page and extra panel on it (had to switch page to another page and back to see it), sometimes combobox background was painted incorrectly in disabled mode.
    The 14.36 has no such problems so far but sometimes the main form flickers black just before it appears on screen.

    The main problem with v14 is the slowness. I continue with v13 until fixed.

    Note:
    In my app I have large number of misc controls on main form, either as designed or I create them at runtime before the main form is shown. I tried to set Active=False during creation to speed it up but without effect.
    When the main form is shown and all the controls are created it is slower but can be worked with.
    The same app can be compiled in Lazarus with dummy AC package (I’ve sent it to you a long time ago) and there it starts blazingly fast (<1s). So the speed problem is AC.

    Regards
    TK

    • This reply was modified 4 years, 10 months ago by tomkrysl.
    in reply to: How to skin custom button #52061
    tomkrysl
    Participant

    I found a solution myself. It can be extracted from the TsBitBtn source.

    It is not so easy as native DrawFrameControl but it is not so difficult as I first thought when looking into the source code.

    A few notes for anybody who might be interested:

    You must be a registered user to have sources.

    Just start with PaintItemBG function which is located in the PrepareCache function.

    This function draws the entire button background into a cache bitmap, which must be then copied to button canvas.

    Initialize the cache bitmap exactly like it is done in the PrepareCache function.

    Furthermore CommonData must be properly initialized (don't forget the AfterConstruction and Loaded methods).

    Finally State parameter signals the button shape.

    It is even quite easy to implement timed fading, just take look at the DoChangePaint function.

    To add this, you need the PrepareCache function and call it in the AC_PREPARECACHE message handler.

    This button might later be part of my KControls package so you might take a look.

    in reply to: AlphaControls for Lazarus #50849
    tomkrysl
    Participant

    Hello AlphaControls team,

    we're using AlphaControls in all our commercial projects (of course registered version).

    We also evaluated Lazarus because it is the only IDE where our projects can be ported into. Many our customers wish the configuration software for our controllers to run on Linux and the only way we recommend now is: You can use Wine (or Windows virtual machine).

    But, have you ever seen your components running under Wine? It is horrible!

    Please do not take this as blaming you, I just know there are limitations in Wine, incompatibilites etc.

    Furthermore, FTDI USB which we use is not running under Wine so far, either.

    We cannot simply switch off Alphacontrols because all our marketing and manuals etc. are built on it and I personally like that controls.

    We will port the applications to Linux either way (just making other form files and some code hacking so we can use one source for both), but I would really appreciate making Alpha controls for Lazarus.

    Of course we would pay for it.

    Best regards

    Tomas Krysl

    http://www.solarcontrols.cz/en/

    in reply to: Bugs in v8.15 #50023
    tomkrysl
    Participant
    'Support' wrote:

    Hello and sorry for a trouble, new update will be available today with this issue fixed.

    I have a list of applications which are used before each new release but all tests can't guarantee that in some situations bug will not exist.

    Look a small image attached. These projects always used for test before each new release.

    If you have a test-application based on your project and if you can give me it, then I can promise a full testing of him before the each new release.

    It's possible to send me such application?

    Bigger image is a list of projects which are tested time-to-time.

    Test project attached. V 8.14 ok, V8.15 not ok.

    Try 3 or more times pressing button 2.

    WinVistaSP2,RadStudio Delphi XE.

    in reply to: Glow effect causes exception in Forms.DoActionIdle #50022
    tomkrysl
    Participant
    'Support' wrote:

    Thank you for information, I will research it. Do you know how can I reproduce an issue?

    Maybe you can cut off all code from your application and send me this project?

    Unfortunately this is not possible. I'm afraid it can be reproduced only in the whole app when connected to the device we sell.

    It seems to be somehow dependent on timing of the messaging processing.

    The only suplementary information I can give in version 7.68 it was ok and in version 8.14 and 8.15 it was not ok.

Viewing 6 posts - 1 through 6 (of 6 total)