Use this page to enumerate Bugs in the application
Note: this list should be distinct from the tasks listed on the Spring 2008 Primary Task List page. These should be general defects we want to track and eventually fix. The intent is migrate these to JIRA when it is configured.
1. If you right click and drag anywhere on the fluency frame you will draw a black line. When you release (the first time) the line will turn green and (usually) not disappear unless you cause some kind of repaint to occur. If you then attempt to repeat, the black line will draw, but upon mouse release will disappear. Need to confirm if this is windows specific.
Update: this appears to be related to the GestureRecognition Plugin. Leaving it as an issue for now because I don't think MouseGestureCapturer should be the global MouseListener by default.
2. After I create a Molecule widget , and I try to drag the widget into the Fluency Application. I then try to add connection. While doing so Fluency crashes. (P.S: This not used to happen till last week but after I took a latest update today it started happening)
3. The widget buttons loaded on the widget tool bar do not allow the user to select and use a widget. Also, the tool tips displayed on the tool bar are not the same as the ones displayed in the WidgetFinder. In principle there should be no difference to the way these icons are loaded and initialized. Need to refactor this. The current code is in SearchButton.java (which has access to the full widget class name) and PluginTool.java (which has access to only the widget description). I think the code should be extracted from both locations and put into a utility class called something like WidgetIcon.
4. If you delete a widget, the existing connections are necessarily deleted. If you then choose to undo, the anti-command in DeleteWidgetCommand does not restore the previous connections (pre-existing problem).
5. When you make connections you sometimes have a "dangling connection" that does not go away unless you click in a specific location (on the editor model or the tool bar), if you click on a menu item it does not terminate that connection, for example. Have looked at the code, and at somepoint we should refactor the way it works.
6. Remove sysouts from the codebase.
7. When selecting widgets from the tool bar in windows, they do not highlight with a border like they do in linux (and presumably in mac os). This highlight/selection should be the default behavior.
8. If two fluency application windows are open in editor mode, fluency is having trouble distinguishing between them internally. This results in the following behavior:
- If you place a widget on each window, delete one and then the other. Then try t undo, they will not undo as expected (the anti-commands seem confused – haven't debugged deeply)
- If you toggle back and forth between each window and do things on each (like add widgets and/or connections) – you eventually will get a ClassCastException in FluencyModel.uncoverWidget().
9. WidgetProperties getProperty() is producing numerous class cast exceptions. This is because sometimes a null Object is returned when a more specific type is expected (such as Point).
10. When in edit mode, select to save current application. File save dialog appears. If this dialog is positioned over the existing app, as you move your mouse inside the bounds of the dialog (to select the appropriate folder etc), the highlighting commands also execute on the application you are attempting to save. This does NOT happen if you move the mouse outside of the dialog and hover over controls on the application. Only happens when mouse is moved in the bounds of the save file dialog and should not happen.
11. When multiple fluency applications opened in the editor, some behaviors stop working. For example:
- widget finder does not always work (and sometimes cannot drag widgets)
- widget and connection sensitive right click stops working
- have noticed other anomalies as well, need to look at what is happening in the glass pane and how/where events are propagated
12. When more than one connection is leaving a widget but also goes to the same import dock (but calls a separate trigger method), the mouse over connection detail only shows the first connection added, regardless of which connection you hover over. You will only see detail of ALL connections if you hover over ALL the connections simultaneously (which can be a bit tricky). This is a bug in link modification changes made this semester.
13. View menu and PluginCore components not working as they should.
- there is a check that is used for toggling items on the menu. if you close the window, the check box does not go away manually. If you then want to redisplay the window (after closing it), you have to then select the View menu twice and click the window you want twice (once to uncheck, and then once to check). Is annoying.
14. Also, related to view menu item. The property editor window was added last term to the View Menu so it could be re-opened if closed. This is a nice and important feature but there are still some bugs.
- there is a problem repainting if you try to hide the property editor window by toggling the check on the view menu. My gut reaction is that this window is not setup properly as as a plugin core object. (During debugging I noticed that the "name" of the property editor window is "DefaultPluginName" but all the other items on this menu have a plugin name)
15. Linux repainting problem when you drag the application frame inside the editor frame. Does not happen on windows or mac (this maybe related to either the java version or red hat verion used). reports indicate that this is not a universal red hat problem.
16. If you start a fluency app, save as molecule, then click on a widget to get a the popup used to add the name of the input dock. If you close the molecule window before you type the name, the molecule window closes but the popup window does not. There is no way to get rid of it without closing fluency.
