Page 2 of 2

Re: Embedding command line parameters

Posted: 05 Mar 2010 08:34
by RalphM
I tried before to put some info in the title bar to identify different instances of XY (i.e. the local installed one on C:\ and a portable one on a removable drive)

So, yes, the titlebar being fully XY-var aware would be a nice addition for me.

Re: Embedding command line parameters

Posted: 05 Mar 2010 09:19
by admin
RalphM wrote:I tried before to put some info in the title bar to identify different instances of XY (i.e. the local installed one on C:\ and a portable one on a removable drive)

So, yes, the titlebar being fully XY-var aware would be a nice addition for me.
You could simply write "portable" into the titlebartemplate of your portable one.

Re: Embedding command line parameters

Posted: 05 Mar 2010 11:27
by RalphM
Not if both instances use a copy of the same ini.
If I used different ini's, I could name them appropriately, which would solve that problem as well, but I rather just create a copy of the whole XY installation on the removable drive...

Re: Embedding command line parameters

Posted: 05 Mar 2010 12:20
by admin
RalphM wrote:Not if both instances use a copy of the same ini.
If I used different ini's, I could name them appropriately, which would solve that problem as well, but I rather just create a copy of the whole XY installation on the removable drive...
I see. OK, I add the whole bunch of XY vars then. The whole thing is a non-documented tweak anyway...

Re: Embedding command line parameters

Posted: 05 Mar 2010 17:09
by TheQwerty
Kind of disappointing that you only made the command go one way....
I think there's much more use for an absolute to relative command in scripting, especially if you're trying to write scripts for the community that require some configuration.

Re: Embedding command line parameters

Posted: 05 Mar 2010 17:14
by admin
TheQwerty wrote:Kind of disappointing that you only made the command go one way....
I think there's much more use for an absolute to relative command in scripting, especially if you're trying to write scripts for the community that require some configuration.
I don't even have code for this in XY. :) Never ever used absolute to relative. Do you have an example?

Re: Embedding command line parameters

Posted: 05 Mar 2010 17:23
by TheQwerty
admin wrote:
TheQwerty wrote:Kind of disappointing that you only made the command go one way....
I think there's much more use for an absolute to relative command in scripting, especially if you're trying to write scripts for the community that require some configuration.
I don't even have code for this in XY. :) Never ever used absolute to relative. Do you have an example?
http://msdn.microsoft.com/en-us/library ... 85%29.aspx

The best use case for it is any of these scripts that require user configuration and ask for the path to an executable or location. They can then more easily use InputFolder/File to prompt the user for the path and this function to convert that path into a relative one that would work correctly when using XY portably.

Otherwise, it requires more complicated scripting to convert the path ourselves or an additional edit field to allow the user to make it a relative path themselves.

Re: Embedding command line parameters

Posted: 05 Mar 2010 21:52
by jacky
TheQwerty wrote:The best use case for it is any of these scripts that require user configuration and ask for the path to an executable or location. They can then more easily use InputFolder/File to prompt the user for the path and this function to convert that path into a relative one that would work correctly when using XY portably.

Otherwise, it requires more complicated scripting to convert the path ourselves or an additional edit field to allow the user to make it a relative path themselves.
Right(, that's why I have something like that in my common-jacky, both ways. [/shameful_plug]) Useful indeed for scrips to save paths relative and keep portability working.