Show Posts
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Hey there, it works fine so far
Only improvement I've been thinking of would be to have a longer variable history, perhaps with vertical scrolling.-ConstanceJill (November 14, 2024, 11:45 AM)
If you are changing the directory of each screenshot after each capture it could be this highlighted option under misc tweaks maybe...]-hamradio (October 15, 2024, 05:36 PM)
Bullseye!
Thank you hamradio! That is it and as soon as you pointed it out, I remembered setting it years ago.
This might say something about why I couldn't find it. I've been a licensed ham for about 57 years. My age is showing and then some.
Thank you again to you and to Ath and to Mouser!-SuperMan (October 15, 2024, 07:35 PM)
It did take me a few minutes of tinkering to figure it out looking thru options and experimenting since I hardly use that button. Also neat on you being a licensed ham as well.
In the Preferences screen, there's a page full of 'Post capture options' to choose from. Most likely you've set one of the options there that's causing this behavior, maybe a Commandline tool?-Ath (October 14, 2024, 01:17 PM)
Thank you for your response.
Yes, I felt sure it must be on that list too but I have already studied the Capture and Post Capture options and did not see it.
I should mention it happens when using the "Save Image As" button on the post capture pop-up dialog. After you select the folder and save it, the file manager pops up. I can't find any way to stop the file manager from launching after it saves, but unless my memory is failing (which is possible) I could swear I once had it set so it did not do that and changed it... some years ago.
I don't think it has to do with a command line... can probably rule that out.-SuperMan (October 14, 2024, 06:54 PM)
Hello!
I think I found a bug (in version 2.1.0 build 73 beta RC1) : after pressing F2 to open the layout editor, if some of the buttons in the layout are disabled, and the user selects a button in the list, then clicks "Move left" or "Move right" to change that button's position, then the number of lines that this button is moved up or down isn't 1 for each click, but seems to be affected by how many disabled buttons exist in the direction which the selected button is being moved towards.
Additional information: I can't reproduce this with either version 2.0.6 or 2.1.0 build 25 beta, which I have kept on hand, so the problem must have been introduced since then.
Edited again: it may require to have more than 2 disabled buttons for the issue to happen.-ConstanceJill (August 27, 2024, 09:59 AM)
I don't think x/y coordinates exists but here is a check for you to make sure the value in screenshot isn't set to a low value (value of 0 = invisible as noted in the window) making it invisible to the eye. Even with that value at 0 if you hover over the correct place (should be the very top and the center of screen if docked to edge of screen) it will still show the bar it just wont show the place to hover to show it. Another to check is that last checkbox in quick capture bar portion of the settings page highlighted incase it is displaying off screen maybe docking it will get it to show back up if it is unchecked.-hamradio (July 12, 2024, 02:07 PM)
Thanks for the quick reply. As (hopefully) shown here, my settings look to me like they should be working correctly - transparency was 255, changed it to 250 for giggles, no change. I had the default set to dock to the edge, but just now unchecked that box and applied changes, then checked the box again and applied changes. No luck, quick bar still isn't visible and doesn't appear when my mouse slides across the top of any one of my monitors - I've tried all 3.
[ Invalid Attachment ]-AzureToad (July 12, 2024, 02:51 PM)
Is there an .INI or .CONFIG file that specifies the X/Y coordinates for where the Quick-Capture Bar is located? I've enable and disabled that item by right-clicking the systray icon, but it's not appearing anywhere for me. I have 3 monitors and have not changed the primary monitor nor resolution. I'm wondering if it's docking off-screen somewhere?-AzureToad (July 12, 2024, 11:07 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.-ConstanceJill (July 07, 2024, 06:00 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.-ConstanceJill (June 20, 2024, 11:23 AM)
Ah! The button with the red "X." I often use the button next to it; I must have hit the X by accident. Thanks again!-tigerdg (May 30, 2024, 06:06 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)
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.pngWhen trying to run that command, I'm met with the following error message:
Application: ping.exe
Application Arguments :-t <var>
Start in:
Button Caption: Ping -t
Command Window : Skip (Direct Launch)
Ignore : Variable WhitespaceLaunch 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)
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)
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)
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 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).Okay I will see if I can track the mystery down before I request more info.-ConstanceJill (May 10, 2024, 04:42 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'm wondering if having it hide as long as no button uses the variable may be confusing for new users that didn't read about the feature first, especially if it's hidden when they start a new layout (which by default would be empty), or if they just start by making one such button and then the field disappears.
Maybe having it just be a toggleable option for each layout would keep it more simple (also when it comes to maintaining the code, even though I guess that's not for me to worry about).-ConstanceJill (May 07, 2024, 02:31 AM)
Well I'm sure yet if that's a good idea, but I've been thinking, perhaps it would be nice to have a layout-related option that would allow to hide the Variable field and Favorites menu, in case someone intends to use that layout specifically for shortcut type links that do not require any input?-ConstanceJill (May 02, 2024, 10:17 AM)
