Edittable Oddness (OpenInsight Specific)
At 03 MAR 1998 03:39:43PM Don Bakke wrote:
I've just noticed a behavour with edittables that, quite frankly, I'm surprised has never come up before.
If I begin entering data into a cell, do not hit or click anywhere else in the edittable, but simply click on a different control on the form, the edittable never validates, output converts, or stores this data in any property (ARRAY, LIST, DEFPROP, INVALUE, etc.) of the edittable. Even if I save the record and bring it back the data is gone. So, for all intent and purposes, entries into an edittable cell aren't tracked until the key is pressed or the cell position changes.
Why doesn't LOSTFOCUS force correct behavour? (BTW, the LOSTFOCUS event does get fired.)
Using OI 3.5, but have tested with OI 3.3 as well.
Thanks,
dbakke@srpcs.com
At 03 MAR 1998 04:55PM Cameron Revelation wrote:
Don,
It sounds like the SYSPROG*LOSTFOCUS..OIWIN* event is not getting executed. Could you post a dump of the LOSTFOCUS chain from System Monitor? Check if you have code on the LOSTFOCUS event … if so, don't return 0.
Cameron Purdy
info@revelation.com
At 04 MAR 1998 09:18AM Aaron Kaplan wrote:
Funny enough, I rely on this feature working, but I have a POSCHANGED event on there as well. Perhaps this is altering my results.
apk@sprezzatura.com
At 04 MAR 1998 10:04AM Don Bakke wrote:
Hi Cameron,
It sounds like the SYSPROG*LOSTFOCUS..OIWIN* event is not getting executed. Could you post a dump of the LOSTFOCUS chain from System Monitor? Check if you have code on the LOSTFOCUS event … if so, don't return 0.
More info:
This only seems to happen in Win95. I have a dual-boot machine and everything works as normal, or as expected, in Windows 3.1.
The only time I had code in the LOSTFOCUS event was after I noticed this problem so I added code to check the properties of the edittable. I have since removed this event and confirmed this removal using the entity delete menu function as well.
Finally, I've also noticed a slightly different look for my edittables as well. This caused me to remember that the latest Protoview Datatable also looks and behaves the same way so I'm suspecting that a different version of DATATBL.DLL is getting called. In fact, I just now did a search and in the C:\WINDOWS\SYSTEM directory there is a copy of the newer DATATBL.DLL so I will remove it and reboot to see if this goes away. Since I've also just installed some new software I suspect this got entered in the above directory and is therefore causing me problems. I will get back with my results.
In the meantime, here is a portion of my LOSTFOCUS chain dump:
RUN_EVENT calling:SYSPROG*LOSTFOCUS..OIWIN* ... Looking for:SRP*..OIWIN* ... Looking for:SYSPROG*..OIWIN* ... RUN_EVENT calling:SYSPROG*..OIWIN* ... Looking for:SRP*LOSTFOCUS.EDITTABLE* ... Looking for:SYSPROG*LOSTFOCUS.EDITTABLE* ... Looking for:SRP*LOSTFOCUS* ... Looking for:SYSPROG*LOSTFOCUS* ... RUN_EVENT calling:SYSPROG*CLICK..OIWIN* ...dbakke@srpcs.com
At 04 MAR 1998 11:25AM Don Bakke wrote:
In fact, I just now did a search and in the C:\WINDOWS\SYSTEM directory there is a copy of the newer DATATBL.DLL so I will remove it and reboot to see if this goes away.
Yep, that was the problem. Now I hope the software that installed this will be able to run!
dbakke@srpcs.com