PeterPanettone

I suppose external SSDs are attached via Thunderbolt cables on a Mac Book Pro? And isn't Parallels better integrated into Mac OS than VM Ware Workstation?

Running VMs with Windows 10 from an external SSD over a USB cable? Are you sure this would work?

Definitely (from the official Apple configurator website)

Yes, but the PC workstation hardware can be easily upgraded while the Mac Book Pro cannot.

A competent person from the PC workstation area told me: "If you buy a Mac Book Pro (15", 4 TB SSD, 4 GB graphics card, 32 GB RAM) today for 6,000 Euro you will have to replace it maximally in 3 years (and pay another 6,000 Euro) because the hardware will be out-of-date". Is that true?

Sorry for this question, but I am really asking myself whether the Apple community is some sort of mental institution and whether Apple can be a reliable business and technology partner? That's because yesterday I went to the local Apple store to ask a few technical questions about the Apple device I am planning to buy. But the employees there were technically incompetent. They couldn't even tell me the name of the current Mac OS (Mojave!). Then I asked for the connectivity with Windows networks, with computer displays, etc., but they couldn't give me competent answers. One Apple store employee made a rather crazy impression. So is Apple reliable and can Apple be trusted?

I am new to Mac. What is the Mac-share? Is that outside of the Windows 10 VM? So can the IDE inside the VM save/load files to/from outside the VM? What do you mean with "compile twice"?

Windows Messages is not complicated: Pass the window handle of Program1 as a parameter to Program2 which then sends the string back to Program1 as a Windows Message. Or - if Program2 is a console type program: Simply (programmatically) read the console output of Program2.

Peganza has kindly released a patch for Pascal Expert 9.5.0.0 to make it work with Delphi 10.3.1 (previously it worked with Delphi 10.3.2). From the Peganza website: "Pascal Expert is a new plugin for Embarcadero's Delphi IDE (RAD Studio). It does a static analysis of your source code, to detect possible issues and errors in your code. The results will help you better understand and produce code of higher quality, consistency, and reliability. Pascal Expert sits right in the Delphi IDE, so it lets you find problems earlier, and fix them right on the spot!" You can read more about Pascal Expert here: https://www.peganza.com/find-bugs-early-with-pascal-expert.html I highly recommend Pascal Expert to optimize your code and make it potentially error-free.

Yes, it worked. Thanks.

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.