PeterPanettone

That worked in 10.3.1. But will I get those items specific for 10.3.2 and not for 10.3.1?

I have filed this new feature Request: The Procedure List should have a Flow Diagram option. What does this mean? Let's assume a unit has this source code: Then the Flow Diagram option would show the following diagram in the Procedure List window (instead of the list of procedures): Left-clicking on a diagram item would show the clicked procedure source code in the source pane. Double-clicking on a diagram item would show the clicked procedure source code in the source code editor. This would be a VERY USEFUL Procedure List view mode! Here is the URL of the Feature Request: https://sourceforge.net/p/gexperts/feature-requests/74/

This is the Pascal Analyzer 8.1.0.0 Call Tree report for the above example source code: However, when using this report, the user would have to buy Pascal Analyzer. So I probably will use the procedure list created by the GExperts procedure list. (Or the one used by the CnWizards procedure list).

Is it possible to customize the font of the Live Doc editor?

I have found it. It's here:

In the Call Tree Diagram, when the mouse pointer hovers over a diagram item, then the source code documentation of this procedure is shown in a formatted hint:

Good idea. Thank you!

The methodology I have in mind is to take the list of procedures generated by the GExperts Procedure List and convert it into a graphical Call Tree diagram by using the rules of logic. Would you agree with that approach?

"call stack" is a term from the IDE's debugging functionality and refers to the "visited" source code lines, I believe. The concept I have called "Flow Diagram" is in practice a sum of all possible call stacks, a diagram showing the complete call tree. Is this definition appropriate? Or how would you name/define the concept?

I would create my own from the TMS Diagram component.

That partly depends on my body's ability to metabolize large quantities of coffee. No, but seriously: Is it allowed to use a closed source DLL dependence? Or do you know a good open-source diagram component?

Colors in the Flow Diagram (this is a personal suggestion which could be customized): • FormEventHandler procedures: Fuchsia • ClickHandler procedures: Green • General ClassMethod procedures: ... • Functions: ... • Etc. etc.

I could also imagine the Flow Diagram View as an additional IDE main view tab after Code, Form Designer and History:

You mean when debugging? No, no, just a representation of the source code in the source code editor. With "MM" you mean ModelMakerTools or MMX?

AFAIR, ModelMakerTools had a lot of complicated abstractions. But what I need is only a very simple flow diagram as shown above.

The wuppdi Welcome Page start-screen text overwrites the next line on the IDE start-screen, as you can see from the above screenshot.

Daniel, first of all, thank you very much for the WWP! And I suppose you wouldn't give away the source for users to compile it themselves for their version?

Are you sure you mean "as the first package to be loaded"? Wouldn't that move the problem at the top of the splash list?

The only workaround I have found is to uninstall it WWP package, then restart the IDE, and then reinstall it. This makes the "wuppdi" splash text go at the end of the splash list: But as soon as I would add another package it would go up in the list again and the problem would reappear. So is there no way for me as a user to fix this problem?

What is the cause of the server malfunction? High temperatures? Why not building data centers in the Arctic? At least we could get funny error messages like: "A polar bear caused a malfunction in our datacenter".

Has anyone ever used Microsoft Application Virtualization for running the Delphi IDE in a kind of virtualized sandbox on a Windows 10 x64 desktop environment? Application Virtualization (also known as Process Virtualization) is a software technology that encapsulates computer programs from the underlying operating system on which it is executed. A fully virtualized application is not installed in the traditional sense, although it is still executed as if it were. https://en.wikipedia.org/wiki/Microsoft_App-V

Do you speak for yourself or for anyone?

To witch question do you refer?

ThinApp sounds also very interesting, with the ability to create SNAPSHOTS: https://www.vmware.com/products/thinapp.html

In a week I will migrate to a new system with new hardware and new OS: From: Windows 7 x64 SP 1, Delphi 10.1 Berlin, Delphi 10.3.1 To: Windows 10 Pro x64, new installation During the migration, Delphi will be used mainly on the new system, but it could also be started a few times on the old system. Is this a problem? What are the best practices for such a migration, from your experiences? Could anybody give me a few helpful hints?