Re: OPO question

From: Kasten10 <kasten10_at_aol.com>
Date: 1995/08/11
Message-ID: <40ft2k$nvc_at_newsbf02.news.aol.com>#1/1


In article <sista.47.000DE509_at_interaccess.com>, sista_at_interaccess.com (Kasu Sista) writes:

>>This in the TestCommand of one of my forms. gSecInterval is user-set as
 a
>>value of how often to update the form (the form in this case is same as
>>SQL*DBA's locks monitor). For some reason, I have to keep setting the
>>value of *something* to keep this sucker spinning (in this case I use
 the
>>hidden field of fldTemp). I'm sure that relate's to TestCommand primary
>>function is to see if a user has clicked on a menu or toolbar. I
 figured
>>this
>>would be similar to HyperCard's on Idle handler (I use to work on Mac's
>>for a living ;).
>
>This is correct. I am not sure why you have to set the temporary field
 value
>though? The test command is called everytime a menu item or tool bar is
>picked. But it is called to update the status bar a few times a second.
 So if
>
>you add a status bar to your form, I believe you do not need the
 temporary
>field update.
>
>Kasu Sista
>Co-Author, Oracle Power Objects Developer's Guide.
>Links Technology Corp.
>Chicago, IL

I'll buy that. I just knew that I did not have a status bar, and if I was NOT
moving the mouse or assigning values *somewhere* that routine was just plain not being called.

Chris Received on Fri Aug 11 1995 - 00:00:00 CEST

Original text of this message