Community
Participate
Working Groups
Build Identifier: 3.6.0 M6 I reported Bug #309774 a few minutes ago and was forced to write an lengthy warning message because I could not select the text with my mouse. This is strange, nearly every widget set supports this in Linux and it simplifies copying text a lot. Please provide this as well (you will probably have to reassign this to platform or whetever ...). Reproducible: Always
Just to be sure we are talking about the same thing, you want the message in the dialog warning about the absence of signature to be selectable. I suppose this may also be true in other dialogs.
(In reply to comment #1) > Just to be sure we are talking about the same thing, you want the message in > the dialog warning about the absence of signature to be selectable. Right. > I suppose this may also be true in other dialogs. Yes, this should be possible in most other dialogs as well. PS: I forgot: I use the gtk variant (haven't tested the Motif frontend).
this isn't going to get fixed so late in the release, sorry. We use the JFace warning dialog and fixing this would mean using our own dialog. Also, there's not really valuable info in here (such as the list of unsigned items) so there's not high value in making this copyable. I think this should be addressed when we polish the dialog to include the list of unsigned items (there are comments in the code indicating this should be done).
(In reply to comment #3) > We use the JFace warning dialog and fixing this would mean using our own > dialog. I don't worry about p2 so much but about the general situation. If the JFace dialog has the problem why not reassign this bug to it? > Also, there's not really valuable info in here (such as the list of unsigned > items) so there's not high value in making this copyable. Right, but there are many other dialogs which contain valuable info.
(In reply to comment #4) > (In reply to comment #3) > > We use the JFace warning dialog and fixing this would mean using our own > > dialog. > > I don't worry about p2 so much but about the general situation. If the JFace > dialog has the problem why not reassign this bug to it? > > > Also, there's not really valuable info in here (such as the list of unsigned > > items) so there's not high value in making this copyable. > > Right, but there are many other dialogs which contain valuable info. A bit of history here. There are two error dialogs, a "pure JFace error dialog" used in JFace-only software where the rest of the Eclipse platform is not present, and the Eclipse status handling error dialog used in most places. It so happens that the unsigned warning dialog uses the former. The latter has copy/paste support and is set up to show all kinds of error details. The simple JFace dialog does not provide copy/paste support. If the message were made into a read-only text (which is how we do the select/clipboard support), then you'd have keyboard traversal stopping on the message. In the simple case, we don't want that to happen. Some dialogs provide this behavior to support accessibility - that is, a screen reader can read it for the blind if the user can traverse to it, but the JFace dialog supports accessibility using a special platform accessible listener, so this is not necessary. All that is to say that we should have a more detailed "unsigned dialog" that uses either the platform status reporting dialog or a custom dialog, and it should list the things that are unsigned, and those should be copyable for sure. So I've left the bug here to track that discussion. (Incidentally, for simple static message boxes, most people just attach a screenshot to the bug report if there is some question about what the dialog means or why they got it.)
see also bug 318904
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. -- The automated Eclipse Genie.
