| "Select tag" dialogue focus issues [message #213311] |
Fri, 01 June 2007 14:43  |
Eclipse User |
|
|
|
Originally posted by: ssoiland.cs.man.ac.uk
Hi!
First of all, I found it quite hard figuring out which newsgroup to post
this to. I might post this as a bug instead.
I'm using Eclipse 3.2.2 on OS X, with a project checked out using the
built-in CVS team support.
Say I want to switch my checked out version from HEAD to a specific tag. I
right-click on the project and select Team -> Switch to another tag or
version.
Everything fine so far. I have previously done the "Configure tags" bit,
so I know my tag is in "Versions" somewhere. I click on "Versions" to
expand the tree. Nothing happens. I click on any of the "Matching tags"
and nothing happens.
I start believing Eclipse have forgotton all tags, and do Refresh tags and
Configure tags again, but still nothing happens.
Then I realise that I have to select the radio button "Select the tag from
the following list" before making a selection from the big list of tags.
Eclipse had not forgotten anything, it just refused my clicks.
I've done this mistake probably 10 times for the last 6 months, and I feel
just as stupid as annoyed every time.
1) If those "Matching tags" can't be selected until the correct radio
button has been clicked, they should be greyed out, otherwise I believe I
can click them. A better solution is that clicking here automatically
flips the radio button for me, after all, if I make a specific choice
that's what I mean, right?
2) Why is "Use the tag currently associated with the workspace resource"
the default in the first place? There's no point in switching version to
the very same version, is there? I believe this dialogue is re-used also
from other pop-ups, but that's still not a very good excuse for the
default in this case.
|
|
|
| Re: "Select tag" dialogue focus issues [message #213565 is a reply to message #213311] |
Sun, 03 June 2007 23:52  |
| Eclipse User |
|
|
|
Originally posted by: eclipse5.rizzoweb.com
Stian Soiland wrote:
> Hi!
>
> First of all, I found it quite hard figuring out which newsgroup to post
> this to. I might post this as a bug instead.
>
>
> I'm using Eclipse 3.2.2 on OS X, with a project checked out using the
> built-in CVS team support.
>
> Say I want to switch my checked out version from HEAD to a specific tag.
> I right-click on the project and select Team -> Switch to another tag or
> version.
>
> Everything fine so far. I have previously done the "Configure tags" bit,
> so I know my tag is in "Versions" somewhere. I click on "Versions" to
> expand the tree. Nothing happens. I click on any of the "Matching tags"
> and nothing happens.
>
> I start believing Eclipse have forgotton all tags, and do Refresh tags
> and Configure tags again, but still nothing happens.
>
>
> Then I realise that I have to select the radio button "Select the tag
> from the following list" before making a selection from the big list of
> tags. Eclipse had not forgotten anything, it just refused my clicks.
>
>
> I've done this mistake probably 10 times for the last 6 months, and I
> feel just as stupid as annoyed every time.
>
>
>
> 1) If those "Matching tags" can't be selected until the correct radio
> button has been clicked, they should be greyed out, otherwise I believe
> I can click them.
The entire section with the tree (HEAD, Branches, Versions, Dates, etc)
is disabled unless the "Select the tag..." radio option is chosen, at
least on Windows. Is it possible that the Mac rendering of disabled
trees is just very subtle and you didn't notice it?
However, the 3 buttons are enabled all the time, which I think is
misleading. You should probably file a bug about that, since clicking
them does work but the result is not visible in the UI unless "Select
the tag..." is chosen.
> 2) Why is "Use the tag currently associated with the workspace resource"
> the default in the first place? There's no point in switching version to
> the very same version, is there? I believe this dialogue is re-used
> also from other pop-ups, but that's still not a very good excuse for the
> default in this case.
That I can't answer. I'm sure there's a reason, but it might be obsolete
or somewhat obscure.
Hope this helps,
Eric
|
|
|
Powered by
FUDForum. Page generated in 0.07620 seconds
] 
Search
Help
Register
Login
Home
