Ian Branch

Yup. Works just as well. Tks.

Noted. Tks.

Tks. Exactly what I needed/wanted. I made a minor change as I am using D12: /// <summary> /// Retrieves the current line number. /// </summary> /// <remarks> /// Requires the JCLDebug unit. /// </remarks> /// <returns>The line number of the current position.</returns> function GetCurrentLineNumber: Integer; begin // var ModInfo := GetLocationInfo(ReturnAddress); // Result := ModInfo.LineNumber; // end; LineByLevel - Whilst I could use it in my code by adding JCLDebug, I wanted to have it as a function in my library. If I used it from my library I got the line number in the library, not the Apps code. Regards & Tks again, Ian

I had a look at that previously. I may be missreading its use but it seems that JCLDebug relies on an Exception for something like this to work: function GetCurrentLineNumber: Integer; var ModInfo: TJclLocationInfo; begin ModInfo := GetLocationInfo(ExceptAddr); Result := ModInfo.LineNumber; end;

Hi Team, D10.4.2, Win 10, 4k monitor @ 150%. Anybody else seeing this effect in the Object Inspector?? If it's just me I won't sweat it, if it is being seen elsewhere I will raise a QC ticket. Ian

Oh how true.....

Hi Team, With the recent change in ownership of VMWare and the changes that have been wrought to it, I am leary of continuing to use it. What is a suitable alternative? I am using Win 11.

Ahhh. Tks.

Tks Brian. Yes, VMWare Workstation Pro. What dictates which alternative you use? Ian

Hi Team, Win 11, D12.1. I installed the latest Indy10 per the instructions. I noted that the uninstall cmd kept failing due to access level. I manually deinstalled the indicated Indy files. I then installed the 290.groupproj without issue. On restarting D12 I see the following message: I found IndyIPServer.dpk but Delphi doesn't like it. 😞 Do I need this .bpl? If yes, how do I now recreate it to Indy10? I am also seeing this error when I start D12: Regards & TIA, Ian

Ditto.

That is what I used.

IndyIPServer290 issue: Deleted it and the issue went away. 😉 It should have been deleted with the Clean up. LivePreview Issue: Answered in 2021 when I had the same issue. I don't use it so it doesn't matter.

Case on Strings. i.e. case myStringVariable of 'A': do something; 'Test': do something; etc end;

Aside from wanting all the existing features/functions working 100% and bug free, I wouldn't mind a construct like this: var a := b := c := d := 0; or similar.

Hi Team, Seemingly since I installed the D12 Patch: If I press enter here: on seemingly any method, or even within the code, more often than not I get this: Nothing else has changed. It is repeatable. Is it me or is there a bug un the Patch/update? It didn't happen before the Patch/Update. Regards & TIA, Ian

Tks Sherlock.

Roger, Lars, Fair comment. I apologise. I would edit it if I could.

So, the thicken plots.... I have narrowed it down to using the ''' construct with the ExpandedText property of a TTaskDialog. I create the TTaskDialog in code. Everything is happy with this: ExpandedText := '1. Wait - The App will try to reconnect until it connects or it has another connection timeout.' + sLineBreak + '2. Cancel - This is a last resort selection and will result in an Application crash and generate a formal error report.' + sLineBreak + 'At this error prompt you have the normal error report options.' + sLineBreak + 'If you don?t know or understand the error report dialog or the options available you should ask to your Workflow System Administrator.' + sLineBreak + 'It is strongly recommended that you select these options in the following priority/order => Wait then Cancel.'; As soon as I put all the text into the ''' construct and double click on the OnShow property of the form, It gives me the error that it can't find OnShow. Interestingly, I didn't get the 'finally-end' inserted as I edited the text.

Hi Brian, You may have hit on something there. I think I first noticed it when I was setting up text within the ''' - ''' multi-line structure. The 4 files I found the issue in had been so edited. I restored previous versions of each and all was fine. Today I was just editing one of those files in the IDE and was in the process of restructuring a block of text per the ''' multi-line structure, when it happened. 😞 I had pressed enter at the end of the text line and got a 'finally-end' back. 😞 I did a test again to see if double clicking on the OnShow Event would work, and no, it now failed per my original experience. I tried to back out the ''' construct, but the issue persisted. 😞 I restored a 1 hour old backup and it was fine. Note to Self: Don't bother with ''' constructs for the foreseeable future. This isn't a Patch 1 specific issue, 3 of the 4 files restored went 'faulty' around mid-Jan & the fourth around mid-Dec. Unfortunately, I can't replicate this in a test App. 😞 Ian

Hi Team, For what ever reason, it doesn't happen anymore. I didn't take notes, but I'm wondering if it was somehow related to the other issue I posted about which has been resolved. Seemingly corruption of some sort that I couldn't identify. Unfortunately, I can't recall if I experienced this issue in those Projects specifically, or in others. 😞 Certainly the issue reproduceable and annoying. Everything is working as expected now. Thank you all for your contributions. I will keep my fingers crossed... Regards, Ian

D12 + Patch. I just double clicked on the FormShow event of a Form to create the event. I got a "Cannot find implementation of method FormShow.: error. I checked, the declaration is in the Form Class and the procedure is in the code. Huh?? I added some code into the FormShow procedure but it doesn't run. I don't get any error messages. Any thoughts/suggestions?? Regards, Ian

😞

I backtracked through the versions and found that three developed the issue in mid January and one in mid Dec. Doing the usual file comparisons, I couldn't find a change/difference in the sour dfm files. 😞 All restored now and working as desired. Thanks for looking. Ian

Update - I just went through the 30 projects in the ProjectGrp. 4 projects are exhibiting the issue. 😞 I guess that narrows it down to what do those 4 have in common....