Jump to content

aehimself

Members
 View Profile  See their activity

  • Content Count

    1090

  • Joined

  • Last visited

  • Days Won

    23

Posts posted by aehimself

  2. Posted

    34 minutes ago, Lajos Juhász said:

    Instead of adding the units from the runtime package into the design time you should add the runtime package as required. (The 32 bit version of the runtime package must inside the path).

    I just went to doublecheck, the runtime package is already included in the Requires section of my designtime package. Seems I added it, I just forgot 🙂

  3. Posted

    Hello,

     

    We had a large legacy component suite which I managed to split into Runtime and Design time packages in preparation to be able to build our application in 64 bit. I don't have much experience, so what I did was, basically:

    - Created a new package, set it as runtime only, moved all contains and requires section from the old suite

    - Created a new package, set it as design time only

    - Attempt to compile the runtime package

    - Move units to the design time package which blocks compilation (has references to designide, etc)

    - Repeat until both packages compiled error free

    - Added "implicitly imported" units to design time package

     

    All works fine, except one strange issue. Delphi chooses a seemingly random unit and throws an Internal Error when I want to install the package (compiling works fine both in 32 bit Debug / Release).

    Here's the twist: if I close Delphi, modify the unit with VS code and add a line break to the end of the unit (or remove one - basically change something completely insignificant) and save, reopen and install - all works just fine.

     

    I'm wondering if I missed something when creating the packages? Did anyone face this before? Does anyone has any tips I can check?

     

    Thank you!

  5. Posted

    5 minutes ago, Lars Fosdal said:

    Have you checked if your app receives any notification after the installation of the font?

    There is no automatic notification as far as I'm aware, but the app receives the WM_FONTCHANGE message which was broadcasted. In the discussion on GitHub I mentioned that if I put a label on the form, set the font name to the same as in the ListView and paste some characters it shows up correctly without PostMessage / Sleep. This makes me believe that the installation is successful, only GDI+ needs some time before it can access a freshly installed font (or implementation is not correct). Unfortunately I have zero experience with any graphic-related stuff so can not confirm / debug :(

    10 minutes ago, Lars Fosdal said:

    A sleep seems so random... what if the system is REALLY busy so that the sleep is too short?

    This is why it's not even viable as a workaround imo.

  7. Posted

    Is it just me, or even the demo application does not import the font file properly when started for the first time?

     

    image.thumb.png.7ee843c7cdfa6bffe6b48152c9d1fc9c.png

     

    If the font is installed on the system (manually or by AddFontResource due to the first run) everything appears correctly.

     

    I tried Screen.ResetFonts and ImageList.RecreateBitmaps after the SendMessage, without success. Dumping everything on the disk with .SaveToPngFiles also saves the rectangles only.

     

    I'm using the latest snapshot from Git directly.

  9. Posted

    My forever favorite stays this: 

    Function GetUserID(APageIndex: Integer): Integer;
Begin
 Case APageIndex Of
   0: Result := -1;
   1: Result := -1;
   2: Result := -1;
   3: Result := -1;
   [...]
   50: Result := -1;
   Else Result := -1;
End;

    Probably it had functionality a long time ago, but this method was still called from a live part of the code when I found it...!

     

    There were also some fancy fails (mainly memory leaks), including but not limited to: 

    TMyClass = Class(TObject)
private
 FOwner: TComponent;
public
 Constructor Create(AOwner: TComponent); ReIntroduce;
End;

Constructor TMyClass.Create(AOwner: TComponent);
Begin
 FOwner := AOwner;
End;

    Or the other, which was probably a typo but took me a while to finally realize the issue: 

    TMyClass = Class(TComponent)
public
  Constructor Create(AOwner: TComponent); Override;
End;

Constructor TMyClass.Create(AOwner: TComponent);
Begin
 inherited Create(Owner);
End;

     

    • Like 2

  11. Posted · Edited by aehimself

    I solved this with the handler of TSynCompletionProposal.OnExecute (TableNamesSelector is a TSynCompletionProposal, SQLEditor is a TSynEdit) : 

    Procedure TSQLConnectionFrame.TableNamesSelectorExecute(Kind: SynCompletionType; Sender: TObject; Var CurrentInput: String; Var x, y: Integer; Var CanExecute: Boolean);
