OpenEuphoria

RE: Eu Editors

• Posted by Judith <camping at txcyber.com> Aug 07, 2002
• 467 views

The new properties catches invalid data as you move from cell to cell in 
Properties. If you were to enter invalid data in a cell and then, for 
example, click in Design or open another window in IDE, properties would 
not validate. I will see what happens if I check w32HLostFocus on the 
Property Window with some kind of overall validation.

Thanks for your comments,

Judith


mistertrik at hotmail.com wrote:
> Cool cool... (more below)
> 
> 
> > > *Make the namespace a little more tolerant of typing. IE atm it doesnt
> > > like
> > > you deleting all the characters in the name attribute before typing in a
> > > new
> > > one. If it could hold off until it loses focus, then perhaps that would
> > > be
> > > better.
> >
> >Martin Stachon has rewritten Properties for the next release and it does
> >allow waiting until user moves to another property before issuing an
> >error message. However, I found it safer to issue the message when the
> >error happens. There is a way around the problem and it is to use 'Wait
> >for Enter Key' under the Configuration Menu. What this allows is for you
> >to set which properties will not issue error messages or take action
> >such as redrawing or changing text until you press Enter key. Not all
> >properties can use Wait For Enter Key, just the ones I felt caused
> >problems like you describe. Your selection in Wait For Enter Key is
> >retained for the next time you use IDE.
> >
> >After making a change to 'Wait For Enter Key', it will take action on
> >the *next* control you click, since it activates when new information is
> >loaded into Properties. I probably should change this to take action
> >right away, hum....
> 
> 
> I'm not sure I understand...
> I had a similar problem where the content of a field had to be correct, 
> otherwise the program would do something silly. So, I had code like 
> this:
> ###(not necessarily real code)
> procedure onLostFocus_MyCtrl()
>     sequence t
> 
>     t = getText(MyCtrl)
> 
>     if not valid(t) then
>          setFocus(MyCtrl)
>          highlight(MyCtrl)
>          popupHint("Invalid Value") *OR* setStatusBar("Invalid Value")
>     end if
> end procedure
> onLostFocus[MyCtrl] = routine_id("onLostFocus_MyCtrl")
> ###
> 
> That sort of thing is ok, isn't it? That way, you ensure the validity of 
> the 
> data, but the person isn't bothered until they've finished with the 
> control.
> =====================================================
> .______<-------------------\__
> / _____<--------------------__|===
> ||_    <-------------------/
> \__| Mr Trick
> 
>