Bill,
I was about to ask you what to do in a timer verb when the count or
time hit a threshold. That is what would I clear or restart? (and that
may eventually be a question I would like an answer for.)
But then I elected to reread this earlier message in which you said
that the 'pactive' part of the wd command may not affect the 'graphic
handle', so I tried omitting 'pactive' (which I had tried earlier, but
something else may have been different).
Anyhow, the result of removing 'pactive' is that I have even
accomplished a `try 500` without any problems with the keystrokes in
the graphics window while retaining the ability to run selections from
either the ijs or ijx window. The one thing that I lose by omitting
'pactive' is that the graphics window is not automatically selected
after the simulation ('try', in this case) finishes. Is there
something I could add to the 'paint' to retain this finishing result
without requiring a timer?
Thanks, very much,
On Wed, Sep 16, 2009 at 12:33 PM, bill lam <[email protected]> wrote:
> On Wed, 16 Sep 2009, Brian Schott wrote:
>> One other change I made was to add the following line to the beginning
>> of the paint verb because I was trying to achieve the finding of the
>> graphics handle when jumping between windows.
>>
>> wd'psel opengl;pactive'
>
> I cannot run that opengl stuff because I use linux64. However I
> suspect that you need a timer to schedule the steps rather than
> blindly loop 100 times.
>
> BTW I guess that you might need
> wd'psel opengl'
>
> but the 'pactive' part will not affect 'graphic handle'. If you have
> more than one isigraph in the same window form, then you need an the
> 'glsel'. Moreover if you use 'glsel' then wd'psel ...' is not needed
> for the purpose opengl drawing. sound confusing ;-)
>
> --
> regards,
>
--
(B=)
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
