Re: [rox-users] Pinboard puzzles

[Jim L. <jc...@au...>]

On 13 Oct, jc...@au... wrote:


> I'd written a simple demo app that I've called 'XTermPlus'. A left click
> on the icon opens a terminal window. A right click give a menu to which
> I added a few simple examples. I'd found that using menu items for 'rox
> -p=MyPinboard' and 'rox -p=' seemed to be working consistently. I could
> therefore boot up into Xubuntu, then press F12 to issue 'rox -S' and
> start the rox session. Then select the 'pinboard on' item from the
> XTermPlus menu and see the backdrop and pinboard appear.

I can now add a curious, but perhaps significantly systematic, extra to the
above...

I have changed pinboard name to 'Default' in case that made any difference.
(It didn't). I also experimented with trying to get my XTermPlus app to use
"xterm -e `rox -p=Default`" to see if that worked. i.e. seeing if that
would do the same as opening a terminal and typing in the command/

That didn't make any difference, but experimenting with that I left open a
rox filer window and mousepad displaying the AppInfo.xml contents I was
editing.

The discoveries were

1) If there are no rox filer windows or any other app windows visible. The
the 'pinboard off' menu item that issues "rox -p=" always removes the
pinboard. But the 'pinboard on' that issues "rox -p=Default" never produces
or restores it.

2) However if I have any rox filer or app windows visible, *both* the menu
commands work - every time so far! So if I have a mouspad or FireFox window
visible (called by an app that issues a command like "exec firefox", or if
I have a rox filer window. Then the 'pinboard on' always works.

Thus the inconsistency I have experienced may be because I hadn't noticed
that behaviour depended on having at least one other window visible
onscreen. Simply having the rox panel visible and being able to use it does
not mean that "rox -p=Default" will produce a visible pinboard and
backdrop. But opening an app or filer or terminal window allows the command
to produce a pinboard OK.

Does that give anyone a clue to what on Earth is going wrong here?

This presumably means that my proceedure of opening a terminal to type in
the command always works because at that point I have a window on screen!
Not because the terminal process itself is handling the command differently
as I had been thinking was happening!

Slainte,

Jim

-- 
Electronics  http://www.st-and.ac.uk/~www_pa/Scots_Guide/intro/electron.htm
Armstrong Audio  http://www.audiomisc.co.uk/Armstrong/armstrong.html
Audio Misc  http://www.audiomisc.co.uk/index.html