Bug 306282 - [EditorMgmt] After running a program the text file becomes uneditable
Summary: [EditorMgmt] After running a program the text file becomes uneditable
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.5.2   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-17 16:45 EDT by dcentore CLA
Modified: 2019-09-06 16:07 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dcentore CLA 2010-03-17 16:45:53 EDT
Build Identifier: 20100218-1602

Whenever I run a program that uses only a JOptionPane for input, after the application exits the editor becomes unusable, with a grayed out tab and only the ability to highlight text. To fix it you can minimize and unminimize eclipse, which gets annoying fast. The code that can be used to test is:

String s1 = (String)JOptionPane.showInputDialog(null, "Insert 1st number", "Input Dialog", JOptionPane.PLAIN_MESSAGE);

Note that I am currently using Ubuntu Intrepid to due a graphics card incompatibility, though I have experienced this problem on Jaunty and Karmic.

Reproducible: Always

Steps to Reproduce:
1.Create a new project and main class
2.in main() simply add "String s1 = (String)JOptionPane.showInputDialog(null, "Insert 1st number", "Input Dialog", JOptionPane.PLAIN_MESSAGE);"
3.Run the program and press enter at the dialog
4.The editor tab is now grayed out and the application cannot be used
Comment 1 Remy Suen CLA 2010-03-17 20:04:24 EDT
What versions of GTK+ do you have installed? Does the error occur with regular text editors (instead of Java editors)?

Can you reproduce the problem with 3.6M6?
http://download.eclipse.org/eclipse/downloads/drops/S-3.6M6-201003121448/index.php
Comment 2 dcentore CLA 2010-03-17 20:33:32 EDT
(In reply to comment #1)
> What versions of GTK+ do you have installed? Does the error occur with regular
> text editors (instead of Java editors)?
> 
> Can you reproduce the problem with 3.6M6?
> http://download.eclipse.org/eclipse/downloads/drops/S-3.6M6-201003121448/index.php

GTK Version 1.2.10

This does not occur with regular editors, but im not sure how I would reproduce this bug using gedit, openoffice, etc...

Downloading 3.6M6 right now ill let you know how that goes (internets a bit on the slow side today...)
Comment 3 Remy Suen CLA 2010-03-17 20:40:57 EDT
(In reply to comment #2)
> GTK Version 1.2.10

That's one installation. There should be another one that's 2.x.y.

> This does not occur with regular editors, but im not sure how I would reproduce
> this bug using gedit, openoffice, etc...

By text editors I meant if you open a text file in Eclipse (a text editor) instead of a Java file (which would use the Java editor with syntax highlighting and such).
Comment 4 dcentore CLA 2010-03-17 20:55:29 EDT
(In reply to comment #3)
> (In reply to comment #2)
> > GTK Version 1.2.10
> 
> That's one installation. There should be another one that's 2.x.y.
> 
> > This does not occur with regular editors, but im not sure how I would reproduce
> > this bug using gedit, openoffice, etc...
> 
> By text editors I meant if you open a text file in Eclipse (a text editor)
> instead of a Java file (which would use the Java editor with syntax
> highlighting and such).

OK I tried 3.6 and the same problem occurs though I have noticed that I need to wait about 3 seconds before clicking on the text (code) editor for the problem to occur.
Comment 5 Prakash Rangaraj CLA 2010-05-25 02:38:11 EDT
Remy,
   Its on you or should we move this to Platform Text?
Comment 6 Remy Suen CLA 2010-05-25 06:00:09 EDT
decentore, if you start such a Swing application from the command line, does it affect your Eclipse text editors?
Comment 7 Eclipse Webmaster CLA 2019-09-06 16:07:58 EDT
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.

If you have further information on the current state of the bug, please add it. 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.