Automatically moving pinboard to front.

if you’re looking for a more logical fit a Window is an aspect of a Task and Switcher is referred to as Task Switcher

Ah, but windows display stuff. It’s their raison d’être.

Ah, but windows display stuff. It’s their raison d’être.

Windows (solid flat things) let you see through them.
Displays present a view.

In there you can specify a hotkey combination too, but not Logo-D (yet?).

Have you tested? :)

Not sure I understand the question. Have I tested what?

So far no changes have been made to ToggleBD’s hotkey handling. Adding Logo-D complicates things a bit as you’d want to allow ‘D’ as the second hotkey only when the first hotkey is Logo. This to avoid acting on Alt-D or Ctrl-D or Shift-D.

In addition you’d need to intercept the D keypress to prevent it from being inserted at the caret. So I’m not sure Logo-D is a good choice. On Linux/Windows, I assume, Logo-D is a special keypress similar to Ctrl-D. On RISC OS however it’s just Logo keypress followed by D keypress.

I did do some experimenting with a notification window on how to get one’s windows back after (accidentally) fronting the backdrop. Works but haven’t made a decision on this yet.

Would the application !Madness help here? It finds each active window and moves it a bit so could equally include a bring to top command as well, which could examine the window stack position and when it had cycled right through, bring them to the top in the right order.

Would the application !Madness help here? It finds each active window and moves it a bit so could equally include a bring to top command as well, which could examine the window stack position and when it had cycled right through, bring them to the top in the right order.

That was my inspiration for my holiday coding project – I’ll see if I can implement Logo-D behaviour during the weekend, might be fun. If I learn anything, I’ll share it here.

Would the application !Madness help here? It finds each active window and moves it a bit so could equally include a bring to top command as well, which could examine the window stack position and when it had cycled right through, bring them to the top in the right order.

For applying or reversing Logo-D¹, it’s not necessary: all that you need to do is to call Message_ToggleBackdrop and whichever “pinboard” application the user has chosen² to use will bring itself to the front or return itself to the back — leaving all of the other windows in the correct stack order. The same code will work on Select/Adjust, too.

So what we need is a “Logo-D calls Message_ToggleBackdrop”, “Click on whichever icon we decide on calls Message_ToggleBackdrop” or “Moving the mouse to a special place calls Message_ToggleBackdrop” utility, which will then work with the current Pinboard, Pinboard2, and others. ToggleBD already fits into this category, even if it doesn’t quite use any of the discussed triggers.

Perhaps all of these should be in Pinboard 2?

Again, we’re back to the point that if you modularise this and use the existing API, then users can mix and match their preferred approach if they don’t like the ones that are shipped as standard with the OS.

¹ “Logo” isn’t a modifier key under RISC OS, though: it’s a “real” key which returns a “real” keycode. You can assign an action to it through Configure on RO4/5/Six. So Logo-D would return two distinct keypresses into the buffer: “Logo” and “D”.

² Assuming it supports the message; the OS ones do, at least, and so should Pinboard 2.

Adding Logo-D complicates things a bit as you’d want to allow ‘D’ as the second hotkey only when the first hotkey is Logo.

Moreover, wouldn’t it interfere with !HID, which does exactly that? I’ve assigned Logo-D since years to firing up my database application.

Perhaps all of these should be in Pinboard 2?

Again, we’re back to the point that if you modularise this and use the existing API, then users can mix and match their preferred approach if they don’t like the ones that are shipped as standard with the OS.

You’re right because I’m making the possibly foolish assumption that the functionality of Pinboard2 is delivered as a modular set rather than a monolith. We can of course rely on the developers to be sensible and make it modular – can’t we?