Need menu item to run update on working tree

[Alexander Belchenko]

I have lightweight checkout of branch with working tree (actual copy of qbzr trunk, checkout in my plugins folder). I'm working all the time in the checkout, therefore master branch working tree regularly going out of date (because it's not updated at all). I want to do some operations on master branch but can't find a way to run Update command (either qupdate dialog or qgetupdates hybrid dialog).

[Ian Clatworthy (ian-clatworthy)]

The error message says to run 'update' doesn't it? If so, we need qupdate to work in that case I feel.

[Alexander Belchenko (bialix)]

Ian Clatworthy пишет:
> The error message says to run 'update' doesn't it? If so, we need
> qupdate to work in that case I feel.
>

In the status view there is standard message:

"Working tree is out of date, please run 'bzr update'."

But I don't see Update action anywhere in the menu.
Perhaps we can just provide button directly in status view to invoke qupdate?

[Ian Clatworthy (ian-clatworthy)]

Bazaar > Collaborate > Update Working Tree *ought* to do it but it's mapped to qgetupdates instead of qupdate. Should I change the mapping?

[Alexander Belchenko (bialix)]

Ian Clatworthy пишет:
> Bazaar > Collaborate > Update Working Tree *ought* to do it but it's
> mapped to qgetupdates instead of qupdate. Should I change the mapping?
>

Oops.

[Alexander Belchenko (bialix)]

Ian Clatworthy пишет:
> Bazaar > Collaborate > Update Working Tree *ought* to do it but it's
> mapped to qgetupdates instead of qupdate. Should I change the mapping?

Sorry Ian, it seems I've missed this menu item yesterday. It was late
night. But... for updating working tree of standalone branch (not
checkout!) I've don't expecting to see update working tree in
Collaborate. Perhaps I'm not completelly understand your design decision
about Work vs Collaboration (vs Explore...). Maybe we need discuss it
more in bzr-explorer-dev ML?

But anyway, I think will be nice to have shortcut icon available
directly in status view for update action, as you did for conflicts or
commit changes etc.

About qgetupdates vs qupdate. The former is a combine and it's actually
the mix between pull and update. You have separate pull option in
Collaborate so qgetupdates seems for me as overkill. qupdate is musch
simpler and do only one job: run `bzr update`.

Also qgetupdates has bug re updating light checkouts, but this is
fixable of course.

In the end I believe you design skills here and your intuition. But I'm
trying to provide feedback as regular user not as co-developer.

[Ian Clatworthy (ian-clatworthy)]

Fixed in rev 234 I believe.