Author Topic: NANY 2013 Release: Customizable Remote Administration Panel (CRAP) (Read 118175 times)

hamradio · « **Reply #100 on:** April 01, 2024, 10:12 AM »

Aww, that's the one I was using on my work computer lately
BTW is it possible for the user to make custom themes, or are we restricted to usng the ones that the program ships with?
-ConstanceJill (April 01, 2024, 03:23 AM)

The new “Dark” theme I did for another program when I was reviewing the themes looked extremely close to the old black. Only some of the colors didn’t look as rough around some parts so you might like that one.

It’s not in at this time for custom color/colors by the user but I have slowly been looking into how I think would be the best way to fit that in.

hamradio · « **Reply #101 on:** April 01, 2024, 07:43 PM »

Now that I am on the desktop...I made a comparison for you.

Your Current Black Theme

NANY 2013 Release: Customizable Remote Administration Panel (CRAP)

NANY 2013 Release: Customizable Remote Administration Panel (CRAP)

The New "Dark" Theme

NANY 2013 Release: Customizable Remote Administration Panel (CRAP)

NANY 2013 Release: Customizable Remote Administration Panel (CRAP)

That said if you still would like the current black one too I will leave it added back as a legacy style.

ConstanceJill · « **Reply #102 on:** April 02, 2024, 05:36 AM »

OK, it does seem better especially since the taskbar is dark too

Would be nice if the text fields could have a dark background (and probably some lighter shade of gray text for a good contrast) too

oblivion · « **Reply #103 on:** April 02, 2024, 08:30 AM »

Here’s my reasoning for the application launch mode. With the command line window the command is all arguments side. If I am going to skip it then I need a reliable way to tell what the executable is without dealing with the arguments side of things.
-hamradio (March 31, 2024, 08:47 AM)

There were, I think, some commands that took a lot of tinkering to make work properly -- and there are definitely some where the command window should be left open as well as some that don't.

I think I made most things work by either using start /b or not -- the remote desktop example I documented in the help is one where it was needed, but -- and I think it's down to Microsoft rather than anything else! -- expecting consistency is possibly a step too far!

I thought I'd left a note on here a few days ago to help with updating the help, if it's needed, for the new version, but I don't see the message so I expect I abandoned it accidentally

Anyhoo -- I'm still using CRAP only on a Windows 10 machine, but that doesn't mean I don't have Win11 available to test on if it's useful!

hamradio · « **Reply #104 on:** April 02, 2024, 10:26 AM »

OK, it does seem better especially since the taskbar is dark too
Would be nice if the text fields could have a dark background (and probably some lighter shade of gray text for a good contrast) too
-ConstanceJill (April 02, 2024, 05:36 AM)

Yeah I have to see if there is a fix for those as they flicker pretty bad when I try to do color related things to those combo boxes on the main window.

There were, I think, some commands that took a lot of tinkering to make work properly -- and there are definitely some where the command window should be left open as well as some that don't.

I think I made most things work by either using start /b or not -- the remote desktop example I documented in the help is one where it was needed, but -- and I think it's down to Microsoft rather than anything else! -- expecting consistency is possibly a step too far!

I thought I'd left a note on here a few days ago to help with updating the help, if it's needed, for the new version, but I don't see the message so I expect I abandoned it accidentally

Anyhoo -- I'm still using CRAP only on a Windows 10 machine, but that doesn't mean I don't have Win11 available to test on if it's useful!
-oblivion (April 02, 2024, 08:30 AM)

Yeah definitely seems like weird behavior from command line on the toggle to keep it open. Thanks for the offer on help file too will keep it in mind as get closer to letting it out.

ConstanceJill · « **Reply #105 on:** April 02, 2024, 12:17 PM »

Hmm to elaborate on the topic of the command line window, what I've been experiencing does not seem to me like an issue with the option to keep it open or not after a command ended, but rather, it's pretty much like the normal behavior of batch files: they just don't go to the next line until the current command has completed, which in the case of most executable means, until their process has ended.

And so if you use cmd.exe to run a GUI mode program such as the RDP client, Notepad, Firefox… then that CMD window just stays there until you close that GUI program — or manually close the cmd window itself.
The solution to that issue would be, IMHO, to have CRAP run the command which the button is set for "directly", instead of calling cmd.

hamradio · « **Reply #106 on:** April 02, 2024, 12:57 PM »

Hmm to elaborate on the topic of the command line window, what I've been experiencing does not seem to me like an issue with the option to keep it open or not after a command ended, but rather, it's pretty much like the normal behavior of batch files: they just don't go to the next line until the current command has completed, which in the case of most executable means, until their process has ended.

And so if you use cmd.exe to run a GUI mode program such as the RDP client, Notepad, Firefox… then that CMD window just stays there until you close that GUI program — or manually close the cmd window itself.
The solution to that issue would be, IMHO, to have CRAP run the command which the button is set for "directly", instead of calling cmd.
-ConstanceJill (April 02, 2024, 12:17 PM)

I would tend to agree but for whatever reason on my windows 10 7+ year old computer (with original parts) before I upgraded on my terms would as far as I can remember appeared to close after launching executables with the right command line option. The new computer however it won’t. Should be fixed now tho hopefully with what you said for the solution as that is what the next version will do with the skip option just it will need the arguments moved down to work. I do change the label caption of the text boxes to account for that depending on if skip is selected or not to tell that.

hamradio · « **Reply #107 on:** April 02, 2024, 09:10 PM »

OK, it does seem better especially since the taskbar is dark too
Would be nice if the text fields could have a dark background (and probably some lighter shade of gray text for a good contrast) too
-ConstanceJill (April 02, 2024, 05:36 AM)

