Troubleshooting

Known problems

  • 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.

  • Newer versions of libxml2 do not seem to validate against the DTD properly (ie, invalid elements are allowed). Future versions of eboxy will do the validation internally.

  • The script parser produces somewhat unhelpful error messages.

  • eboxy does not use the attribute defaults defined in the DTD - these are hardcoded into the application.

  • There have been some reports of flickering when using eboxy with framebuffer output. This is due to drawing issues with SDL_gui, and will be fixed when eboxy changes over to a different GUI library.

  • 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.

  • eboxy does not purge its image/font cache while running unless exechide is called. This could be an issue if you are designing an image browsing screen and load lots of images.

  • The autoconf/automake build setup for eboxy is slightly broken, in that make dist doesn't really work properly and the --enable-debug option to configure doesn't work either. To build with debugging symbols, just run the following:

    	CXXFLAGS=-ggdb ./configure
    	

    (yes, that's all on one line). Then run the normal make and make install.