Ian Bartholomew wrote:
> A bit of debugging shows that in InputState>>aboutToIdle the initial
> call to uiIdle answers 1, rather than a Boolean. However, looking at
> the code for uiIdle I can't see how it can possibly answer 1 - so I'm
> going to bed!.
I have a vague recollection of running into this once a few months back
in D5. I looked at the code for a bit and remember thinking "this is
impossible". As I didn't have any way to repeat what had happened, I
just let it go. Glad to hear you found something that can reproduce what
appears to be the same problem!
--
Bill Dargel
[hidden email]
Shoshana Technologies
100 West Joy Road, Ann Arbor, MI 48105 USA