QuickSnap : Released Oct 12, 2006

Blue · Post by **Blue** » Sun Oct 08, 2006 10:18 pm

in Procedure LoadPreferences()

shouldn't the default values (i.e. the first 5 lines ) get re-initialized in the ELSE clause of the statement ?
Since they're global variables anyway, the compiler wont get upset.

Now that you're reading the "My Pictures" path from the registry, it makes no big difference, but that re-initialization is the reason why in build pre-0.960 the ending backslash kept disappearing on me.

netmaestro · Post by **netmaestro** » Sun Oct 08, 2006 10:27 pm

Image was not getting saved if:

- "show window contents while dragging" was off
- you were in right-click, or outlined mode
- you had moved the window
- you saved the image with the keyboard shortcut

This bug is fixed, current build is 0.969

The LoadPreferences logic looks ok to me, there's no point in initializing it twice. There's no reason for the backslash to disappear that I can see.

Blue · Post by **Blue** » Mon Oct 09, 2006 1:36 am

netmaestro wrote:[...]The LoadPreferences logic looks ok to me, there's no point in initializing it twice

My point exactly!
I was wondering whether you aren't, in fact, initializing the variables twice:
(1) Upon entry in the procedure, everything gets initialized ipso facto. Then...
(2) a. if the ini file exits, it is read and the variables get initialized again by the content saved in this ini file.
This is the most frequent case, once a user has used the app.
(2) b. if the ini file does not exist, it gets create; the variables' values get saved.

Blue · Post by **Blue** » Mon Oct 09, 2006 2:08 am

netmaestro wrote:Image was not getting saved if:
[...]

I didn't come across any situation where the image was not being saved. That has worked impeccably since the 1st version I tried.

The problem I was referring to is something else. Since 0.965. in (right-click) outlined mode, ONCE the image has been saved, the screen remains dimmed with no visible clue showing that the work has been completed and that the app is now awaiting further input from the user.
Since Quicksnap doesn't return anything to the display, the user is left wondering whether the app has just died or is still busy saving the picture.

In windowed mode, the problem does not occur because of the window frame itself. Once the image has been saved, any higlight disappears, and everything goes dimmed. But the the window frame and the "Save" icon get redisplayed and remain clearly visible.
The message is crystal clear: the image has been duly saved and the app is ready for further input, awaiting the user's selection. Perfect.

I have pictures illustrating this. If it helps, I'll post them.

netmaestro · Post by **netmaestro** » Mon Oct 09, 2006 2:17 am

I can't reproduce that. It may be fixed already, not sure. Try with the latest build and see if it still happens.

Current build: 0.970

- Set the hotkey gadget to grab and keep focus when in the hotkey panel.

Blue · Post by **Blue** » Mon Oct 09, 2006 4:00 am

netmaestro wrote:I can't reproduce that. It may be fixed already, not sure.[...]

Working with build 970

Same old same.

In fact, I don't want you to think of what I've been describing in my recent posts as a bug. It's a shortcoming, but it's consistent with the regular operation of QuickSnap. It may just be that I'm not conveying clearly what the situation is. Difficult to solve it, in that case!

