Leaderboard

See https://quality.embarcadero.com/browse/RSP-29136 https://quality.embarcadero.com/browse/RSP-29162

It might not be perfect yet but at least there's a path forward, rather than the hopelessly broken error insight we've been putting up with for the past 15 years. Red squiggles that go away eventually is definitive progress compared to red squiggles that had no hope of ever disappearing.

Konopka KSVC and Bookmarks are now available in GetIt for Syndey Edit: Navigator is also now available.

You have to select all the fields to be converted in the MMX Code Explorer Window. For an example see this video: Convert Multiple Fields to Properties

This is exactly what I started to do lately. All my applications business logics are basically a TObject-descendant, and service initializations or console launchers only create an instance of them. I find this structure really easy to test, to port, to maintain or extend. This might be my own personal preference, though.

I've been asked to find a GUI automation tool for a Firemonkey desktop application for Windows. There're several tools that work for VCL applications but I can't find anything for FMX apps. Many well known tools can't find the FMX controls and they can only simulate mouse and keyboard events, compare screenshots, OCR, etc. All I could find is this StackOverflow question : https://stackoverflow.com/questions/30197921/how-can-i-automate-delphi-firemonkey-ui-testing-without-access-to-source-code That question has 2 suggestions : - Use the "FireMonkey Accessibility Package". - Build a "Test harness". The "FireMonkey Accessibility Package" for Delphi 10.2 is here : https://cc.embarcadero.com/Item/30780 It seems to work with Delphi 10.3 if we apply this fix : https://quality.embarcadero.com/browse/RSP-25532 My question to all of you is this : What GUI automation tool do you use for Firemonkey applications? Are we limited to building "Test harnesses" or using the "FireMonkey Accessibility Package"? Thanks!

In my example there's already room for 65 characters in the destination since Delphi strings have an implicit null terminator.

Note that when using StrLCopy(), it copies up to the max length you specify and then adds +1 for a null terminator. So, to account for the null terminator, you need to either +1 the memory allocation, or -1 the max length to copy. This is documented behavior. Actually, they did - it is called SetString().

One connection per thread is like an unwritten rule. I experimented with one connection for 7 workers, but gave the idea up quickly. One thing I found strange is that if I called dataset.Open in a background thread, I had to call .FetchAll too, otherwise it still froze the VCL thread upon accessing .RecordCount. But the jumping between records error still makes me believe that the connection is going to be the issue - if FireDAC works similar to the components I use.

You need to use StrLCopy instead of StrPas since there's no guarantee that the source string is null terminated. You actually need a StrLPas function but fo some reason they've never implemented that variant. Also remember that the buffer is a static array[] of Char[0..63] so you need to iterate the outer array somehow. var Buffer: PChar; GetMem(Buffer, PaperCount*SizeOf(Char)); try var p := Buffer; for i := 0 to PaperCount-1 do begin var PaperName: string; SetLength(PaperName, 64); StrLCopy(PChar(PaperName), p, 64); PaperName := PChar(PaperName); // or SetLength(PaperName, StrLen(PChar(PaperName))) ... Inc(p, 64); end; finally FreeMem(Buffer); end;

That's what I would do as well. Though it is nice to have everything in one unit...it is not nice to do so, because that code is not reusable, especially if it is in a dpr. And you never know, if you'll need it later on.

Treat console apps like you treat VCL or FMX apps. Keep the actual code in units and have just the skeleton init and run code in the .dpr.

Error insight (and code navigation) is still unreliable, unfortunately. I'm test-driving 10.4 with small projects (maximum 15 units) and sometimes the red wiggles stay until I restart Delphi (or run the application). Code navigation completely fails for some 3rd party components if the (system wide) library path is pointing to DCUs only and debug source path and browsing path is set to the source files. It usually can navigate to the first unit, but not to the second one from there (unless if it is already open)

Yes it is, thank you. I thinking to release it all source code later. The idea behind is simple and it is a quarantine project: I was thinking to monitor some of my computer sensors using WMI queries, but quickly I realise the information about GPU is device dependent on drivers and the time I would expend to accomplish won't be wort. I found a software called Open Hardware Monitor (https://github.com/openhardwaremonitor/openhardwaremonitor) that you can keep it running in background and expands the WMI. Now I have a server that read temps and loads so I can choose what I want to monitor. My computer case has a glass so I could put an old tablet or phone there inside 😄 Here's more decent screenshot of both client and server (still a WIP).

I’ve found a link to how to add a storyboard to a Delphi 10.3 project here: https://quality.embarcadero.com/plugins/servlet/mobile#issue/RSP-12931 Take a look at the 4th response from Sarina DuPont

You're absolutely right ... I just wish if your friend Daniel did too ! Now, we're clearly understanding each other. I got the feeling that you were trolling. You would clearly understand if role changed and you were at my place. I'm very sorry if this at any case hurts you.

I don't think about you at all. I was interested in the question. Try to view comments as impersonal. That's entirely possible. I'm interested in learning. It's possible that my misunderstanding is because of imprecise statements. It's possible I'm slow on the uptake. To be clear, I thought you said that types declared in the project file had no RTTI. I checked that and was able to retrieve RTTI for such types. I simply don't understand the strength of your reaction.

I see no obvious reasons why this could cause problems. IOW, I think it should work, yes.