You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jörn Kottmann (JIRA)" <de...@uima.apache.org> on 2010/11/26 12:12:13 UTC
[jira] Created: (UIMA-1950) Filling a feature in the Edit View is
difficult if it not has a value yet
Filling a feature in the Edit View is difficult if it not has a value yet
-------------------------------------------------------------------------
Key: UIMA-1950
URL: https://issues.apache.org/jira/browse/UIMA-1950
Project: UIMA
Issue Type: Bug
Reporter: Jörn Kottmann
Philip Ogren:
"On a related note - I have noticed that filling the value of e.g. a feature of type string is really hard to do if it does not yet have a value. The problem is that it requires extremely precise mouse movements to activate the cursor in the empty text field. This is very tiresome for situations in which the text is not pre-annotated automatically."
(was reported together with UIMA-1875)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (UIMA-1950) Filling a feature in the Edit View is
difficult if it not has a value yet
Posted by "Jörn Kottmann (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jörn Kottmann updated UIMA-1950:
--------------------------------
Component/s: CasEditor
Affects Version/s: 2.3.1SDK
Assignee: Jörn Kottmann
The UI code which does the update throws an exception. It should be investigated what exactly is causing the exception and if that is related to this issue. And the exception should logged here.
> Filling a feature in the Edit View is difficult if it not has a value yet
> -------------------------------------------------------------------------
>
> Key: UIMA-1950
> URL: https://issues.apache.org/jira/browse/UIMA-1950
> Project: UIMA
> Issue Type: Bug
> Components: CasEditor
> Affects Versions: 2.3.1SDK
> Reporter: Jörn Kottmann
> Assignee: Jörn Kottmann
>
> Philip Ogren:
> "On a related note - I have noticed that filling the value of e.g. a feature of type string is really hard to do if it does not yet have a value. The problem is that it requires extremely precise mouse movements to activate the cursor in the empty text field. This is very tiresome for situations in which the text is not pre-annotated automatically."
> (was reported together with UIMA-1875)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (UIMA-1950) Filling a feature in the Edit View is
difficult if it not has a value yet
Posted by "Jörn Kottmann (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12935984#action_12935984 ]
Jörn Kottmann commented on UIMA-1950:
-------------------------------------
Here is the exception:
org.eclipse.core.runtime.AssertionFailedException: assertion failed:
at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110)
at org.eclipse.core.runtime.Assert.isTrue(Assert.java:96)
at org.eclipse.jface.viewers.TextCellEditor.doSetValue(TextCellEditor.java:228)
at org.eclipse.jface.viewers.CellEditor.setValue(CellEditor.java:855)
at org.eclipse.jface.viewers.EditingSupport.initializeCellEditorValue(EditingSupport.java:100)
at org.eclipse.jface.viewers.ColumnViewerEditor.activateCellEditor(ColumnViewerEditor.java:194)
at org.eclipse.jface.viewers.ColumnViewerEditor.handleEditorActivationEvent(ColumnViewerEditor.java:444)
at org.eclipse.jface.viewers.ColumnViewer.triggerEditorActivationEvent(ColumnViewer.java:680)
at org.eclipse.jface.viewers.ColumnViewer.handleMouseDown(ColumnViewer.java:664)
at org.eclipse.jface.viewers.ColumnViewer.access$0(ColumnViewer.java:660)
at org.eclipse.jface.viewers.ColumnViewer$1.mouseDown(ColumnViewer.java:89)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:185)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:3776)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1367)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1390)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1375)
at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1187)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3622)
at org.eclipse.swt.widgets.Display.applicationNextEventMatchingMask(Display.java:4479)
at org.eclipse.swt.widgets.Display.applicationProc(Display.java:4739)
at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:220)
at org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1025)
at org.eclipse.swt.widgets.Tree.mouseDownSuper(Tree.java:1960)
at org.eclipse.swt.widgets.Widget.mouseDown(Widget.java:1021)
at org.eclipse.swt.widgets.Control.mouseDown(Control.java:2240)
at org.eclipse.swt.widgets.Tree.mouseDown(Tree.java:1937)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:4976)
at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:220)
at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:1943)
at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2008)
at org.eclipse.swt.widgets.Display.windowProc(Display.java:5040)
at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:4582)
at org.eclipse.swt.widgets.Display.applicationProc(Display.java:4659)
at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)
at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:115)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3274)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2629)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2593)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
at org.eclipse.equinox.launcher.Main.run(Main.java:1407)
at org.eclipse.equinox.launcher.Main.main(Main.java:1383)
> Filling a feature in the Edit View is difficult if it not has a value yet
> -------------------------------------------------------------------------
>
> Key: UIMA-1950
> URL: https://issues.apache.org/jira/browse/UIMA-1950
> Project: UIMA
> Issue Type: Bug
> Components: CasEditor
> Affects Versions: 2.3.1SDK
> Reporter: Jörn Kottmann
> Assignee: Jörn Kottmann
>
> Philip Ogren:
> "On a related note - I have noticed that filling the value of e.g. a feature of type string is really hard to do if it does not yet have a value. The problem is that it requires extremely precise mouse movements to activate the cursor in the empty text field. This is very tiresome for situations in which the text is not pre-annotated automatically."
> (was reported together with UIMA-1875)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (UIMA-1950) Filling a feature in the Edit View is
difficult if it not has a value yet
Posted by "Jörn Kottmann (JIRA)" <de...@uima.apache.org>.
[ https://issues.apache.org/jira/browse/UIMA-1950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jörn Kottmann closed UIMA-1950.
-------------------------------
Resolution: Fixed
Fix Version/s: 2.3.1SDK
The cell editor was set to "null" which is not an allowed value and caused the exception. In case the feature is null its replaced by an empty string, the first edit will set the feature to be an empty string, returning to "null" as a feature value is not possible currently.
> Filling a feature in the Edit View is difficult if it not has a value yet
> -------------------------------------------------------------------------
>
> Key: UIMA-1950
> URL: https://issues.apache.org/jira/browse/UIMA-1950
> Project: UIMA
> Issue Type: Bug
> Components: CasEditor
> Affects Versions: 2.3.1SDK
> Reporter: Jörn Kottmann
> Assignee: Jörn Kottmann
> Fix For: 2.3.1SDK
>
>
> Philip Ogren:
> "On a related note - I have noticed that filling the value of e.g. a feature of type string is really hard to do if it does not yet have a value. The problem is that it requires extremely precise mouse movements to activate the cursor in the empty text field. This is very tiresome for situations in which the text is not pre-annotated automatically."
> (was reported together with UIMA-1875)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.