Re: [StrongED] TaskWindow in StrongEd 4.70a6

[Fred Graute <fjgraute@xxxxxxxxx>]

In message <45784a6054.pittdj+@xxxxxxxxxxx>
          David Pitt <pittdj@xxxxxxxxxxxx> wrote:

> In message <c8b2446054.fjgraute@xxxxxxxxx>
>   Fred Graute <fjgraute@xxxxxxxxx> wrote:
>
> > In message <545f6c5082cvjazz@xxxxxxxxxxxx>
> >           Chris Newman <cvjazz@xxxxxxxxxxxx> wrote:
>
> >> In article <359df05e54.fjgraute@xxxxxxxxx>,
> >>    Fred Graute <fjgraute@xxxxxxxxx> wrote:
> >>> In message <545eeab1a3cvjazz@xxxxxxxxxxxx>
> >>>           Chris Newman <cvjazz@xxxxxxxxxxxx> wrote:
>
> [snip]
>
> >>>>  : Unknown task
> >>>>  : Internal error: abort on data transfer at &03FFFFFC
> >>
> >>> This cannot be caused by the taskWindow problem, it must be a different
> >>> bug. More details such as machine, OS version, etc would be appreciated.
> >>
> >> RiscPC Strong ARMv4 Adjust 4.39 with Unipod
>
> > Thanks. I'll have a try on the RiscPC to see if it fails but I don't
> > have 4.39 (only an older version of Select) so may not be able to
> > reproduce this.
>
> > Has anyone else tried 4.70a6 on a RiscPC with RISC OS Adjust 4.39?
>
> I had used SE4.70a6 on OS4.39 VRPC with only the TaskWindow bug. Until
> this email turned up and would you believe it I got this immediately
> on starting StrongED.

[snip]

> Anyway it would seem to be the OS4.39 DA thing again, I had thought
> that had gone away.

As had I but alas it was still calling OS_HeapSort on 26-bit instead of
OS_HeapSort32, even though StrongED now RMEnsures CallASWI 0.03 to make
sure that it can call OS_HeapSort32 safely. :-(

Anyway, I've uploaded a new RunImage for 4.70a6 that should fix this
issue. Please give it a try and let me know if it's really fixed.
http://www.stronged.iconbar.com/archives/misc/ri470a6.zip

The following issues have also been fixed:

 - TaskWindow would abort when opened for the first time.

 - Saving BASIC files where the line numbers weren't stripped could lead
   to spurious data at the end of the file.

 - If a mode had syntax colouring turned off then turning it on would
   cause an abort.

 - Fix problem where lines didn't indent properly after adding a new
   line and then moving cursor left so it aligned with the line above.
   When the first character was typed the indent could be too small or
   too big if the font used had a width <> 8.

 - The same fix as above has been applied to the Unwrap function so that
   the character width doesn't affect at what point a line is wrapped.
   Needs more work especially with proportional outline fonts.

Cheers,
Fred.

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

--
To unsubscribe send a mail to StrongED+unsubscribe@xxxxxxxxxxxxxx
List archives at http://www.Torrens.org.uk/RO/StrongED/index.html