Re: [StrongED] Re: Illegal window handle in Taskwindow

[Fred Graute <fjgraute@xxxxxxxxx>]

In message <53551fbb06stronged-sub@xxxxxxxxx>
          Frank de Bruijn <stronged-sub@xxxxxxxxx> wrote:

> In article <58171c5553.fjgraute@xxxxxxxxx>,
>    Fred Graute <fjgraute@xxxxxxxxx> wrote:
> > It's working fine here on an Iyonix. Are you using an RPi, or one of
> > the other new systems?
>
> Nope. Iyonix with RISC OS 5.18.

Hmm, that surprising. It's Iyonix with 5.19 (06-May-2013) here but there
is no problem when selecting text in TaskWindow mode.

> Just switched on the StrongDump option and caused another abort. Zipped
> dump: http://aconet.nl/tmp/strongdump.zip

Thanks, but as I suspected there's not much useful data in there. The
reason is that 'Illegal window handle' is an error from the WIMP. When
the aborts occurs the CPU is executing a WIMP SWI, so it's outside of
the StrongED context. As a result most of the data in the StrongDump is
a bunch of nulls.

Unless I can reproduce it here it's going to be difficult to fix this.
A couple of questions to try to narrow it down:

 - Does the abort also occur if you double/triple click to select a word
   or line?

 - Did the window have input focus before starting to select text?

 - Was the TaskWindow still active? (When it's been killed to text will
   have been switched back to BaseMode.)

 - Does selecting text in any other mode produce an abort?

Cheers,
Fred.

-- 
StrongED Developer
http://www.stronged.iconbar.com/

-- 
To unsubscribe send a mail to StrongED+unsubscribe@xxxxxxxxxxxxxx