Re: [StrongED] ToggleBD 1.03 available

[Tony Moore <old_coaster@xxxxxxxxxxx>]

On 19 Mar 2013, Fred Graute <fjgraute@xxxxxxxxx> wrote:
> In message <4ab0d32e53.old_coaster@old_coaster.yahoo.co.uk>
>           Tony Moore <old_coaster@xxxxxxxxxxx> wrote:

[snip StrongHelp]

> > Toggle options Screen edge is greyed out but, in fact, the option is
> > active on all four screen edges.
>
> Ah yes, there is placeholder code that reacts to the EdgeNotification
> message that is in the ROL branch but not in the ROOL branch. I still
> need to make a decision on this; use the message or do edge detection
> in ToggleBD itself.

Meanwhile, is it possible to unset the option? At the bottom of the
screen, it conflicts with raising the iconbar (if covered), and,
generally, causes inadvertent backdrop toggling.

[snip]

> > Here, ToggleBD continues to work, with the reservations mentioned in
> > my earlier posts, ie for RO4.39 and 6.20 both 'Raise...' and
> > 'Lower...' cause the backdrop to be toggled front/back. However, for
> > RO5.19, only 'Lower...' toggles the backdrop. 'Raise...' brings the
> > backdrop to the front but further keypresses. or icon clicks, don't
> > send it back.
>
> I still don't understand why that is, here using 5.19 it works fine
> both on the Iyonix and RPCEmu.

I wonder if anyone else sees the problem?

> > I'm afraid that 'bear of little brain', here, is still trying to
> > understand the difference between 'Raise...' and 'Lower...' which,
> > when using  RO4.39 or 6.20, seem to produce identical results:
>
> Open a window when the backdrop is raised then you'll see the
> difference when you keypress/icon click again.

Let toggle1 = 'first pair of keypresses/icon click' and
    toggle2 = 'second pair of keypresses/icon click', etc

If Behaviour is set to 'Raise...'

   If the backdrop is initially at the back, toggle1/toggle2 causes the
   backdrop to be raised/lowered, as expected.

   If a window is opened, over a raised backdrop, toggle2 _raises_ the
   backdrop, having lost track of the toggle sequence, in which the next
   operation is 'lower'. Toggle3 is needed to lower the backdrop.

If Behaviour is set to 'Lower...'

   If the backdrop is initially at the back, toggle1/toggle2 causes the
   backdrop to be raised/lowered, but this result is unexpected, since
   initially the backdrop is at the back, so toggle1 should be ignored.

   If a window is opened, over a raised backdrop, toggle2 causes the
   backdrop to be lowered, as expected.

For me, ToggleBD needs only to bring the backdrop to the front, on
toggle1, and send the backdrop to the back, on toggle2. At present this
is best served if Behaviour is set to 'Lower...'.

Maybe I've misunderstood something ...

Tony




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