PeterPanettone

Who?

Here are the places I found where the "drop bookmark" feature can be switched off: History: Searching: Did I miss any? Is anyone using these dropped bookmarks? Thanks for the other basic MMX features; they are very helpful!

This is the GExperts version I use: In the old days, "when GExperts was still working," GExperts remembered its window sizes. Now, when I open a GExperts window (e.g. Code Librarian), it always starts at the same minimal default size (although the window position is being restored). Is there a way to make GExperts remember its window sizes again? I've tried to edit the window size values in the Registry, but it does not work - it always starts at the minimal size:

Delphi 12.1, GExperts 1.3.24 build 4222, Windows 11: Code Librarian doesn't remember its window size, font size, and the width of its treeview panel, although I have saved the IDE desktop after setting both. Is this a bug, or is there a trick to having these options restored between sessions?

Are you sure that "scaling" generally works as intended? Maybe we could do without it

This might also cause another existing problem: Currently, if the IDE CRASHES (which unfortunately happens sometimes), all changes in CodeLibrarian (e.g., adding an Item) are LOST! So, the remedy proposed by you should also be applied to content saving: All CodeLibrarian CONTENT CHANGES should also be saved during FormHide).

Has Delphi not been suffering from this problem for many years now?

Thanks for the information. What do you mean by "scaling" in this context?

Dear Thomas, Thank you for quickly finding the cause of the CodeLibrarian's misbehavior! Does this mean that you also have a remedy? The "Side-by-side" Layout is preferable on a widescreen monitor, of course: However, it's the width of the treeview that is not remembered.

Dear Thomas, In my posting, I mentioned "Delphi 12.1". I suppose that by configuration dialog, you mean CodeLibrarian's Options dialog where I have set the font size: But as soon as I reopen CodeLibrarian, the settings are lost.

On Mac, I have used SnippetsLab for Delphi code snippets. I have exported them to a json file. Does anybody know a good snippet manager for Windows that: - supports Delphi syntax - can import json files - has good organizational features like tags, folders, search, filters, etc.

The advantage of GExpert's Code Librarian is that it uses the same syntax highlighter as the IDE editor itself. Its disadvantage is that the edits are lost when the IDE crashes after you have made some edits in Code Librarian in the current session!

Now that GetIt is available again in Delphi 12, I tried installing an item. But something is wrong with the GetIt Package Manager installation mechanism - when clicking on the 'Yes' button, nothing happens: There seems to be something hidden behind the dialog box. I could only kill the IDE from Task Manager! Can anyone confirm this?

After a successful build, this message is shown: Is it possible to show the size of the executable file as additional information in the Messages window?

That was not a "problem" but an IDEA.

That's just fun. I am a multitasking guy. It's also part of a psychological study for which I'm being paid. I am also collecting material for my new Delphi book: "Neurotic disorders in hobby programmers."

Nobody said "status dialog". We call this the "Messages" window:

For individual preferences, we have OPTIONS. "The assumption or desire to transfer one's needs to the general public is a symptom of neurotically exaggerated ego-referentiality, often triggered by childhood regression." (Quote from a professional psychologist).

Behavioral conditioning and a few other effects: https://www.verywellmind.com/operant-conditioning-a2-2794863 I love Delphi!

I found this funny anecdote. While it doesn't fully apply to this topic, it can still be thought-inducing: Five monkeys are placed in a cage with a banana hanging from a ladder. Every time a monkey tries to get the banana, all the monkeys are splashed with cold water. Soon, each monkey hits anyone who tries to get the banana to avoid punishment. One by one, the monkeys are replaced by new ones. The others beat Each new monkey when it tries to get the banana, although water jets are no longer used. Ultimately, all the monkeys beat each other, even though none have experienced the original punishment. They do it because it has "always been done that way."

Please read: Click here:

Exactly. This is another reason to show the executable size after success and duration information—both for the debug and release build configurations.

Well, a developer's requirements can be different. For example, the decision to include a certain component at design time or not could depend on the size of the executable. Therefore, the size of the executable could certainly be an interesting information. For example, it could matter whether the executable size is 10 MB or over 100 MB.

Well, the size of the executable created is just as important (or even more important) information than the build/compile time, which has always been displayed.

Please add this option to GExperts as soon as possible. Many users will be happy about it! Thank you!