BUG: 4.0dSR1: CRASH erasing numeric in Guide Template Edit-Mode

JimTowler

(This report is against the 4.0d SR-!, so not a Beta as such. But posted here so the right eyes find this post.)

While editing the Template for a Guide, I get an exception when deleting the numerics in a UI input box.

To create the CRASH: Backspace as if to change the 30 to 5 per yellow highlight

Seems the application is attempting to compute the numeric value of <blank string>.

Please Logos:

Automated or human testing on all UIs
Add exception trapping and handling around all UIs
Trap and reset to "defaults" or something: Don't crash on bad input.

2821.Logos4Crash.txt

Find more posts tagged with

Comments

JimTowler

Workaround:

Highlight old numeric, then overwrite with new value, so field contains a numeric at all times.

Rosie Perera

Please Logos:

Automated or human testing on all UIs

Add exception trapping and handling around all UIs

Trap and reset to "defaults" or something: Don't crash on bad input.

+1 [Y]

Fred Chapman

https://community.logos.com/discussion/comment/148143#Comment_148143

I found and reported the same crash last night on this thread in the L4 forum http://community.logos.com/forums/t/19628.aspx

JimTowler

https://community.logos.com/discussion/comment/148170#Comment_148170

Fred,

Yes - I saw that just now. Same error here and as you reported too.

The error log clearly shows that the application is attempting to convert the blank string into a number, and can't do it.

I recreated a simple version of this in Visual Basic, and got the same exception crash converting a non-numeric string to a number. The fix was to wrap the line with TRY / CATCH and assign some useful default instead of crashing. It bothers me that Logos4 does not seem to have more exception handling around anything that might be expected to fail or have user-inputs that could be invalid.

I see that 4.0d SR-1 has a fix for this same POOR CODING in a different place in the aplication.

Try
number = CInt(someString)
Catch
number = 0
End Try

NetworkGeek

https://community.logos.com/discussion/comment/148175#Comment_148175

The same problem, not catching catastrophic errors that result from a user action, was reported here:

http://community.logos.com/forums/p/19427/146399.aspx#146399

and here:

http://community.logos.com/forums/p/16468/124986.aspx#124986

Melissa said in the first thread that development is working on it. Hopefully they will remove crashes that come from user activity, sounds like a good code review of the software would ferret out a lot of them...

Dave Hooton

To create the CRASH: Backspace as if to change the 30 to 5 per yellow highlight

4.0e should be interesting if elementary stuff like this has not been eliminated.

Melissa Snyder

Crash has been reported, thanks.