JaxoDraw uses the issue tracking system of SourceForge to manage its issues.
There you can browse existing issues (bug reports and feature requests) and also submit new ones. You will have to register an account on SourceForge, if you don't want to do that, you should submit your bug reports via the JaxoDraw mailing list.
The table below gives a list of bugs and limitations of JaxoDraw that are currently known (last update: 20.6.2005). Each bug has four entries:
Note that not all points are necessarily real bugs, we regard this just as a collection of features that do not work exactly the way we would like to.
| Number | Synopsis | Classification | Status |
|---|---|---|---|
| #1 | If a LaTeX text file is previewed with the Java internal previewer (i.e., without having set a custom previewer in the preferences), the page displays but cannot be scrolled. | JaxoDraw bug (all) | Closed (v.1.1-0) |
| #2 | Choosing a different Look and Feel in the Preferences dialog of the Options menu item and pressing the OK button, does not update the Look and Feel of the current session. | JaxoDraw bug (all) | Closed (v.1.0-1) |
| #3 | When using IBM's Runtime Environment, the program may be executed and works fine for most parts but presents some peculiarities: the layout of pop up windows is not always the same and XML output serializes the bounding boxes of objects that are explicitly marked as transient in the source code. This has been reported to us for version number 1.4.1 of IBM's SDK. | Java bug (all) | Open |
| #4 | If your LaTeX compilations give errors complaining about unknown commands like \SetColor{}, or the postscript viewer goes boink complaining about unrecoverable errors when reading your ps files generated with JaxoDraw you have to update your axodraw.sty file to the one included in our distribution. | Axodraw bug (all) | Closed |
| #5 | The wiggles of a gluon loop do not close correctly when watching the ps file generated through a LaTeX compilation. | Axodraw bug (all) | Open |
| #6 | Runnig an internal LaTeX compilation without axodraw installed, will hang the program. Workaround: Run JaxoDraw from a directory where there is the style file of axodraw (such as the distribution home directory). Solution: Install axodraw on your system (which is very easy, as explained in Appendix A of the JaxoDraw user guide). | JaxoDraw bug (all) | Open |
| #7 | The LaTeX-EPS export command save the file only in the directory JaxoDraw was started in and NOT in the directory chosen in the dialog. | JaxoDraw bug (all) | Closed (v.1.0-1) |
| #8 | If your locale settings are different from the english ones, you may get errors in your LaTeX files (a comma "," instead of a point "." could appear as decimal separator). | JaxoDraw bug (all) | Closed (v.1.0-1) |
| #9 | If you switch to the various type of vertices, than it is not possible to get back again the default one (the dot). | JaxoDraw bug (all) | Closed (v.1.0-1) |
| #10 | The Antialias On/Off preference does not get saved. | JaxoDraw bug (all) | Closed (v.1.0-1) |
| #11 | The GridSize preference does not get applied to the current session. | JaxoDraw bug (all) | Closed (v.1.0-1) |
| #12 | If you installed JaxoDraw globally using the install.bsh shell script (or the Redhat rpm) you can execute the program but it takes quite long to come up. | JaxoDraw bug (all) | Closed (v.1.1-0) |
| #13 | If by mistake the user creates a zero size object (which is possible when the grid is on) the postscript generated is corrupted. | JaxoDraw bug (all) | Closed (v.1.1-0) |
| #14 | Some swing internal components do not allow full internationalization (see Sun's bug #4195173 ). For JaxoDraw, this effects only some text fields in the FileChooser, ColorChooser and Print dialogs, where the text will always be given in english. | Java bug #4195173 (all) | Open |
| #15 | With the version 1.4.2 of Sun's SDK, the text field "This color is:" + colorName is not displayed in the ColorChooser menu. See SUN's bug #5029286 , this seems not to have been solved. However, the color names are indicated in a pop-up menu when the color fields are rolled over. | Java bug #5029286 (all) | Closed (v.1.2-0) |
| #16 | The right-click pop-up menus (like on the vertex button and the tabs) do not change if a different Look and Feel is selected from the Options menu. | Java bug (all) | Open |
| #17 | Choosing the color of a LaTeX label did not affect the final LaTeX output. | JaxoDraw bug (all) | Closed (v.1.1-0) |
| #18 | If you copy an arrowed line, the copied line may flip the arrow direction. | JaxoDraw bug (all) | Closed (v.1.1-0) |
| #19 | The color of a group cannot be changed directly from the Color button of the edit menu. | JaxoDraw bug (all) | Closed (v.1.2-0) |
| #20 | After editing a group with LaTeX labels, the size of the latter is always set to "tiny". | JaxoDraw bug (all) | Closed (v.1.2-0) |
| #21 | When the grid is switched on and the canvas contains objects at an arbitrary position, if the latter are moved they get shifted by the grid size and not anchored to the grid points. | JaxoDraw bug (all) | Closed (v.1.2-0) |
| #22 | The use of colors is not consistent with the axodraw conventions: for example gray-scale lines are allowed, but axodraw allows gray-scales only as filling colors. This may cause problems when LaTeX compiling the diagram. | JaxoDraw bug (all) | Closed (v.1.2-0) |
| #23 | If a LaTeX text object is present at the edge of a graph then the bounding box of a "LaTeX -> EPS" export is most probably not correct. This manifests itself by a "broken" text, ie, a thin white line is crossing the text. Basically, there is no way for us to estimate the extension of a text after latex compilation, so the only workaround is to adjust the bounding box by hand. | JaxoDraw bug (all) | Open |
| #24 | If the program is executed via the jar file (which is the case for every binary distribution), then the User Guide can not be opened by most custom browsers. This is because some popular browsers do not support the jar protocol (among them Windows' Internet Explorer and Mac's Safari), i.e., they cannot open html files contained in a jar archive. Workaround: leave the preference for a custom HTML browser empty (in which case the HTML files are rendered by Java internally) or use a browser that supports the jar protocol (like Mozilla). | Browser limitation | Open |
| #25 | Mac OS X only: Printing or exporting to postscript/EPS does not work if a postscript text is present in the graph. We believe that this is a bug in Apple's Java implementation for MacOSX, or due to the fact that the Swing printing API is not fully implemented in J2SE 1.4.1 or 1.4.2 on Mac OS X (see Apple's Java issues page). Update: apparently, this has been fixed in the new 5.0 java release for MacOSX, however the spacing of texts is not correct. | Java bug (Mac) | Open |
| #26 | Mac OS X only: Saving files only works if the Look & Feel is different from the MacOSX native Aqua. This is only because the Aqua file chooser dialog does not provide a text field for typing a file name. If a file exists already, you can click on it and the graph will get saved correctly. Workaround: temporarily change to another Look & Feel (Metal is recommended). | Apple's Java bug (Mac) | Open |
| #27 | Mac OS X only: The visible grid points do not match the actual grid points. | Apple's Java bug (Mac) | Open |
| #28 | Closing curly brackets } do not display in postscript texts. | JaxoDraw bug (all) | Closed (v.1.2-0) |
| #29 | Creating an empty Postscript label by editing a non-empty label and erasing its text results in an exception. | JaxoDraw bug (all) | Closed (v.1.3-0) |
| #30 |
Dragging the mouse when choosing the last point defining an arc
cause strange behavior of the arc objects (the arc may be
drawn in red, or may not be drawn at all because the three
points are collapsing to a line).
Workaround: Avoid dragging (!); however notice that subsequent editing of the arc object is possible and in that case the arc will display normally. |
JaxoDraw bug (all) | Closed (v.1.3-0) |
| #31 | If the arc is too small nothing will be drawn on screen. | JaxoDraw bug (all) | Closed (v.1.3-0) |
| #32 |
JaxoDraw crashes on Debian Linux Systems (and maybe others
if certain fonts are installed).
Workaround: For a workaround read this news entry. |
Java bug #4994629 | Closed (v.1.3-0) |
| #33 |
If you use Java 5.0 to run JaxoDraw you will
not be able to bring up the preference panel due to an
ArrayOutOfBounds
exception at run time (which is absent if you run it with
any previous Java distribution).
Workaround: For a workaround read this news entry. |
Java 5.0 problem (all) | Closed (v.1.3-0) |
| #34 |
Arcs are messed up when re-opening saved files.
Workaround: For a workaround read this news entry. |
JaxoDraw bug (all) | Closed (v.1.3-0) |
| #35 |
File operations (Open, Save, Import, ...) do not work on Windows
if the path to the file contains white spaces.
Workaround: Use only file- and path names that do not contain white spaces. |
JaxoDraw bug (Windows) | Open |
| #36 |
Opening several tabs on Windows freezes the program.
This is apparently a memory problem, running
JaxoDraw from a console gives an error message:
"AWT-EventQueue-0" Java.lang.OutOfMemoryError".
Workaround:
Increase the size of the Java memory allocation pool
(with the |
Java problem (Windows) | Open |
| #37 |
Photon and gluon arcs are not correctly exported to LaTeX.
For some combinations of arc points and symmetry parameter,
the starting- and end angle of the LaTeX command for these arcs
are ordered in the wrong way.
Workaround: In the generated tex file, manually exchange the angle parameters and/or change the sign of the amplitude. |
JaxoDraw bug (all) | Closed (v.1.3-0) |
| #38 |
Editing the coordinates of a line object does not work.
This bug was introduced in the 1.3-0 release.
|
JaxoDraw bug (all) | Closed (v.1.3-1) |
| #39 | No JaxoDraw executable is found after a local install on Linux using the ant script. | JaxoDraw bug (Linux) | Closed (v.1.3-1) |
| #40 | Changing the fill color of a fill object to a gray scale and back to a non-gray scale always sets the line color to black in the edit panel. It should preserve the color that was set before (if it was not black), only when the user presses the final accept button of the edit dialog, should the line color be set to black. | JaxoDraw bug (all) | Closed (v.1.3-2) |
| #41 | When drawing a double line and making the double line separation bigger than the default one, the line is not drawn correctly. | JaxoDraw bug (all) | Closed (v.1.3-2) |
| #42 | Editing a postscript text does not work in a saved and re-opened graph. | JaxoDraw bug (all) | Closed (v.1.3-2) |
| #43 | When entering a new LaTeX/PS text, the panel does not have focus, i.e., one is obliged to click on the text field in order to enter some text. | JaxoDraw bug (all) | Closed (v.1.3-2) |
| #44 |
Arc drawing bugs:
|
JaxoDraw bug (all) | Closed (v.1.3-2) |
| #45 | Several latex import bugs: Lines and arcs with arrows at the end (axodraw commands \LongArrow,\LongArrowArc and \LongArrowArcn) are ignored when doing a latex import. A colored vertex always gets it's color reset to black. The latex command \CCirc is not imported. | JaxoDraw bug (all) | Open |
| #46 | When setting the allignment property of a latex text to cc (center-center) and the rotation angle to a non-zero value, the resulting latex file cannot be compiled (error message: Unexpected empty argument). | JaxoDraw bug (all) | Open |
| #47 | Trying to resize a triangular vertex from the point that was last clicked when it was drawn, doesn't do anything. | JaxoDraw bug (all) | Open |
|