Page 2 of 2
Re: sGrab specifying the output file spec
Posted: Mon May 19, 2014 12:46 am
by tonyw
You CAN read the current contents of a string gadget after the user has left it by clicking somewhere else. I do it in most of my applications.
IIRC, the way it works by default, you only get a notification when the user presses the Enter key whilst in the gadget. You have to remember the "last gadget ID", and compare it with the "current gadget ID": if the "last" is one of your string gadgets, go back and read the current string. It's not rocket surgery, but some programmers are lazy.
Re: sGrab specifying the output file spec
Posted: Mon May 19, 2014 7:39 pm
by trixie
@tonyw
It's not rocket surgery, but some programmers are lazy.
If the desired behaviour indeed is that after being abandoned, the string gadget restores its contents to whatever there was before the unconfirmed edit, then the restoring should IMHO be performed by the gadget and not by the programmer.
Re: sGrab specifying the output file spec
Posted: Tue May 20, 2014 6:40 am
by ggw
MichaelMerkel wrote:Raziel wrote:...
I'm using
Store-path:{TITLE}_{NUMBER}.{TYPE}
in SGrabs main window under "File" and have never ever overwritten anything by accident, because SGrab is smart enough to check if there's a file with the same name and simply progress to the next number
i also use this. and if i need the file to be saved somewhere i rename and copy it to wherever i like.
regards...
michael
I will go with that. I don't mind typing to change the name after the fact. Usually the title is enough for me to clearly remember which grab it is the name of. That and the date, I am very chronologically oriented.
Thanks.
Re: sGrab specifying the output file spec
Posted: Tue May 20, 2014 6:51 am
by ggw
trixie wrote:@tonyw
It's not rocket surgery, but some programmers are lazy.
If the desired behaviour indeed is that after being abandoned, the string gadget restores its contents to whatever there was before the unconfirmed edit, then the restoring should IMHO be performed by the gadget and not by the programmer.
In so many applications it is the "confirmation of contents" that then causes further action (if all other entries also have confirmation) so it becomes awkward to change your mind about other entries (based on what you /just/ typed and confirmed).
The web browsing constraints and plethora of hurried programmers has ruined any strong sense of what to expect if THE confirmation leads to another (reformed) page.
Michael's ideas will take some thinkng about the pros and cons of those couple ideas.
Re: sGrab specifying the output file spec
Posted: Sun May 25, 2014 8:43 am
by marko
michael wrote:
and is the good-working software in that case undoing the typed in string content and displaying the "correct" input again?
or is the "not-conformed" content still visible in that case?
i actually guess the latter. which makes it, well, broken in my opinion. *if* not pressing enter or whatever is a cancel of input the content needs to reflect that.
+1
Well, yes, broken in my opinion too.
Re: sGrab specifying the output file spec
Posted: Sat Jul 26, 2014 11:17 pm
by Lio
SnapIT took over the job from SGrab, please try it !