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

hamradio · « **Reply #150 on:** May 10, 2024, 04:30 PM »

Hey there,

I've been using 2.1.0 beta 67 today and I've run into a kinda new issue.

With previous versions it already happened from time to time that, while launching a command with a button, I'd get the attached error message. It was not a very common occurrence and the command ran anyway with no other issue, so I didn't mind much.
What's new with this latest beta is that, after running into that error, now I can't seem to interact with the Variable field any more. I can open the drop-down list (which appears to be empty while it shouldn't be) but can't get the blinking cursor to appear inside the field itself, or select the current value by double clicking it, or even replace it by selecting a favorite… seems the only way out is to exit CRAP and restart it.
-ConstanceJill (May 10, 2024, 11:43 AM)

Same command each time or different? If same might have to investigate that command myself if possible to debug.

ConstanceJill · « **Reply #151 on:** May 10, 2024, 04:42 PM »

I can't tell for sure but I think so far I mostly had it happen with the ping command, which happens to be the first in my layout (in case that's relevant).

hamradio · « **Reply #152 on:** May 10, 2024, 05:08 PM »

I can't tell for sure but I think so far I mostly had it happen with the ping command, which happens to be the first in my layout (in case that's relevant).
-ConstanceJill (May 10, 2024, 04:42 PM)

Okay I will see if I can track the mystery down before I request more info.

hamradio · « **Reply #153 on:** May 10, 2024, 05:22 PM »

Hey there,

I've been using 2.1.0 beta 67 today and I've run into a kinda new issue.

