Menu

#119 Project icons in CLI mode pass wrong Current Dir to Default Tool

v1.0_(example)
open
nobody
None
1
2017-01-21
2017-01-21
Elena
No

When a Project icon (with CLI tooltype) associated with a specified Default Tool is launched, the Default Tool executable is launched with current dir set to the Default Tool path and NOT to the Project file path as it should be. (The argument passed, moreover, does NOT contain any path but only the project filename part.) This way, any associated default tool will NEVER be able to open the project file, not knowing its path ! (Amiga Workbench sets the current dir to the Project file path as it should be). The excuse that "Ambient is NOT Amiga Workbench", which I heard already, makes no sense: since the CLI tooltype, to launch Default Tools in Cli mode (vs Workbench mode), IS supported by Ambient, a correct path MUST be provided aswell. This bug prevents the user to associate his custom project icons with any commands, to the point that even just associating a
text project icon to, say, c:Ed, CANNOT work (and the culprit is NOT Ed, of course !!!) This has NOTHING to do with the fact Ambient supports MIME types, and should be addressed ASAP IMHO. Thanks.

Discussion


Log in to post a comment.

MongoDB Logo MongoDB