I was entering the latest range session velocities and fat fingered the keyboard and a "/" was entered into the number field. I got following error...

Parse error
SafeStr2Double failure [103/]

This is probably no biggie as long as I keep my fingers where they belong. The data entry routine must not validate the string entered.

On another note, I just entered shot string data for about about 100 targets this session. One thing that has been bugging me and has gotten downright annoying is the fact that the enter key doesn't work for accepting data in many of the program entry fields, especially shot velocity. How Come? I have to enter the number and then grab the mouse every time to accept the number when a simple press of the return key should handle it. This creates a lot of extra hand motion between the keyboard (on my lap) and the mouse (on the desk). It probably works fine for lefties though.

Thanks
SS

matey thats getting close to nit picking in my book!!

yep.

For light use I can see where it's not a big issue but when you enter 100 10 shot strings (1000 numbers) I don't think it's nit picking at all. Then go back thru and edit a few of them. Try it and see if you still disagree.

In the comments section Enter works fine, other places (such as the session name or just about any text entry box) one would have to remember to use the Tab key instead of the Enter key.

Just about every other software application uses the return key to accept data entry so I was surprised this one doesn't. I'm just trying to point out ways to make the program a little more consistent and work better. This could turn out to be nothing more than a properties setting in the source code.

nit picking and attention to detail are very similar in my book.
besides.... they don't call me anal al for nothing.

SyberShooter wrote:

The data entry routine must not validate the string entered.

Actually that is the validation function and it did properly detect that "103/" isnt a proper number.

I could always try and parse it and turn it into a valid number, but odds are it wont be the number the user really meant to enter. Perhaps I need to change it slightly so its a bit more graceful when it detects an error, but for the most part it is doing what it should be doing.


-DallanC

SyberShooter wrote:

Just about every other software application uses the return key to accept data entry so I was surprised this one doesn't. I'm just trying to point out ways to make the program a little more consistent and work better. This could turn out to be nothing more than a properties setting in the source code.

Lemme look into this. Currently all entry is "realtime" but I see your point.


-DallanC

if it should be ok for "lefties" heres a suggestion. put your mouse on the other side of your keyboard when doing your data. it may help!

I wish that actually worked Elvis...I have tried using my mouse with the left hand and it just don't happen mate...I am a quamby with my left hand.

I can see Syber's point mate...it would be much easier and quicker to be simply able to hit the ENTER key. I near went crazy entering about 50 shots in the old version of PB, so I reckon I would be a jibbering wreck...even worse than I am anyway...after entering 1000 shots. I don't even want to think about that to be honest.

Cheers, Vince

DallanC wrote:

SyberShooter wrote: The data entry routine must not validate the string entered. Actually that is the validation function and it did properly detect that "103/" isnt a proper number. I could always try and parse it and turn it into a valid number, but odds are it wont be the number the user really meant to enter. Perhaps I need to change it slightly so its a bit more graceful when it detects an error, but for the most part it is doing what it should be doing. -DallanC

Duh ! where is that smak head icon... I should have recognised that the first 3 # were from my velocity and not an error code. yeah, a little more descriptive error message might be good, along the lines of " hey stupid, quit fat fingering the data" would work for me.


We're in Hawaii at the moment so i can't banter with the crew but I probably use PB differently than most people so have a higher than normal data entry point of view. We will be back in a week and I can do more detail on how I use PB but basically is is in load development so I have lots of targets.
al

SyberShooter wrote:

DallanC wrote: SyberShooter wrote: The data entry routine must not validate the string entered. Actually that is the validation function and it did properly detect that "103/" isnt a proper number. I could always try and parse it and turn it into a valid number, but odds are it wont be the number the user really meant to enter. Perhaps I need to change it slightly so its a bit more graceful when it detects an error, but for the most part it is doing what it should be doing. -DallanC Duh ! where is that smak head icon... I should have recognised that the first 3 # were from my velocity and not an error code. yeah, a little more descriptive error message might be good, along the lines of " hey stupid, quit fat fingering the data" would work for me. We're in Hawaii at the moment so i can't banter with the crew but I probably use PB differently than most people so have a higher than normal data entry point of view. We will be back in a week and I can do more detail on how I use PB but basically is is in load development so I have lots of targets. al

Cheers, Vince

good on ya lad. if we could find that button we all would be wearing it out.

DallanC wrote:

SyberShooter wrote: Just about every other software application uses the return key to accept data entry so I was surprised this one doesn't. I'm just trying to point out ways to make the program a little more consistent and work better. This could turn out to be nothing more than a properties setting in the source code. Lemme look into this. Currently all entry is "realtime" but I see your point. -DallanC

Ok that was rediculously hard to fix, but I have it "tabbing" to the next exit control when you hit "Enter".

It should have been litterally a 1 line fix but in this case it got into a circular logic issue and kept setting focus to itself (actually it would call to set the Text Label above the edit box as focused but because you cant make a label have focus, it would set focus back to the stupid edit box. Curse you microsoft and your lousy form control flow!

I R OUTSMAHTED IT THOUGH!


-DallanC

good on ya Dallan a great job as always.

DallanC wrote:

Ok that was rediculously hard to fix, but I have it "tabbing" to the next exit control when you hit "Enter". It should have been litterally a 1 line fix but in this case it got into a circular logic issue and kept setting focus to itself (actually it would call to set the Text Label above the edit box as focused but because you cant make a label have focus, it would set focus back to the stupid edit box. Curse you microsoft and your lousy form control flow! I R OUTSMAHTED IT THOUGH! -DallanC

It would have just worked if you had used Perl!

PERL lol... I've written alot of stuff in Perl. The problem is you come back to it 6 months later and you cant read it to figure out what it does

New version coming sometime later today btw.

-DallanC