{{tag>category:"OpenInsight 32-bit" author:"Jim Vaughan" author:"Carl Pates" author:"Matthew Crozier"}}

[[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]]


==== Get_Property (OpenInsight 32-bit) ====
=== At 04 MAR 2021 05:13:37PM Jim Vaughan wrote: ===
 
 
<QUOTE>
I use Get_Property ARRAY property to get a data from an Edit Table. It's a large Edit Table and returning the data takes some time. 



I then a few lines of code later call Get_Property again to get the VALUE of a radio button on a different window. The data returned is the same as the first call, a large string of @FM, @VM delimited date. If I call the Get_Property again with the exact same parameters I get a return value of 1, which is correct. 



Anyone ever seen anything like this?



Jim R Vaughan

www.waterloo-software.com
</QUOTE>
----

=== At 04 MAR 2021 07:24PM Jim Vaughan wrote:  ===

<QUOTE>Some more information 



Data has a LEN of 1,909,206 and the Set_Property ARRAY is very quick the Get_Property ARRAY is very slow.



Jim R Vaughan

www.waterloo-software.com

</QUOTE>

----

=== At 05 MAR 2021 08:12AM Carl Pates wrote:  ===

<QUOTE>Hi Jim,



Can't say I've seen the problem with the wrong return value before - no idea off the top of my head why it would do that, and then return the correct value on the next access.



I would expect the Get to be slower - I rewrote the Set several years ago to make it faster, so that's the difference there.



[email=cpates@revsoft.co.uk]Carl Pates[/email]

</QUOTE>

----

=== At 05 MAR 2021 01:19PM Jim Vaughan wrote:  ===

<QUOTE>Yes, very strange.



I fixed it by storing the data elsewhere, removing need for a Get_Property. 



Jim R Vaughan

www.waterloo-software.com

</QUOTE>

----

=== At 07 MAR 2021 04:14PM Matthew Crozier wrote:  ===

<QUOTE>Yes, I've seen that behaviour where get_property() could return the result of the [i]previous[/i] get_property() call rather than the property it is being asked for.  In our case it wasn't related to the amount of data through. It seemed to occur when the SIZE event gets calls repeatedly through vigorous  resizing AND there is a background process going on, monitored with a TIMER event.  This is going back to OI v9.2.1



We never got to the bottom of it, but applied a work-around by inserted this line in any code sensitive to this


<code>
Loop while get_property( MDIframe, 'DEFPROP' ) == 'WINDOW' Repeat
</code>


This won't continue through the code until get_property() comes back with the known correct answer.



My notes on this refer back to Rev Bug Tracker #252:


<QUOTE>There is a behavioral difference with the SIZE event when the window is called with Start_Window versus Dialog_Box. Start_Window allows the SIZE event to trigger as the window is being resized. Dialog_Box only allows the SIZE event to trigger after the window has been resized. [b]My assumption is that the way OpenInsight handles modal processing is suppressing the synchronous execution of events.[/b]

</QUOTE>



HTH, M@

[url=http://www.vernonsystems.com]Vernon Systems[/url]

</QUOTE>


[[https://www.revelation.com/revweb/oecgi4p.php/O4W_HANDOFF?DESTN=O4W_RUN_FORM&INQID=WORKS_READ&SUMMARY=1&KEY=D55E2C6E6643D64CA6A099933FA5D268|View this thread on the Works forum...]]