![]() | Known Bugs
![]() |
For a more up-to-date list see http://theoval.cmp.uea.ac.uk/jpgfdraw/faq/
The response time has improved with version 0.5b, however the following things can still slow Jpgfdraw's reaction time: setting the anti-aliasing on; setting the rendering to quality instead of speed; using a dash pattern with a zero length gap (use a solid line instead).
In addition, if you don't have much memory available, high magnifications, displaying the grid and having a high number of subdivisions on the grid may also slow response time.
If you have a thin line and the magnification is small or you have low resolution, the line may be too thin to show up on your display. Try either using a thicker line style or increasing the magnification.
Make sure that you are actually clicking and not dragging. (Some touch sensitive mouse pads can mistake a click for a move or drag.) Make sure that you have selected the correct tool.
Remember to use the Edit->Path and Edit->Text submenus to change the styles for existing objects, and use Settings->Styles... for all subsequent new objects.
Remember to identify each as a flow frame, a dynamic frame or a static frame. Any that hasn't been thus identified will not be written to the sty file.
Remember to include the pgf package. Jpgfdraw was tested using version 1.01 of the pgf package. It may not work with earlier versions.
The mapping between and screen pixels is computed on startup to improve Jpgfdraw's reaction time, so it doesn't register the change in screen mode. The Bitmap->Refresh menu item will update the scaling factor.
![]() | Known Bugs
![]() |