Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 364730

Summary:	dialog created by input handle shouldn't be modal
Product:	[Eclipse Project] Platform	Reporter:	Sven Köhler <sven.koehler>
Component:	Ant	Assignee:	Platform-Ant-Inbox <platform-ant-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	satyam.kandula
Version:	3.7.1
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:	stalebug

Description Sven Köhler

2011-11-24 11:42:32 EST

Build Identifier: 

Hi,

Eclipse defined an input handler which opens a dialog.
When you select "run in same JRE as the workspace" for the ant build, then the dialog is model. If you select another JRE the dialog is not modal (since the ant build runs in another JVM, of course).

I think that a modal dialog is a bad thing. First of all, because you can't switch to the console view and scroll up&down to see the list of options that you can enter. In the example build.xml below, the set of valid options is displayed using echo (in my real use-case, the lists consists of about 80 options).


Reproducible: Always

Steps to Reproduce:
<project name="samples" default="help" basedir=".">
	<target name="help">
		<echo>List of options</echo>
		<input message="Enter one of the options:" addproperty="foo.bar1"/>
	</target>
</project>

Comment 1 Satyam Kandula

2011-11-25 05:58:16 EST

They are advantages of making it non-modal, but just the other day I didn't know that my build.xml was waiting for my input :(.

Comment 2 Sven Köhler

2011-11-25 06:52:18 EST

(In reply to comment #1)
> They are advantages of making it non-modal, but just the other day I didn't
> know that my build.xml was waiting for my input :(.

I wouldn't object something half-modal: a dialog, that stays in front of the main window, but I can still switch to the console view, scroll the console, etc.
But I don't know, if something like that even exists.

However, it wouldn't work for any ant build that's running in an external JVM anyway. Maybe one can find something to alert the user about the the input dialog.
One obvious thing would be to print some message to the console about the dialog.

Comment 3 Lars Vogel

2019-11-14 03:15:27 EST

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.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.