On Fri, 2021-02-05 at 10:34 +0000, Joe Wilkinson wrote: > I have created the palette shown with 4 scheme scripts. > > It works fine but: > If I switch to another application, like this email, it remains on to > until I close it, when it takes me back to Denemo (and all I want it > to do is GO AWAY!) I think its normal that the various windows that a program remain open when you start using windows belonging to anther program, such as your email program. If you decide you want to close a Denemo window then you can do that, but at that point you are interacting with Denemo, you can hardly expect it to pass the focus back to some external program, unless you are shutting the main Denemo window which will terminate Denemo and after that it is up to Windows what to give the focus to. If you want the palette to go away, why wouldn't you iconize it? (My window manager provides a button for this in the decorations at the top, while your screenshot shows windows only providing an "x" button, but I gather you have an option to right click to get at the iconize option ... better still, though why not iconize the Denemo main window, which, at least with my window manager iconizes palettes as well).
> If I want to edit the scheme script it will accept taking the script > into the scheme window BUT the Scheme window won't stay open if the > Palette is not closed. I'm not at all sure I understand what you are saying, and I suspect this is because of a fundamental misunderstanding: the Scheme window has nothing to do with palettes or commands: it's just a text editor with the facility to execute any text it holds using a Scheme interpreter. Individual buttons in a palette have the option to replace the Scheme script that they contain with the contents of the Scheme window. And likewise individual menu items (if they are scripted ones) can replace their scripts with the contents of the Scheme window. But the Scheme window stores no knowledge of where the text it holds has come from or where it might go to (*) - it has no connection with any particular palette button or menu item. Having cleared that up (I hope!) I still have no idea what you were describing about the Scheme window not staying open - it stays open until you close it, independently of the status of any other windows. > So tweaking the script becomes time consuming > To reopen the palette (for example to Save Script which I assumed > meant save script back into button) requires 4 mouse clicks. Again, I'm unsure what you mean. If you want to edit the script of a palette button you would right click it and choose "Get Script into Scheme Window" you would edit it in the Scheme window then you would right click the palette button and choose "Save Script from Scheme Window" It would be nice if the Scheme window knew where the text had come from and you could just tell the Scheme window to save, and nicer still if you could somehow tell it to save to an arbitrary menu item or palette button via some means of navigating through the command/palette space ... > I can't allocate a key sequence to open MyPalette - right click > causes it to open. There is a command to do that: d-ShowPalettes (**) (d-ShowPalettes "MyPalette") So you can make a command with that as the script and give it a keyboard shortcut. Then you can show your palette at a keypress. > And I can't dock it either. All I get from a right click in the top > bar is: To Dock a palette right click on any palette item, choose the Edit Palette sub-menu and then Dock. The right click on the top bar only gives you options Windows knows how to do... > > Is this behaviour normal? It is cumbersome. Yes, it's not how you would design it from scratch :( Richard (*) Hmm, I see this is not entirely true, the File menu of the Scheme window does have a Save option, which means if it remembers the Scheme was loaded from a file on disk, it can save back to that file. But it does *not* mean that it can "save" to anything other than a file on disk. It is individual buttons that can "capture" the Scheme window contents for their own purposes that effectively do that. (**) I'm not sure why it isn't named d-ShowPalette without the "s" ...
