Community
Participate
Working Groups
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 Build Identifier: M20060629-1905 I have an Eclipse View that uses SWT_AWT bridge to embed JTable with editable cell. Double clicking the cell in the table will make that cell to be in edit mode and the focus (the cursor) will blink for user input. Then I switch to different application (e.g. Microsoft Excel) and copy some string in that Excel. When I come back to my Eclipse Application, the focus in the selected cell in the JTable has lost (e.g. cursor no longer blinks). I have to double click again to the table cell to make it editable. This is not the right behavior and only happens if using SWT_AWT bridge. The focus should stay in the table cell even though user switches from one application to another. For comparison, in pure Swing application, this focus always stays in the table cell no matter how many times end user switches to different applications. I've created a small Eclipse project to illustrates this problem. Please download it from the attachment and launch is as Eclipse Application. Reproducible: Always Steps to Reproduce: 1.Using the sample Eclipse project, launch the project as Eclipse Application. 2.In the main view on the right, double click the cell in the JTable and try to edit some value and keep it in edit mode (e.g. make sure the cursor blinks) 3.Open some other application (e.g. Microsoft Word, Excel, etc) and copy some string in that application. 4.Go back to the sample application, you will notice that the focus has lost in the table cell. The right behavior should be the focus always stays in that table cell.
Created attachment 152199 [details] Sample Program for Bug 295113 SWT_AWT Focus Lost issue with JTable
This is a one-off bulk update. (The last one in the triage migration). Moving bugs from swt-triaged@eclipse to platform-swt-inbox@eclipse.org and adding "triaged" keyword as per new triage process: https://wiki.eclipse.org/SWT/Devel/Triage See Bug 518478 for details. Tag for notification/mail filters: @TriageBulkUpdate
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.