DonationCoder.com Software > N.A.N.Y. 2013

NANY 2013 Release: Customizable Remote Administration Panel (CRAP)

<< < (24/36) > >>

ConstanceJill:
Download worked, thanks, I'll give it a try a bit later :)

ConstanceJill:
Hey there,

I've imported my work layout, settings and icons into a folder where I unzipped the beta version, which seemed to work fine as far as the import goes.
Favorites menu is fine too :)

Then I tested removing the start command on a few of my GUI driven apps and enabling the "Skip Command Window" option instead, moving all the parameters (when applicable) from the prefix towards the "Application Arguments" field, and indeed it launches the program with no unnecessary CMD window, which is nice :)

I did notice however that, for such buttons where the "Skip Command Window" option is enabled, if the following conditions are all met :
1 - I don't include the <var> parameter anywhere in the "Application Arguments (optional)" field
2 - the "Ignore Variable Text" checkbox is not checked
3 - there is some text in the "Variable" field of the main window

then, when the mouse cursor is over such a button, both the command preview in the status bar and the "Application Arguments:" line within the tooltip look as if the contents of Variable would be included, between the Application and its other arguments (if any are specified), yet the contents of the Variable is actually not included when clicking the button to run the command.

Now obviously I shouldn't forget to include the <var> in the arguments at the position where it's needed, but there still is an inconsistency between what the preview says and what the program does.

hamradio:
Hey there,

I've imported my work layout, settings and icons into a folder where I unzipped the beta version, which seemed to work fine as far as the import goes.
Favorites menu is fine too :)

Then I tested removing the start command on a few of my GUI driven apps and enabling the "Skip Command Window" option instead, moving all the parameters (when applicable) from the prefix towards the "Application Arguments" field, and indeed it launches the program with no unnecessary CMD window, which is nice :)

I did notice however that, for such buttons where the "Skip Command Window" option is enabled, if the following conditions are all met :
1 - I don't include the <var> parameter anywhere in the "Application Arguments (optional)" field
2 - the "Ignore Variable Text" checkbox is not checked
3 - there is some text in the "Variable" field of the main window

then, when the mouse cursor is over such a button, both the command preview in the status bar and the "Application Arguments:" line within the tooltip look as if the contents of Variable would be included, between the Application and its other arguments (if any are specified), yet the contents of the Variable is actually not included when clicking the button to run the command.

Now obviously I shouldn't forget to include the <var> in the arguments at the position where it's needed, but there still is an inconsistency between what the preview says and what the program does.
-ConstanceJill (April 05, 2024, 04:21 AM)
--- End quote ---

Thanks I will fix to where if arguments is left blank in the button properties that the variable provided that ignore variable text is not checked will work for the arguments. If you specify arguments then obviously use <var> to where you want the variable to be. Does that sound like the proper way you would expect?

Also I am testing the ability to have categories (no sub categories yet) and separators for favorites in my local copy...

ConstanceJill:
Thanks I will fix to where if arguments is left blank in the button properties that the variable provided that ignore variable text is not checked will work for the arguments. If you specify arguments then obviously use <var> to where you want the variable to be. Does that sound like the proper way you would expect?
-hamradio (April 05, 2024, 11:41 AM)
--- End quote ---
If I understand it right, provided that both the following conditions are met :
1 - "Ignore Variable Text" checkbox is not checked
2 - nothing is specified in the "Application Arguments (optional)" field
then CRAP would run the command with the contents of <var> as its only argument

Sounds fair enough.

Perhaps we may even add a validation such that, before a button can be saved, if the following conditions are all met :
- "Skip Command Window" is checked
- "Ignore Variable Text" is not checked
- <var> is not found anywhere within the arguments
then the program shall issue a warning?

Or maybe have the contents of "Application Arguments (optional)" default to "<var>" as long as "Ignore Variable Text" is not checked?

hamradio:
If I understand it right, provided that both the following conditions are met :
1 - "Ignore Variable Text" checkbox is not checked
2 - nothing is specified in the "Application Arguments (optional)" field
then CRAP would run the command with the contents of <var> as its only argument

Sounds fair enough.
-ConstanceJill (April 06, 2024, 02:23 AM)
--- End quote ---

Correct that is the way I was thinking when I wrote. As empty arguments would take into account any variable entered if ignore variable text wasn't checked.

That said you also mentioned...

Perhaps we may even add a validation such that, before a button can be saved, if the following conditions are all met :
- "Skip Command Window" is checked
- "Ignore Variable Text" is not checked
- <var> is not found anywhere within the arguments
then the program shall issue a warning?

Or maybe have the contents of "Application Arguments (optional)" default to "<var>" as long as "Ignore Variable Text" is not checked?
-ConstanceJill (April 06, 2024, 02:23 AM)
--- End quote ---

So which way would you prefer for it to be?

Navigation

[0] Message Index

[#] Next page

[*] Previous page