On 18/09/2007, Tony Houghton <h@...> wrote:
> I think it would be a good idea to have Add Panel and Remove Panel
> somewhere in ROX's GUI. Where to put "Remove Panel" is quite obvious:-
> under "Panel Options..." in the panel-specific menu. "Add Panel" isn't
> so easy. "Add Panel" doesn't relate to the panel the menu is opened
> over, so it doesn't really make logical sense, and you wouldn't be able
> to add a panel if there were no panels to start with. I wondered about
> putting it under "Backdrop..." in the backdrop menu. Then you wouldn't
> be able to create a panel if ROX wasn't managing the backdrop, but is
> that a problem?
Well, I use ion3, so I don't have a backdrop ;-) But having 'Add
panel' on the pinboard menu does sound sensible.
("Enable pinboard" is in ROX-Filer's AppInfo.xml menu, but that's
pretty strange and I don't think many people found it there)
> I had a quick look at the code and I'm a bit puzzled by the SOAP "Panel"
> call. It's defined as taking parameters Side, Name in that order with
> Name being optional, but most of the calls to it have Name as the first
> argument and Side is usually NULL. Do they get sorted by name before
> being passed to the function?
Name matters but order doesn't IIRC.
The reason for the ordering is historical. Originally, everything was
indexed by side. e.g. you'd say:
$ rox --bottom=MyPanel
$ rox --bottom=MyOtherPanel
$ rox --bottom=
Now, each panel remembers which side it goes on and you just say:
$ rox --border=MyPanel
(note cunning reuse of -b to avoid breaking scripts ;-)
Except when removing things, where you still give the side (which is
also a bit odd).
Dr Thomas Leonard http://rox.sourceforge.net
GPG: 9242 9807 C985 3C07 44A6 8B9A AE07 8280 59A5 3CC1