From: Sieghard <s_...@ar...> - 2023-10-01 18:13:26
|
Hello Fred, you wrote on Sun, 1 Oct 2023 00:22:40 +0000: > There are binaries of ideU here: > https://github.com/fredvs/ideU/releases/ Yes, ok, I already took the source. > You dont need to compile it to test the debugger. > But of course if you want compile ideU with your new dialogs units, maybe > it will be a few tricky because in ideU source there are also custom > dialogs units. I DID recompile it (version 2.12.0 now), and even threw my "newdialogs" at it, and it compiled right away, and runs ok, on first glnce, at least. Well, not so much ok, though, as it DOESN'T want to keep the font size setting. Others too? It stupendously insists at always coming up with a huge 17 point (?) default font, although I didn't attempt to change the font yet. But that's a minor grievance only. Amendment: I just found that _disabling_ the setting for the "Suggested font height: 17" _does_ obey a saved font height. I suggest presetting that as "unchecked". Concerning the main pronlem I reported, the observations presented in my last message do hold: if a unit file had been opened before, e.g. for setting a breakpoint within there, the ide WILL reopen it a second time when the breakpoint is triggered on a subsequent run. Your ideU just does not complain about not being able to also open the form, at least when no form was shown before. Towards the stability of the debugger connection: I didn't test it a lot yet, but very soon stumbled over a not formerly seen phenomenon. Trying to have it show various variable values, I hit the name of an externally defined constant string (the "StatExt" from "newdialogs/msedialog.pas"). And it died, reproducibly, after a short delay. On the other hand, with the ideU, the debugger seems to be more stable indeed. Although I did have a glitch where it died on a complicated expression (FindText.dropDown.ValueList.asArray, to set the contents of a history list), I could not reproduce it a second time, so this might have been caused by something different I did. So, so far the results look like this: - Your ideU version 2.12.0 compiles correctly even with the "newdialogs". - It IGNORES any previous font setting, if that's not explicitely disabled. - It still places message windows (the "about" form, e.g.) at random spots sometimes, where they might be hard to see, especially below other windows. This might cause a situation where the ideU seems to hang. - "Some" dialogs (it happened to me on the project save dialog) have bad formatting problems - an overly long line gets broken up to be rendered behind the dialog's buttons. - The debugging code can die on certain conditions, like trying to access an externally defined constant. - Otherwise, the debugging code seems to be more stable than that of the original ide, although this couldn't be thoroughly tested yet. I hope that this might be of some use to you and help you to make your ideU even better, although I probabely will stay with the original ide or just my simple "make" script, because I simply don't need and thus not use most of its features. Thank you for your consideration, and have a good time. -- (Weitergabe von Adressdaten, Telefonnummern u.ä. ohne Zustimmung nicht gestattet, ebenso Zusendung von Werbung oder ähnlichem) ----------------------------------------------------------- Mit freundlichen Grüßen, S. Schicktanz ----------------------------------------------------------- |