With previous versions it already happened from time to time that, while launching a command with a button, I'd get the attached error message. It was not a very common occurrence and the command ran anyway with no other issue, so I didn't mind much.
What's new with this latest beta is that, after running into that error, now I can't seem to interact with the Variable field any more. I can open the drop-down list (which appears to be empty while it shouldn't be) but can't get the blinking cursor to appear inside the field itself, or select the current value by double clicking it, or even replace it by selecting a favorite… seems the only way out is to exit CRAP and restart it.
-ConstanceJill (May 10, 2024, 11:43 AM)

I think I have traced to how the history works so I don't think it is command related at all in the end based on the translation of that message. So I should be able to fix.

Edit: Thanks for reporting it. Pretty sure I have tracked the issue down now to fix.

hamradio · « **Reply #154 on:** May 10, 2024, 05:49 PM »

2.1.0 build 68 BETA BUILD is on the beta page for download.

What's New/Modifications
A couple of bugs fixed.

As always let me know if bugs are found no matter how BIG or small of a bug it may be.
Also let me know your thoughts/feedback on this program/build in general even if no bugs are found...

Try the build 68 that I just uploaded and see if the issue is resolved for you.

ConstanceJill · « **Reply #155 on:** May 11, 2024, 01:58 AM »

Thanks!
I'll be on vacation for 2 weeks so I'll probably be using CRAP a lot less during that time as I mostly use it for work, but I'll let you know as soon as possible.

ConstanceJill · « **Reply #156 on:** May 14, 2024, 03:38 AM »

Hello there.

I unzipped version 2.1.0 build 68 beta over my existing install on my home computer (which previously had build 60 beta) and got a few new bugs when using it to launch some (but not all) programs:

1 : It appears that, if the "Start in" field has the path within double quotes (for example, "D:\steam" ) then when clicking the button, instead of the program being started, I get the following error message:

Error while launching application.
Caractères non conformes dans le chemin d'accès.

That last line would translate back to english into something akin to "invalid characters in path"

I don't have the issue when making a new layout so I guess it's likely to only be an issue for the small niche of people who tried a previous beta where the Start in field was already a thing, or who would perhaps manually create such a button, but I feel that either the error message should be made more explicit, or perhaps the program should either automatically remove or ignore double quotes in that field — after testing, I can confirm they're not needed even if the program must be started in a folder that has spaces.

2 : I had a button with the following parameters:
Image file: <sysroot>System32\conhost.exe;0
Application: <sysroot>System32\conhost.exe
Start in: %userprofile%\desktop
Button Caption:\nCMD
Command Window: Skip
Ignore: Variable Text

With build 60 beta the program did run (albeit it started the program in the same folder where the shortcut to launch CRAP pointed it to start in, instead of the one I had specified in the button's properties), but now it gives me a different error instead (see attachment, the line in french would translate to "invalid folder name").
Removing the contents of the "Start in" field from the button, or making sure it doesn't use environment variables with "%", allows it to work again.

Another little thing: I noticed that, if the button caption starts with "\n" to avoid having the text appear too close to the icon, the "\n" also is displayed in the tooltip while hovering the button. While it's more accurate to have it show, I can't help but think it probably shouldn't be showing in the tooltip. However, it would probably be even better if the user could, under the global button properties, set a minimum spacing between the icon and text, so that there would be less need for "\n" in captions.

hamradio · « **Reply #157 on:** May 14, 2024, 04:13 PM »

Hello there.

I unzipped version 2.1.0 build 68 beta over my existing install on my home computer (which previously had build 60 beta) and got a few new bugs when using it to launch some (but not all) programs:

1 : It appears that, if the "Start in" field has the path within double quotes (for example, "D:\steam" ) then when clicking the button, instead of the program being started, I get the following error message:
Error while launching application.
Caractères non conformes dans le chemin d'accès.

That last line would translate back to english into something akin to "invalid characters in path"

I don't have the issue when making a new layout so I guess it's likely to only be an issue for the small niche of people who tried a previous beta where the Start in field was already a thing, or who would perhaps manually create such a button, but I feel that either the error message should be made more explicit, or perhaps the program should either automatically remove or ignore double quotes in that field — after testing, I can confirm they're not needed even if the program must be started in a folder that has spaces.

2 : I had a button with the following parameters:
Image file: <sysroot>System32\conhost.exe;0
Application: <sysroot>System32\conhost.exe
Start in: %userprofile%\desktop
Button Caption:\nCMD
Command Window: Skip
Ignore: Variable Text

With build 60 beta the program did run (albeit it started the program in the same folder where the shortcut to launch CRAP pointed it to start in, instead of the one I had specified in the button's properties), but now it gives me a different error instead (see attachment, the line in french would translate to "invalid folder name").
Removing the contents of the "Start in" field from the button, or making sure it doesn't use environment variables with "%", allows it to work again.

Another little thing: I noticed that, if the button caption starts with "\n" to avoid having the text appear too close to the icon, the "\n" also is displayed in the tooltip while hovering the button. While it's more accurate to have it show, I can't help but think it probably shouldn't be showing in the tooltip. However, it would probably be even better if the user could, under the global button properties, set a minimum spacing between the icon and text, so that there would be less need for "\n" in captions.
-ConstanceJill (May 14, 2024, 03:38 AM)

1. I have fixed in my local copy to where it should remove any sign of double quotes. (At launch phase)
2. Yeah it cannot handle environment variables like that in beta v2.1.0 b68 and previous but I have researched and made a small change to attempt to parse %userprofile% and others from the "start in" with no additional changes needed by you upon the next update. Also now checks to see if it still contains % after attempting to parse the environment variables and will cancel if still found after parsing what it can.

As for the last bit about caption I cannot tell it the space to use between icon and caption. Also make sure the \n isn't shown in the tooltip in button properties as I think in one beta it added them to the tooltip portion in a minor bug from the drag and drop as well and should be fixed though in current beta version.

Example of #2 when environment variables are parsed and the string still contains some that could not be replaced...

NANY 2013 Release: Customizable Remote Administration Panel (CRAP)

ConstanceJill · « **Reply #158 on:** May 15, 2024, 01:17 AM »

All right

I also noticed one other issue: I have this RAM drive program called OSFMount installed; and I drag and dropped its shortcut from my start menu to CRAP.

It requires admin rights to be ran, so Windows' User Account Control window usually pops up when starting it —and it did so indeed back when I was launching it from version 2.1.0 build 60 beta— however, in build 68 beta, CRAP only gives with an error message « L'opération demandée nécessite une élévation » (translated back to english: « The requested operation requires an elevation »). The UAC window does not appear and the program isn't ran.

hamradio · « **Reply #159 on:** May 15, 2024, 01:46 PM »

All right

I also noticed one other issue: I have this RAM drive program called OSFMount installed; and I drag and dropped its shortcut from my start menu to CRAP.

It requires admin rights to be ran, so Windows' User Account Control window usually pops up when starting it —and it did so indeed back when I was launching it from version 2.1.0 build 60 beta— however, in build 68 beta, CRAP only gives with an error message « L'opération demandée nécessite une élévation » (translated back to english: « The requested operation requires an elevation »). The UAC window does not appear and the program isn't ran.
-ConstanceJill (May 15, 2024, 01:17 AM)

Thanks! I changed one line of code back to the build 60 way (which is the only one that I changed that could have had an effect on it from my side)...so we shall see if it fixes it in the next one.

Also after much research the combo box non dropdown style should turn to the dark mode style of Win10+ and only on Win10+ along with of course when on either of the two dark themes.

hamradio · « **Reply #160 on:** May 16, 2024, 12:05 PM »

2.1.0 build 70 BETA - BETA Download Page

This might be the last beta this beta cycle before help gets polished and then a general release build if things are running smooth.

Added conversion of environment variables to the start in field (e.g %HOMEDRIVE%, %HOMEPATH% and others) when launched.
Note on #1: Launch will be cancelled if it still has environment variables that could not be converted with a message that should display all the environment variables that remain invalid.
Reverted to beta build 60 for a launch parameter.
Added a tweaks menu under preferences which will display on win11. Currently it is used only for you to choose what the corners of the application windows should be. (default, donotround, rounded, and roundedsmall). It will load and save the preference on a previous operating system but will only show the menu along with being effective when on win11.
The variable combobox should now display as the dark mode style when on win10+ and one of the dark themes chosen.
Other smaller bugs fixed, enhancements, optimizations.

As always let me know if bugs are found no matter how BIG or small of a bug it may be.
Also let me know your thoughts/feedback on this program in general even if no bugs are found...

ConstanceJill · « **Reply #161 on:** May 17, 2024, 06:07 AM »

Thanks!

So I extracted 2.1.0 build 70 BETA and tried running a few commands on my work computer, but I ran into a an error with a few of them.

For example, I have a button with the following settings :

Image File: <appdir>icons\Ping.png
Application: ping.exe
Application Arguments :-t <var>
Start in:
Button Caption: Ping -t
Command Window : Skip (Direct Launch)
Ignore : Variable Whitespace

When trying to run that command, I'm met with the following error message:

Launch cancelled. Application file listed bellow is missing.

ping.exe

Same problem with buttons that I set to direct launch mstsc.exe, explorer.exe or mmc.exe

From what I gathered, it would seem that, when using "Direct Launch" only, when the full path to the application is not specified, this version of the program tries to check if it finds the program in the PATH, but fails to find it.
However, it does find and launch successfully some third party executables that I've placed in other folders, which I added to my system PATH, without having their paths spelled out in the button settings.
I suspect that it probably has to do with the PATH relying on the %SystemRoot% environment variable for executables that ship with Windows (?)

Replacing the setting in the button with "%systemroot%\system32\ping.exe" also does not fix the problem, I have to put "C:\Windows" in place of "%systemroot%".

Another minor annoyance that I noticed is that, after editing a button, the contents of the Variable field is emptied.

hamradio · « **Reply #162 on:** May 17, 2024, 02:07 PM »

Thanks!

So I extracted 2.1.0 build 70 BETA and tried running a few commands on my work computer, but I ran into a an error with a few of them.

For example, I have a button with the following settings :

Image File: <appdir>icons\Ping.png
Application: ping.exe
Application Arguments :-t <var>
Start in:
Button Caption: Ping -t
Command Window : Skip (Direct Launch)
Ignore : Variable Whitespace
When trying to run that command, I'm met with the following error message:
Launch cancelled. Application file listed bellow is missing.

ping.exe

Same problem with buttons that I set to direct launch mstsc.exe, explorer.exe or mmc.exe

From what I gathered, it would seem that, when using "Direct Launch" only, when the full path to the application is not specified, this version of the program tries to check if it finds the program in the PATH, but fails to find it.
However, it does find and launch successfully some third party executables that I've placed in other folders, which I added to my system PATH, without having their paths spelled out in the button settings.
I suspect that it probably has to do with the PATH relying on the %SystemRoot% environment variable for executables that ship with Windows (?)

Replacing the setting in the button with "%systemroot%\system32\ping.exe" also does not fix the problem, I have to put "C:\Windows" in place of "%systemroot%".

Another minor annoyance that I noticed is that, after editing a button, the contents of the Variable field is emptied.
-ConstanceJill (May 17, 2024, 06:07 AM)

I will fix the annoyance. I will also remove the file exists check to let it catch files not found as before which should fix the other issue too.

hamradio · « **Reply #163 on:** May 17, 2024, 07:23 PM »

2.1.0 build 71 BETA - BETA Download Page
(Maybe last beta build before a general release build if things are appearing to be polished.)

1. Reverted the launch file exists check to the before method.
2. Fixed minor annoyance with variable field being cleared.
3. Added warning if a button uses the variable text and the variable bar is hidden. (Upon attempting to launch.)

Let me know if this one fixes the 2 above issues you mentioned.

ConstanceJill · « **Reply #164 on:** May 18, 2024, 01:37 AM »

Yep, looks like points 1 and 2 are fixed indeed, thanks!

I'll let you know if I find anything else.

hamradio · « **Reply #165 on:** May 18, 2024, 03:36 PM »

Yep, looks like points 1 and 2 are fixed indeed, thanks!
I'll let you know if I find anything else.
-ConstanceJill (May 18, 2024, 01:37 AM)

hamradio · « **Reply #166 on:** May 20, 2024, 07:16 PM »

I'm currently thinking early next week perhaps for the non beta release of this beta cycle as long as its running smoothly/no other ideas by then.

hamradio · « **Reply #167 on:** May 31, 2024, 02:20 PM »

FYI: It's just been too busy to post the release version this week.

ConstanceJill · « **Reply #168 on:** June 01, 2024, 12:41 PM »

No problem, I'm happy with the latest beta for now

I guess it would be nice if the person who made the help file could update it with contents about the new features for the release version, too.

oblivion · « **Reply #169 on:** June 18, 2024, 05:45 AM »

No problem, I'm happy with the latest beta for now
I guess it would be nice if the person who made the help file could update it with contents about the new features for the release version, too.
-ConstanceJill (June 01, 2024, 12:41 PM)

Sorry, I had a whole heap of stuff hit me at once and I haven't been paying attention recently.

I'll try to get caught up with the new stuff and update the help document that the help file was built from in the next few days.

Do you feel that my previous style (largely of worked examples) was a useful approach?

ConstanceJill · « **Reply #170 on:** June 19, 2024, 12:57 PM »

Yes, it seems fine to me

ConstanceJill · « **Reply #171 on:** June 20, 2024, 11:23 AM »

Hey I've just noticed a few minor things that I find just a little annoying:

1 - If, in the Variable text field, I select something from the Variable history, then click in the text field (thus unselecting the text), and then I press Ctrl+A to select all, then on the first attempt nothing seems to happen, and the second time I press Ctrl+A, the text field is cleared.

It seems to only happen with text I recalled from the history or, if I just entered that text into the field by typing it, only after using a button with that variable.

2 - clearing the variable history messes with the dark theme around the Variable text field and on the button to open the Variable history, either until the theme is replaced by another one and re-applied, or the program is restarted.

hamradio · « **Reply #172 on:** June 20, 2024, 07:29 PM »

Hey I've just noticed a few minor things that I find just a little annoying:

1 - If, in the Variable text field, I select something from the Variable history, then click in the text field (thus unselecting the text), and then I press Ctrl+A to select all, then on the first attempt nothing seems to happen, and the second time I press Ctrl+A, the text field is cleared.

It seems to only happen with text I recalled from the history or, if I just entered that text into the field by typing it, only after using a button with that variable.

2 - clearing the variable history messes with the dark theme around the Variable text field and on the button to open the Variable history, either until the theme is replaced by another one and re-applied, or the program is restarted.
-ConstanceJill (June 20, 2024, 11:23 AM)

#2 is fixed and I think I may have finally figured out the cause of #1 and fixed it.

Uploaded RC#1 as well with those 2 fixes to the beta page.

ConstanceJill · « **Reply #173 on:** June 21, 2024, 02:09 AM »

That was fast! Thanks, I'll be testing it today

ConstanceJill · « **Reply #174 on:** July 07, 2024, 06:00 AM »

Hey there, I've been using 2.1.0 build 73 RC1 since my previous message in my work setting and those 2 issues appear to be fixed indeed

I noticed that the about box still says "2.1.0 build 72" but the version number in the executable properties is correct (2.1.0.73).
Didn't run into any problem with it, though I must admit I didn't re-test every feature again.