Re: [StrongED] Re: StrongEd v4.70a11 and Throwback

[Fred Graute <fjgraute@xxxxxxxxx>]

In message <5618a4cabflist01@xxxxxxxxxxxxxxxx>
          Martin <list01@xxxxxxxxxxxxxxxx> wrote:

> In article <434a8e1856.fjgraute@xxxxxxxxx>,
>    Fred Graute <fjgraute@xxxxxxxxx> wrote:
>
> > What happens if you start 4.70a11, load a BASIC file and then click on
> > the 'List functions and procedures' icon [1] on the toolbar?
> A LoF opens, and lines are highlit when the mouse is over them.
> Clicks open the program at that line.

Can you confirm that the LoF doesn't have focus in this case, ie cursor
up/down do not move the highlight?

If that's the case then my working hypothesis (see below) would be wrong
and we have an even stranger problem.

> > In this case the LoF doesn't get input focus so it may not work now.
>
> Not sure what you mean by that.

When a LoF is created via the keyboard (F2 or cs-F) then it will be
given the input focus so that the user can stay with the keyboard. When
a Lof is opened using the mouse (eg via a toolbar icon) then it won't be
given focus.

My working hypothesis for now is that somehow StrongED isn't seeing the
pointer entering event and because of this it doesn't set up a mouseline
(the menuline controlled by the mouse). When there is no mouseline the
pointer leaving event isn't unmasked and no highlight is shown, this
matches your description.

Clicks in the window also use the mouseline data to go to the target
line. When that data isn't set, clicks will usually fail (except when
the data present happens to be valid).

When the window has focus, a focusline is set up (menuline controlled by
keyboard). If the mouse is over the window too, only the focusline will
be shown but it can be controlled by both keyboard and mouse. So in that
case it doesn't matter if the pointer entering event is missed.

> > Another thing to try is to generate some throwback. Then open a StrongED
> > view and press cs-F8 to give the throwback window focus. Does that make
> > it work?
>
> Yes!!!
>
> While the Throwback window has Input Focus, the mouse moves the selected
> line up/down, and Enter shows that line in the program but closes the
> Throwback window.

Okay, that exactly what should happen.

> Clicks on the lines *sometimes* displays that line in the program (not
> worked out when it does or not). I will try to clarify this.

That's a bit surprising. I would have expected that to work too, need to
check the code to see what it's actually doing.

> > 4.69f9 only has one menuline (the highlight that follows the mouse
> > and/or cursor up/down). 4.70a11 has two, one for the mouse and another
> > for the keyboard). When a window has both input focus and pointer over
> > it then only one menuline is shown but it can be controlled by both.
>
> I think I see what you mean. When the mouse moves the black line the
> original one is left with white background.

No, the white line indicates the last line that was activated using the
mouse or keyboard. 4.69 does not mark the last line activated.

In 4.70a11, if you have a throwback window then moving the mouse over it
shows the black highlight. If you then open a LoF using the keyboard it
too will have a black highlight but controlled via the keyboard.

4.69 makes a bit of hash of that last scenario. If the pointer is over
the throwback window, the cursor keys will move the highlight in that
window even though it is the LoF that has focus.

> Not sure what use the mouse has (yet) because if Enter pressed that line
> is displayed in the program, but the Throwback is closed. Might be useful
> on occasion.

The keyboard actions for LoF & throwback are defined in the BaseMode
ModeFile and can thus be changed to suit one's needs. The current
definitions are:

  Up         Move to previous line
  Down       Move to next line
  Left       Lose focus
  Esc        Close window
  Delete     Delete highlighted line

  Tab        Move to target line, keep window open, keep focus
  Right      Move to target line, keep window open, lose focus
  Return     Go to target line, close window

  c-Return   Go to target line but in a new view, close window

See manual -> Reference -> Functions -> ThrowbackAction for details.

> > For some reason 4.70a11 is not detecting if the mouse is over LoW or
> > throwback so no menuline is ever activated and StrongED doesn't know
> > what the active line is. LoF works because it's given the input focus
> > and so there is a menuline. The problem is finding out why this happens.
>
> I have now also tried a new SE install on a Pi - which works.
> The same install (using ShareFS) did not work on my Iyonix.

Does the SE on the RPi continue to work even after prolonged use?

> [Note that with no extra modes installed, a TaskWindow request fails with
> Abort on instruction fetch at &4 (this is on a high vectors build)]

Someone has already reported this and it shows that the TaskWindow mode
must always be part of any StrongED release.

Cheers,
Fred.

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

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