Roy_043 wrote: ↑Thu Jun 01, 2023 1:38 pm ... That's a lot of information to NOT read.
In brevity:
- the main cause IMO is the different contexts of different minds (GUI-writer on one side, user on the other), depending on the issues
- particularly in this case, my mind strongly and falsely was focussed on finding
'...the dot program from the graphviz package...' instead of its location (directory)
These two major reasons were leading to that.
A bit more lengthy:
What happened (for a new user, or
dunderhead ):
- Hitting Tools -> Dependency Graph, FC's prompt is saying:
...specify Graphvizs installation path... (img-1)
- img-1.png (6.76 KiB) Viewed 1384 times
- the user is specifying the ../Graphviz directory - (for the user, this
is the Graphviz's '... installation path...', the path/directory, where Graphviz was installed to and all installation-files reside (6 directories, at the minimum hundreds of files)
- without further notice, FC reacts with repeating the initial promt
Ok, the user is searching for
'... the dot program ...' (whatever that may mean) within the Graphviz directories, now on OS-level.
- having finally found a file named dot.exe within the ../bin dir, the directory ../bin is entered or pointed to
-> success!
Edit:
Personally, I would point to the dot.exe as main executable and would add its usual home-directory to the information (depending on the OS, if needed).
So, another useful GUI-draft could be (if nothing else stands against it):
'...enter the directory name of the main executable of Graphviz...' ... 'in most OS'ses ../bin, where dot.exe resides'
Agreed - the length of the string would increase a little. It still would be worth to avoid confusion IMO.
This is rubbish...
Provided, an installation directory is called the installation directory (I have no better suitable name for it). It would be
very little effort to sort out this ambiguity or unclarity.
If FC would follow the text of its message-prompt of img1.png, everything would be fine.
(The directory-structure of Graphviz is known to the deveopers. Once the custom-dependent installation place is known, all what is needed also is known. For each valid OS, I think.)
Regards
Uli