This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 228665 - Subversion Window does not update automatically when another project is selected
Summary: Subversion Window does not update automatically when another project is selected
Status: REOPENED
Alias: None
Product: versioncontrol
Classification: Unclassified
Component: Subversion (show other bugs)
Version: 7.3
Hardware: PC Windows 7
: P3 normal with 1 vote (vote)
Assignee: Ondrej Vrabec
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-17 15:20 UTC by dave0783
Modified: 2013-04-17 19:34 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description dave0783 2013-04-17 15:20:51 UTC
After opening the editor and selecting a project, if you navigate to Window > Versioning > Subversion, the IDE will open the Subversion window as expected; however, it will not be for the currently active project as expected.  I find that the windows contents is for the project you last worked on that used subversion.  I feel this is unexpected behavior and possibly a bug.  Ideally, the Subversion window should update automatically when you switch projects as the window can be pinned in place.
Comment 1 Ondrej Vrabec 2013-04-17 15:38:22 UTC
> I find that the windows contents is for the project you last worked on that used subversion.
exactly
> I feel this is unexpected behavior and possibly a bug.
no
The window is just opened, nothing else. To change the project you want to see use Subversion -> Show Changes for the required project.
Comment 2 dave0783 2013-04-17 15:59:53 UTC
(In reply to comment #1)
> > I find that the windows contents is for the project you last worked on that used subversion.
> exactly
> > I feel this is unexpected behavior and possibly a bug.
> no
> The window is just opened, nothing else. To change the project you want to see
> use Subversion -> Show Changes for the required project.

I understand that you can use Subversion -> Show Changes; however, this is highly inconvenient, especially if you do not have the window open already and you open it as I described; the window that opens will not be for the current project, you will need to do an extra step to get the window to be on the correct project.  

If you take the Navigator for example, you do not have to refresh the navigator when you open a new file, it does so automatically; when you open a new project, this window should behave in the same manor; it should update automatically to show you the project you are working on.
Comment 3 Ondrej Vrabec 2013-04-17 16:04:14 UTC
The action has been removed anyway in 7.4. Sorry, i am simply not going to fix it. It's been working this way for over 5 years and i am not going to change its behavior. All versioning views work this way, they keep their context until you change it manually.
Comment 4 dave0783 2013-04-17 16:18:28 UTC
(In reply to comment #3)
> The action has been removed anyway in 7.4. 

Nice, I'm looking forward to 7.4.  Out of curiosity, what will this process be being changed to?

> Sorry, i am simply not going to fix it. 

I guess its clear that your not even open to the idea of fixing it.  I will still maintain that this is an inefficient process.

> It's been working this way for over 5 years and i am not going to change
> its behavior. All versioning views work this way, they keep their context until
> you change it manually.

Just because it has been working one way does not mean that its working the right way. At this point, I guess I'm just suggesting a way to make things more efficient for the dev using the IDE.

Sorry if I have wasted your time.
Comment 5 Ondrej Vrabec 2013-04-17 16:26:56 UTC
> Nice, I'm looking forward to 7.4.  Out of curiosity, what will this process be
> being changed to?
As i already said, what you're looking for is exactly another action and that is Subversion -> Show Changes.
> I guess its clear that your not even open to the idea of fixing it.  I will
> still maintain that this is an inefficient process.
> Just because it has been working one way does not mean that its working the
> right way. At this point, I guess I'm just suggesting a way to make things more
> efficient for the dev using the IDE.
> Sorry if I have wasted your time.
I just don't think that we must have several different actions with different names doing exactly the same thing. Subversion -> Show Changes changes the scope the view works on and displays its modified files. Versioning -> Subversion now (at least in 7.3) simply opened the view and did not change it. What you suggested was to make it an equivalent of Show Changes which would make the action useless, redundant and confusing, don't you think? So the fact the action was actually removed is for your benefit, because you'll have just one action doing the work you expect, right?
Comment 6 dave0783 2013-04-17 16:52:50 UTC
(In reply to comment #5)
> > Nice, I'm looking forward to 7.4.  Out of curiosity, what will this process be
> > being changed to?
> As i already said, what you're looking for is exactly another action and that
> is Subversion -> Show Changes.
> > I guess its clear that your not even open to the idea of fixing it.  I will
> > still maintain that this is an inefficient process.
> > Just because it has been working one way does not mean that its working the
> > right way. At this point, I guess I'm just suggesting a way to make things more
> > efficient for the dev using the IDE.
> > Sorry if I have wasted your time.
> I just don't think that we must have several different actions with different
> names doing exactly the same thing. Subversion -> Show Changes changes the
> scope the view works on and displays its modified files. Versioning ->
> Subversion now (at least in 7.3) simply opened the view and did not change it.
> What you suggested was to make it an equivalent of Show Changes which would
> make the action useless, redundant and confusing, don't you think? 

I think our disconnect here is that I believe its more efficient for the dev not to have to right click on the project and go to show changes, especially if they already have the Subversion window open and possibly hidden.  I believe that the most efficient process would be 1) open netbeans, 2) choose your project 3) make your changes 4) hover over the minimized Subversion window 5) press the commit button.  Instead, I find my self doing steps 1-4, not noticing that I am on the wrong project, and not seeing my modifications.  I then have to right click the project go to Subversion -> Show Changes and then continue to step 5.  If you take the navigator for example, when you open a file, it automatically updates to reflect the file you have open.  If I had to right click the navigator and "refresh" every time I opened a file, I simply would not use it.  The same concept holds true with the Subversion window; Maybe the issue is the fact that the Subversion window remains open all the time, I don't know.

> So the fact the action was actually removed is for your benefit, because you'll have just one action doing the work you expect, right?
Comment 7 Ondrej Vrabec 2013-04-17 18:21:56 UTC
What you're describing is a different issue/request you originally posted:
> After opening the editor and selecting a project, if you navigate to Window >
> Versioning > Subversion, the IDE will open the Subversion window as expected;
> however, it will not be for the currently active project as expected.  I find
> that the windows contents is for the project you last worked on that used
> subversion.
Comment 8 dave0783 2013-04-17 19:34:13 UTC
(In reply to comment #7)
> What you're describing is a different issue/request you originally posted:
> > After opening the editor and selecting a project, if you navigate to Window >
> > Versioning > Subversion, the IDE will open the Subversion window as expected;
> > however, it will not be for the currently active project as expected.  I find
> > that the windows contents is for the project you last worked on that used
> > subversion.

Not really, the only difference is that I already had the window open as opposed to manually opening it. I apologize if I conveyed my issue incorrectly.