Var
 sa: TArray<String>;
Begin
 If TableNamesSelector.ItemList.Count > 0 Then Exit;

 sa := SQLEditor.LineText.Substring(0, SQLEditor.CaretX - 1).Split([' ']);
 If Length(sa) > 0 Then sa := sa[Length(sa) - 1].Split(['.']);
 If Length(sa) < 2 Then TableNamesSelector.ItemList.Assign(SQLHighlight.TableNames) // No dot, offer table names immediately
   Else Begin
        CanExecute := False;
        If Length(sa) = 2 Then // Start a thread to collect field names of said table...
        End;
End;

    You have to pass sa[0], sa[1], X and Y to the thread. sa[0] is the table name, sa[1] is the field name fragment which was already typed, x and y is the position where the proposal should pop back up.

    Once it finishes, you can: 

     TableNamesSelector.ItemList.Assign(worker.FieldNames);
 TableNamesSelector.Execute(worker.FilterForText {passed to the thread as sa[1] from OnExecute}, worker.X, worker.Y);

    Also handle the OnClose event of the completionproposal: 

    Procedure TSQLConnectionFrame.TableNamesSelectorClose(Sender: TObject);
Begin
 TableNamesSelector.ItemList.Clear;
End;


    The idea is that if the ItemList is empty the data still has to be collected and execution is disallowed. It will be popped up when the thread finishes.

    • Like 1
    • Thanks 1

  15. Posted · Edited by aehimself

    Long story short: I'd like to get the popular opinion / correct way to handle a situation in a TDataSet descendant - and DelphiPraxis does have the userbase for it.

    What do you think, does it make sense to be able to change the .SQL property (the SQL query to be executed) of a dataset component while it is open and contains a resultset? Keep in mind that this can be an INSERT, UPDATE, DELETE command too, not necessarily an other SELECT.

     

    The full discussion with pros and cons can be read here for those interested.

  16. Posted

    20 minutes ago, corneliusdavid said:

    If you want to write a server app or a web module, this is the best way to go as debugging a console app

    I started to write my applications as a single class some years ago and never turned back. Want to start from console? TMyApp.Create; From a Windows service? TMyApp.Create; From the Mt. Everest? TMyApp.Create;

     

    You'll have to refine logging for sure but this is the easiest way I ever experienced to write self-containing, easy to debug code.

     

    I even took this one step further by adding some code to the .dpr of my Delphi services: if you start with the /console parameter, it starts as a console app instead of a service.

  18. Posted · Edited by aehimself

    Thank you @Dalija Prasnikar, I learned some new things about window messages! Unfortunately though, none of the above applied to my case.

     

    After the comment of @Lars Fosdal I got rid of the TTimer and used the same dummy window to catch the now manually fired SetTimer messages too. I also included a counter which increases each time a window message is received (whether processed or not) to see how swarmed application is. With a timer of 1 second, 70 seconds of runtime I got 72 messages. 1 is UM_WORKERENDED, I count the extra 1 as an acceptable discrepancy due to the timer's accuracy (or something unprocessed).

    So no, it was not the window messages.

     

    The solution is so painfully trivial I'm almost afraid to share...

     

    In the TComponent my timer was set to 750 msec to update the elapsed time on the UI. As I'm using TStopWatch, I manually converted the .ElapsedMilliSeconds to some readable format... using dividing and substracting.

     

    First time the timer fired at 0,75 seconds, UI was updated with the rounded 0 seconds.

    Second time the timer fired at 1,5 seconds, UI was updated with the rounded 1 seconds.

    Third time the timer fired at 2,25 seconds, UI was updated with the rounded 2 seconds.

    Fourth time the timer fired at 3 seconds, UI was updated with the rounded 3 seconds.

    Fourth time the timer fired at 3,75 seconds, UI was updated with the rounded 3 seconds.

     

    Even if the timer component is spot on it can be seen that every 3 seconds, for 2 seconds the elapsed time does "not update"... thus the feeling of variable speed.

     

    After upping the sampling to 1000 msec instead of 750 and some small tweaks to the conversion everything seems to be working fine.

     

    Why it was working on the TPanel...? Because originally I forgot to change the default 1000 msec interval to 750...

     

    What a nice way to waste a day by debugging something, which is working as it should 🙂

    • Like 1

  19. Posted

    Hello all,

     

    I have a progress indicator on a panel which is visible until a thread is running. On here is a timer which is updating the status of the thread every second (elapsed time, some data from inside the thread, etc.). The .OnTerminate event of said thread has a custom message sent to the panel so I can do some final touches plus freeing the thread object up: 

     PostMessage(Self.Handle, UM_WORKERENDED, 0, 0);

