I'm currently using the latest version listed on the TortoiseHg homepage,
which is 2.0.5 64bit on Win 7.
>> Firstly a minor niggle. The Patch Queue button does not toggle the Patch
>> Queue view, so once you have entered Patch Queue view there is no obvious
>> way to exit back to the normal repository view.
> Click on Revision Details tab
I see how toggling the different views works now. Damn I'm pretty dim not to
have worked that out : /
>> The Graph Log view is the same. Only the last applied patch has any diff
>> associated with it and that also doesn't show the diff of the last
applied
>> patch but the diff for the entire stack of applied patches.
> The displayed diff is the one corresponding to the selected patch.
No, not on the version I'm using.
If I create a test project. Then create two patches Patch1 and Patch2 in the
same patch queue, with both of those patches applied in order. What happens
in the Graph Log is that clicking on Patch1 shows no diff at all, and
clicking on Patch2 shows the combination of Patch1 and Patch2 all as one
diff. I've tested this on several projects created from scratch. It's the
same effect if the patches are unapplied, only the most recent patch in the
queue displays any diff at all when selected, and the diff it displays isn't
the diff for just that patch, but the diff of the entire patch queue.
This is what I see in the Patch Queue view as well. Which means there is no
way to see the diff for a single patch, applied or unapplied. I hope you
won't mind me continuing to call it the "Patch Queue view" rather than the
"Patch Queue dock widget". Since it is accessed from the View menu with the
Patch Queue menuitem I think it will be easier for anyone else who might
read this to understand what we are talking about :)
Regarding using patches without the Patch Queue view. In the Graph Log I see
that it is possible to apply patches, (either by double clicking them or
using the right click context menu), but I don't see any way to remove them.
The right click context menu for an applied patch contains no entries for
removing or popping an applied patch. I also don't see any way to apply all
patches or switch patch queues other than via the Patch Queue view. Not that
this is an issue for me since it seems perfectly logical to me to use the
Patch Queue view for this.
----
Sorry if the email address hacks you off, but it's tiresome having to create
a throwaway email account just to access support for a product via a mailing
list because they don't have a forum, and finding meaningful names for
throwaway accounts is even harder, since obviously all the real names are
taken and there are only so many email accounts real.name1234 that you can
keep track of. I did sign my mail with my 'Internet real' name Neutrino, and
I've tried to change the account details to match.
If you had a forum you'd also be able to sticky what information you'd like
to receive in all queries, version number and so on. People would also be
able to more easily post images which is pretty useful.
----
P.S
I've installed the latest nightly build and unfortunately the situation is
not better. Individual patches still do not show a diff properly, only the
latest applied or unapplied patch shows the diff of the entire stack.
There have also been a couple of other changes which on first impression I
don't like much either. In the version of 2.0.5 that I was testing
previously there was a patch list window which was the leftmost pane of the
Patch Queue view, (this was the window that displayed the list of patches in
the currently selected patch queue).
In the new build what was the old Patch Queue view has been renamed the MQ
Patch view, and the patch list (which was an integral part of the old Patch
Queue view) is now a standalone window called Patch Queue that you have to
access separately from the View menu. So now if you click the MQ Patch view
toolbar button the MQ Patch view doesn't even show you the patches in the
current patch queue until you also display this separate Patch Queue window.
Bizarrely this new Patch Queue window has the ability to dock with any part
of the UI apart from the MQ Patch view, the one place it would be arguably
most useful and certainly most familiar.
I don't know what the motivation was for splitting the Patch Queue UI
component into multiple separate parts but I don't think it's improved the
UI (which I though was pretty good as it was). It certainly takes more mouse
clicks now to load the views you need to manipulate patches than it did
before. There is now less modality in the patch management UI. You used to
be able to just click the Patch Queue view toolbar button and see everything
you needed to manipulate patches, but not anymore. It's possible this could
be improved somewhat by making it so that if the Patch Queue window is
tabbed to any other windows then when the MQ Patch view is activated the
Patch Queue window is made the active tab so that way you can still access a
complete patch UI with one mouse click, but even that's rather speculative
since it begs the obvious question: well what happens when you then switch
to a different view?
The new Patch Queue window also seems to have a few bugs.
Bug 1. The "Unapply one patch", "Unapply all patches" buttons are enabled
even when there are no patches applied to the repository.
Bug 2. More seriously. Activate a new patch queue. Apply all patches.
Unapply all patches. Now the Patch Queue window lists none of the patches in
the queue at all, and neither does the Graph Log. At this point you have to
reload the patch queue to do anything.
The Commit button now has multiplexed functionality whereby through the use
of a sub-dropdown of the Commit button itself you can swap its function
between Commit, QNew and QRefresh. Once you've QNew'd a new patch and made a
modification you then have to manually multiplex the Commit button into its
third form to Refresh the patch. Given that you have to switch the button
between these multiple forms manually I don't understand what the advantage
of this is. It just seems like more mouse clicks to get the same amount of
work done.
That's as much testing of the nightly build as I have time for now.
Apologies for not loving it yet, but I hope the feedback is of some use at
any rate.
Neutrino.
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Tortoisehg-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/tortoisehg-discuss