Let me try a different approach and step through the process with you.
OK.
(So I'm talking ONLY about the right-click outlined mode. Not the windowed other.)

In build pre-0.965 (if I remember well), the saved picture kept its dashed outline. With 965 onwards, you made a change that effectively removed that dashed border around the saved picture. And you also implemented a new visual clue to let the user know that the work was completed.
Somewhere, in that process, the visual clue that the app has returned to its waiting state disappeared.

So, if you ...
(1) set your system NOT to show the content of Windows as they are being moved around.
(2) start QuickSnap whichever way you prefer.
(3) right-click anywhere on the screen (once if inside the highlighted area, twice if outside) to enter "outline" mode.
(4) press the spacebar to save the image

The screen flickers, the "Save" icon appears and disappears, and your screen stays dimmed, with nothing else visible. The highlight has vanished (logical and consistent with the other mode: the area has just been saved to a file!). Your screen remains dimmed. No clue visible that QuickSnap ia alive and well and waiting for your input... Naturally, the moment you move the mouse, the highlight reappears since QuickSnap is expecting you to take a snapshot of some other area.

If you don't get that result, I'll be very surprised. And i won't say another word about it, ever again!

What's needed, in my humble opinion, is a different kind of comeback clue from Quicksnap in Outline mode. The dashed line of the outline should reappear, as by magic. But just the dashed line, not the highlighted content. The rapid appearance and disappearance of the "Save" icon is perfect to signal that the image has been saved. Don't change that.

Blue · Post by **Blue** » Mon Oct 09, 2006 4:50 am

*** Build 370 ***

A picture is worth a thousand words, I've been told.
So for your viewing pleasure, here are some snapshots of QuickSnap in action:

(1) right-click operation:
The whole screen is dimmed, but an area has been selected.
It is brightly highlighted.

(2) I now press the spacebar

(3.a ) QuickSnap has correctly saved the picture
It's now patiently waiting, somewhere behind this pretty dimmed screen, for further input !

(3.b ) What I think QuickSnap should be showing instead of the above
this nice dahed outline results from tricking Quicksnap, in a way.

CQFD: The above is proof positive that QuickSnap CAN produce the desired visual clue. It's now just a matter of coaxing it out of it at the right time.

netmaestro · Post by **netmaestro** » Mon Oct 09, 2006 5:31 am

OK, I was finally able to reproduce your results, and I found the reason. There was definitely a mistake in the logic, which should be corrected now. It should have uniform behavior in either mode now, with contents-dragging on or off. Could you test please?

Current build is 0.972

Blue · Post by **Blue** » Mon Oct 09, 2006 6:19 am

*** working on build 0.972 ***

netmaestro wrote:OK, I was finally able to reproduce your results, and I found the reason.

Great! The part that baffles me is why you weren't getting the same behaviour previously.

Perfect now
Youppilaï !

Oupsy: Of course, I now have to remember to revert to "Outline dragging only" in order to fully test this new build...

One moment please...
All righty. As I was saying: Youppilaï . It works well, no matter which dragging mode is active.

Now, tell me where the trouble was.......

Blue · Post by **Blue** » Mon Oct 09, 2006 6:45 am

Suggestions:

1. Make menu entry #5 "Open snapshots folder"
with RunProgram(folder$) as the command
and Poof! instant access to our saved pics !

2. Control rather than Alt as the arrow keys modifier to down-size the selection area.

3. If you ever get tired of the name QuickSnap, use SnapSmart.
That wouldn't be an exageration !

netmaestro · Post by **netmaestro** » Mon Oct 09, 2006 8:23 am

New version with a couple of changes:

- Selection rectangle shrink keys are now Ctrl+Arrow instead of Alt+Arrow

- Hotkey gadget now contains the currently set hotkey

- Until I figure out how to get the text out of a Hot key control, the hotkey status line on the main prefs page is discontinued. It has to be possible, and when I figure it out I'll put it back, but there's no point in having it when it's wrong half the time. You have to tab over to the Hotkey panel to see the current setting for now.

- New menu item "Snapshots Folder" opens up your save folder

Current build is 0.976 (and it's firming up nicely..)

mskuma · Post by **mskuma** » Mon Oct 09, 2006 11:53 am

I don't really understand the need for right-mouse click to switch to the dashed-border view. Why not simply (temporarily) change to the dashed-border view whenever you hold down the left-mouse button to drag? That would be more intuitive for the user I think. (edit: Same could be done when clicking & dragging out the size of the box from the corners - or maybe just use the dashed border from the outset?).

I still require two presses of the hotkey to bring up the capture window - does anyone else see this behaviour?

Thanks for honing & polishing.

Blue · Post by **Blue** » Mon Oct 09, 2006 4:03 pm

mskuma wrote:[...]Why not simply (temporarily) change to the dashed-border view whenever you hold down the left-mouse button to drag? That would be more intuitive for the user I think.

I think that's a good point.

I've been so immersed in getting the kinks out that I forgot to wonder why. It's kind of cute to have 2 modes, but to what advantage ?

[some time later...]

Forget I said that. I like having both modes available.
For large areas, the windowed mode is good enough, practical and visually informative. But for small ones, particularly very mall ones, I prefer to switch to the outlined mode. I find it more useful and better adapted. I think both modes should remain. If someone doesn't know or care about the outlined mode, he'll simply not use it. Which is rthe case with all software anyway: not everybody uses all the features all the time; one tends to develop a habit of using certain featues, which does not imply that the unused ones should disappear.
For my way of using the software, the presence of the outlined mode is a big PLUS, a very nice distinguishing and useful feature.
Of course, those aren't necessarily facts; they're an opinion. And I share it !

Blue · Post by **Blue** » Mon Oct 09, 2006 4:29 pm

netmaestro wrote:New version with a couple of changes:
Current build is 0.976 (and it's firming up nicely..)

Agreed. It's looking great.

As for the hotkey, it's definitely an improvement that the input box now displays the currently active one.

netmaestro · Post by **netmaestro** » Mon Oct 09, 2006 6:56 pm

A separate outlined mode that's persistent without a key being held down is quite important. You really see the advantage when you're doing fine adjustments, especially on a small rectangle. Remember, for expansions and shrinks, it's already a two-key combination. A third mousebutton to maintain outlined mode would be unworkable.