Procedure TProgressPanel.UMWorkerEnded(Var Msg: TMessage);
Begin
 _worker.WaitFor;
 FreeAndNil(_worker);
End;

    All was working fine until a recent refactoring, when I changed the panel to a TObject for modularity reasons (now said panel can display different content, so I had to move the progress indicator to it's own).

    Since a TObject has no handle I created a dummy window with AllocHwnd and sending my message on this dummy handle. Everything works like clockwork, but I realized that the status update timer became laggy. Sometimes it refreshes too quickly (from second 1 to 2 in ~750 msec) and later on delaying more than 1 second (from second 2 to second 3 in 1,25 sec). Elapsed time is measured with a TStopWatch so I doubt the issue is with the measurement.

     

    I am aware that the TTimer works via Window Messages - is it possible that adding a dummy window with AllocHwnd (which is picking up ALL window messages, not just the one specified) causes the code to simply be overwhelmed, not processing WM_TIMER in time?

     

  20. Posted

    If you have Excel installed where the program will run you can use the COM API to interact with Excel files from your Delphi app I think. I personally never used any of these but I know it can send E-mails with Outlook so I suppose you can use Excel too.

    From there it's easy as a pie. Just do a loop, dataset.Append; dataset.FieldByName.AsString := excelcell; dataset.Post.

     

    @FPiette has my preferred answer too. Just export to CSV / TSV (which I personally prefer) and it's really easy to parse those with Delphi.

  22. Posted

    Hello,

     

    On my development PC Delphi 10.4.2 stopped displaying the tooltip with the parameters and their types when a bracket was opened. E.g.:

     

    image.png.3f46c43352baff5c9c06af743bfef3db.png

     

    I compared the Code Insight settings with a PC where it is showing up properly and they seem to match. Currently I'm using these:

     

    image.thumb.png.837e5e085f1e78cd546114bbc533af25.png

     

    I remember that in the past unchecking something - reopening Delphi - re-checking something - reopening Delphi solved this (my hunch is on Code template completion... unsure though) but I cannot seem to get this tooltip back alive now.

     

    Is there something I still can try before dropping my registry entries and start to reconfigure the IDE from ground up?

  23. Posted

    9 minutes ago, Der schöne Günther said:

    Stupid question: Is it running inside a VM or directly on real hardware? When I installed it inside a Hyper-V machine, it lacked 3D acceleration and a lot of effects (transparency, animations, rounded corners) were missing.

    It is a VM running on ESXi, with tools installed. Transparency is visible even through RDP. In general, windows do not have rounded corners, just some special ones (like the Start thingie, dialogs in Settings, etc.)

  25. Posted · Edited by aehimself

    Actually no, compression is not performed in the project in which this class was used.

    Data packet is a JSON object which gets serialized and encrypted... size is usually between 80-140 bytes, which only increases after compression.

     

    The reason I didn't include a version in the header is the packet itself: if a new version adds a new field this easily can be detected during deserialization.

     

    I know the code is not completely universal. I kept it as simple as possible to do it's job in this context and nothing more - keeping the logic easy to read and understand. If your packets are usually larger than 64k, it's enough to change TPacketLength = UInt64; for example, the rest of the code should take care about this automatically.

     

    P.s.: I just read your first answer again and realized that I'm indeed copying an Integer in a TPacketLength which is definitely not right! I'll fix this and move the size check from my program to this class so I can reupload. I should also mention the size limit in the "Keep in mind" section I assume 🙂

     

    P.s.p.s.: There was a network loss between just the other day and about 90k of buffer was received by the server upon reestablishment containing a number of ~140 byte packets. The code worked flawlessly, separated and processed each of these without errors. So yeah, I'm happy 🙂

    • Like 2
×