{{tag>category:"OpenInsight 32-Bit" author:"Barry Stevens" author:"Mike Ruane" author:"Jim Peters"}}
[[https://www.revelation.com/the-works|Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community]]
==== EDIITABLE SELPOS (OpenInsight 32-Bit) ====
=== At 16 FEB 2006 12:54:19AM Barry Stevens wrote: ===
OI 7.2.1
I am sure I am doing the same code as in 4.3:
Editable with 4 cols required. On changed event for col 1 checking the value and if an error then set SELPOS to the PREVSELPOS value and set the cell to null.
The cell is being set to null but, I get an OI messgae re the 2nd cell is reqired and focus is in 2nd cell.
This doesnt happen in 4.3 but does in 7.2.1.
Not exactly the same code , but the same logic.
(I will do a an upgrade of the 4.3 system to 7.2.1 and test it.)
But, in the meantime:
Can anyone confirm this, or tell me how it SHOULD be done.
----
=== At 16 FEB 2006 03:43AM Barry Stevens wrote: ===
Oops 4.3=4.13
OK, appears the 4.13 system worked because I had IOOPTIONS set to allow tab out - was for another reason, so I fluked it.
Does anyone have a method they use, besides IOOPTIONS.
In the meantime I will experiment.
----
=== At 16 FEB 2006 04:29AM Barry Stevens wrote: ===
OK, I found - utility("FLUSH")- works, so far. Not sure if there are any gotchas yet
----
=== At 16 FEB 2006 09:44PM Barry Stevens wrote: ===
..or you can use STOP !!!
In the process of converting an Arev system (No Don , not that one). I recompiled it in OI , expecting to do the normal changes:
change the STOP
add else null to writes und unlocks.
Whoope, these syntaxes are now accepted.
----
=== At 17 FEB 2006 07:21AM Mike Ruane wrote: ===
Courtesy of your friendly neighborhood CTO enhancements. While reviewing the opcodes we need for some of CTO changes, it's amazing to me that some were taken out.
We continue to review them and plan to put some more in. Watch this space.
----
=== At 17 FEB 2006 12:13PM Jim Peters wrote: ===
Interesting!
So... what is the scope and effect of a STOP in an event script? Is it similar a return 0 in the currently executing script, or does it cancel anything else in the que too?
In other words, is this something we want to use on purpose sometimes?
When I first started working with OI I was pleasantly surprised with the understated backward compatibility with Arev code. Now it is even easier.
It looks like we all benefit from CTO, even if we don't have a bunch of green screen Pick type stuff to work over. Good job guys!
----
=== At 17 FEB 2006 05:05PM Barry Stevens wrote: ===
In commuter code the STOP kills all in event queue.
----
=== At 17 FEB 2006 06:21PM Barry Stevens wrote: ===
In regards to CTO.
Where is it in OI7.2.1
What systems\languages does it address.
[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=WORKS_READ&SUMMARY=1&KEY=07EB9B7AE7E13B67852571170020707C|View this thread on the Works forum...]]