Next
Previous
Contents
- eboxy cannot tell what resolution fullscreen should use, so if you want
anything other than 640x480 (the default) you will need to specify it with
the --width (or -x) and --height (or -y) options. With --fullscreen (or -f)
specified, eboxy will attempt to change to the specified screen resolution
if it isn't already active.
- If you are using eboxy full-screen with LIRC, there is a problem that
you may need to work around. With certain window managers, or no window manager
at all, focus may not be correctly passed to other applications when you use any
of the exec* script commands, and so LIRC commands won't be ignored while the
external program is running, which could be bad if you use some of the same
remote buttons in external applications as you do in eboxy. So far the only
workaround for this is to use a window manager that transfers the focus properly -
twm does not work, fvwm2 and KDE's kwm are known to work. If you use fvwm2, you
will need to use a configuration similar to the following (in
~/.fvwm2rc
):
Style * NoTitle, BorderWidth 0, HandleWidth 0, ClickToFocus
ClickToFocus
is the most important setting - the others just reduce
the interruption a second or two after eboxy regains focus, as it becomes
full-screen again (unfortunately the transition is still visible, however).
- If you overlap two button images, you won't see PNG transparency working
the way you might expect. Images are transparent onto the background only.
It's generally best to avoid overlapping widgets at the moment.
- The script parser produces somewhat unhelpful error messages.
- The mouse cursor may interfere with your GUI whether you're using it or
not. If the GUI starts with the cursor over the top of a button then that
button will be selected first. If you don't like this (you probably won't
if you're not using the mouse) then specify the --hidecursor (or -h)
command line option, which both hides the mouse cursor and moves it to the
top left hand corner of the graphics area before bringing up the GUI.
- eboxy does not use the attribute defaults defined in the DTD - these are
hardcoded into the application instead. This may be a good thing (because
skins are more likely to be interpreted the same across different systems).
- If you modify an image file that eboxy is using while it is running, eboxy
will not reload that image even if you reassign the image property of the
widget that is displaying it - images are cached, as are fonts. The only time
the cache is reloaded is if you use the "exechide" command.
However, if you wish to reload an image being displayed in a picture widget,
you only need to call its reloadimage() method in a script and the image will
be reloaded from disk.
- When eboxy hides its GUI (ie, when exechide is used in a script) it in fact
unloads everything from memory, deinitialises the graphics library and then waits
while the program runs. When the program finishes, eboxy loads itself back up.
You will always get back to the correct page, but the "state" will be lost. I
hope to correct this in the future if I can figure out a better way of doing
the hiding.
- It may just be my keyboard, but the printscreen key doesn't produce the
expected result with eboxy (more precisely, with SDL).
Read the file TODO
to get some idea of the general direction I'd like
to take eboxy in the future.
eboxy was written by
Paul Eggleton.
I welcome any comments, questions, suggestions, or patches that people might
have.
You can download updated versions of eboxy by visiting the eboxy
homepage.
There is also a SourceForge
project
for eboxy, where you can post bugs, suggestions, patches and discuss eboxy.
The latest in-development version of eboxy is also available from CVS at SourceForge.
Next
Previous
Contents