Edwin Yip

@dummzeuch Can I take this chance to make a suggestion? - In the 'Memo' view of  'Library Path' and the porject options 'Search Path', as shown in @Primož Gabrijelčič

's posted screenshot, two things would increase the productivity:

• Allow pressing [Ctrl + A] to select all text in the Memo.
• Even better - to have a 'Edit with external text editor' button, which when being clicked, will open the system's default text editor to edit the search paths.

I guess this can be done with something like:

• save the paths to a temp file with a unique name.
• use the CreateProcess API to launch the text editor (the system's default one or can be specified by the user in GExperts), open the temp file.
• After the text editor's closed (IIRC you can can notified with the CreateProcess win32 API), load the modified content from the temp file and put it into the 'Memo' view of the path editor.

Sorry for being off topic, I saw PG's screenshot and this idea came up :P

15 hours ago, David Hoyle said:

Switch off the option to scroll to the newest message, Auto Scroll (F6), Fifth icon from the right on the top toolbar.

Hey David, the speed difference is HUGE! Thank you so muchhhhhhhhhhhhhhhhhh!

Try GExperts -> Editor Experts -> Paste String As.

This is a gem from GExperts. Furthermore - you have 'Copy Raw Strings' which does the opposite.

When in DEBUG mode one of my app generates a log of log entries using CodeSite.

The logging process is OK, but the Live Viewer's update is tooooooooo slow - even after the app existed the Live Viewer still took 5 more minutes to finish receiving the logs.

Any way to improve the performance? 

I want this feature too.

Two options off my head:

1.  Tools->CodeSite->CodeSite Method Tracer, which can auto add method enter/exit tracing to your code. Once you have identified the method, you can manually add the logging for each time as you tried.
2. Utilize DelphiAST to write an IDE plugin or a tool to do that :) If you do this, don't forget to share it with the community :)

On 10/26/2018 at 9:17 PM, Memnarch said:

Would love to see that. While I'm not an expert to C++, working with it in the UnrealEngine makes it so much simpler to identify ownership just by looking at the declaration of a parameter for example.

Which means: If an argument is not a Shared-Pointer, you can't store the value anywhere and only use it during runtime of the method. If it is a Shared-Pointer, you can keep that if needed. The Story of "Who owns it?" suddenly becomes very short 🙂

An exception here are UnrealProperties but that is blackmagic beyond the scope of what i wanted to say here 😉

@Memnarch, that's very interesting, would you point me to some example code? I don't know much about c++, thanks!