So I have been thinking...I could probably move away from the combo box for selecting favorites as well which would take care of one of the white boxes on the main window. Would then need to write a edit favorite dialog perhaps with the list of favorites there or a shift + click / ctrl + click to do the edit/delete work which would be like I have in the layouts menu. I could also probably do a shortcut key that would call up the favorites menu then too. Plus allow for other ideas down the road like maybe even a "folder" system for them to where you could organize them. The dropdown would also take up less of the main window space and I would remove the ability to put the favorites bar on new line from the preferences...but might have a few drawbacks as well...therefore what are the thoughts on that ConstanceJill and oblivion?

What it could look like only with a few other tweaks to it obviously just a rough draft to show atm...

NANY 2013 Release: Customizable Remote Administration Panel (CRAP)

ConstanceJill · « **Reply #108 on:** April 03, 2024, 06:13 AM »

Should be fine I guess. I'd prefer the text contents (typically a hostname) to be visible before selecting the favourite, but I suppose I could always include it in the description myself.

hamradio · « **Reply #109 on:** April 03, 2024, 11:56 AM »

Should be fine I guess. I'd prefer the text contents (typically a hostname) to be visible before selecting the favourite, but I suppose I could always include it in the description myself.
-ConstanceJill (April 03, 2024, 06:13 AM)

The tooltip of each menu item would also show that data. Which is one thing that the combo box doesn't show currently for each item.

hamradio · « **Reply #110 on:** April 03, 2024, 10:34 PM »

Would be nice if the text fields could have a dark background (and probably some lighter shade of gray text for a good contrast) too
-ConstanceJill (April 02, 2024, 05:36 AM)

Another thought on this...I could always test a toolstrip textbox with different colors for the variable entry and if it doesn't have the flickering issue I could convert to it for the variable entry as well if you think it wouldn't be too much hassle being a separate dropdown that is not attached the launch entry control for the history.

ConstanceJill · « **Reply #111 on:** April 04, 2024, 06:13 AM »

Sorry, I'm not quite sure what that means / what it looks like, and the search results I get seem to be more about the code to implement one…
I don't really mind the current text input fields by the way, so if it's too much work to just have their background color changed by the theme, please don't feel pressured to change that.

hamradio · « **Reply #112 on:** April 04, 2024, 12:42 PM »

If would like to try a public beta it can be got from the following link.

CRAP beta build

Notes:
I haven't got the drag and drop in for adding entries currently but the new favorites menu, skip command window, and adding the exe to the command prefix/application line if it is empty is in.
The title bar should/will only change color for dark themes in Win10+.
Ctrl+F will bring up the favorites menu currently if you want to use the keyboard.
If you don't want confirmation of deletion of a favorite press both shift+control before clicking one currently.

ConstanceJill · « **Reply #113 on:** April 04, 2024, 01:17 PM »

I'm getting a 404 when trying the link.

hamradio · « **Reply #114 on:** April 04, 2024, 02:13 PM »

I'm getting a 404 when trying the link.
-ConstanceJill (April 04, 2024, 01:17 PM)

See if it will go to it now think I forgot to click OK on one option in the admin panel.

ConstanceJill · « **Reply #115 on:** April 04, 2024, 03:13 PM »

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

ConstanceJill · « **Reply #116 on:** April 05, 2024, 04:21 AM »

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 · « **Reply #117 on:** April 05, 2024, 11:41 AM »

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)

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 · « **Reply #118 on:** April 06, 2024, 02:23 AM »

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)

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 · « **Reply #119 on:** April 06, 2024, 09:15 PM »

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)

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)

So which way would you prefer for it to be?

ConstanceJill · « **Reply #120 on:** April 07, 2024, 02:29 AM »

I think having the contents of "Application Arguments (optional)" defaulting to <var> (with the text being visible in the field), and adding the validation/warning at the time of saving the button in case the user removed <var> from there without checking "Ignore Variable Text" would make more sense.

hamradio · « **Reply #121 on:** April 07, 2024, 03:16 PM »

I think having the contents of "Application Arguments (optional)" defaulting to <var> (with the text being visible in the field), and adding the validation/warning at the time of saving the button in case the user removed <var> from there without checking "Ignore Variable Text" would make more sense.
-ConstanceJill (April 07, 2024, 02:29 AM)

So I am thinking something like this where it offers to set the checkbox of ignore variable text to true and add/edit or if no is clicked let you make necessary changes manually. Thoughts on the message contents/actions with how I set it up?

Feel free to suggest message edits as well as that is a rough draft currently.

ConstanceJill · « **Reply #122 on:** April 08, 2024, 02:29 AM »

Your current proposal for the message seems self explanatory enough to me

oblivion · « **Reply #123 on:** April 08, 2024, 04:21 AM »

The new CRAP is cheerfully working with my favorites / layouts etc in Windows 10. I definitely like the new favorites menu and dark mode.

I will experiment with the CMD-related settings as I go.

The edit and delete favorites buttons -- will they return?

oblivion · « **Reply #124 on:** April 08, 2024, 04:57 AM »

An initial note. Quite a few of my CRAP buttons use "runas" so I can use an admin account to run things from a non-admin login.

If I use the new "skip command window" option, I have to set the application as runas.exe and pass everything else (the actual program as well as the user account details) to the command as a lengthy parameter.

It works -- of course! -- and is exactly as the command actually works but it means, for me at least, most of my buttons -- those that don't need a results window left open, anyway -- are going to be runas.exe with the actual program I'm running (along with its parameters) demoted to a parameter of runas.

Not sure if this matters or not! I haven't found an error with it, just a change of focus.