New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Commit-graph: Add option to always display first parent node in left-most column #5819
Comments
Could you please try this in the 3.00 rc2? The revision graph code is rewritten in version 3.00. |
Please try https://ci.appveyor.com/api/buildjobs/9uvt7cgl2v3e99om/artifacts/Setup%2FGitExtensions-Portable-3.00.00.4308.zip as well. This is the most up to date v3 artifact. |
It works as I would hope in this build! Specifically:
I have not tried the 4308 build, but I'd be happy declaring this request resolved with new default behavior. |
@RussKie: I was not able to run this build; it crashes opening a repo, trying to access the "Recent" folder from Program Files instead of user data. I don't know wheter there is just an xcopy install step I need to perform, or if it's just a bug in the build. |
Is there a stack trace to share?
…On Wed, Dec 5, 2018, 8:39 AM johndog ***@***.***> wrote:
Please try
https://ci.appveyor.com/api/buildjobs/9uvt7cgl2v3e99om/artifacts/Setup%2FGitExtensions-Portable-3.00.00.4308.zip
as well. This is the most up to date v3 artifact.
@RussKie <https://github.com/RussKie>: I was not able to run this build;
it crashes opening a repo, trying to access the "Recent" folder from
Program Files instead of user data. I don't know wheter there is just an
xcopy install step I need to perform, or if it's just a bug in the build.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#5819 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEMyXvUVaGL21YaFTDewkh8ioj_6byIQks5u1uuegaJpZM4Y2EHV>
.
|
Is there a stack trace to share?
I clicked “send report” when the dialog came up, does that go anywhere useful?
|
No |
Alright, managed to find a way to get the stack from the dialog...
|
I see the problem, it is indeed an xcopy deployment issue. I found that the config file has this setting in the zip file:
I set it to false, and now it behaves like a normal installation. I suppose if I'm trying out a drop like this I'm not expected to put folder in a secured location like Program Files. |
Yes, portable installation is not meant to be placed in restricted folders.
We need to fail more gracefully and make the exception clearer....
…On Wed, Dec 5, 2018, 11:04 AM johndog ***@***.***> wrote:
I see the problem, it is indeed an xcopy deployment issue.
I found that the config file has this setting in the zip file:
<!--Set this setting to True to store settings with the application, False to store settings in user's application data path.-->
<setting name="IsPortable" serializeAs="String">
<value>True</value>
</setting>
I set it to false, and now it behaves like a normal installation. I
suppose if I'm trying out a drop like this I'm not expected to put folder
in a secured location like Program Files.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#5819 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEMyXnQL0DZlHUFFvQhcgVrGOaPG-Gryks5u1w2QgaJpZM4Y2EHV>
.
|
Correct. Adding to list of portable work. Portable is a use like running on
a thumb drive. It stores settings with the program. Hence the name
portable.
…On Tue, Dec 4, 2018, 8:47 PM RussKie ***@***.***> wrote:
Yes, portable installation is not meant to be placed in restricted folders.
We need to fail more gracefully and make the exception clearer....
On Wed, Dec 5, 2018, 11:04 AM johndog ***@***.***> wrote:
> I see the problem, it is indeed an xcopy deployment issue.
>
> I found that the config file has this setting in the zip file:
>
> <!--Set this setting to True to store settings with the application,
False to store settings in user's application data path.-->
> <setting name="IsPortable" serializeAs="String">
> <value>True</value>
> </setting>
>
> I set it to false, and now it behaves like a normal installation. I
> suppose if I'm trying out a drop like this I'm not expected to put folder
> in a secured location like Program Files.
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <
#5819 (comment)
>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/AEMyXnQL0DZlHUFFvQhcgVrGOaPG-Gryks5u1w2QgaJpZM4Y2EHV
>
> .
>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#5819 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADdhsX3bnjvdEu-wR8DxZU1UoBjNtV8-ks5u1yWngaJpZM4Y2EHV>
.
|
Feature request.
Most of the time, the nodes of the graph that occupy the left-most column are part of the first-parent chain.
But occasionally I'll encounter a graph render like this:
In this case, the series of nodes highlighted pink (which do not have "Merged PR" in their description) are actually a second-parent sequence. The first parent of the highlighted commit is actually the green one further down.
It looks like the nodal position is either non-deterministic, or is using a strategy that optimizes for something else. It leaves horizontal positioning off the table as data. I think it would be a lot more valuable to use the horizontal position to communicate the specific relationship between merge nodes and their parents, specifically the ordering of the parents.
Clearly when there is a complex network of nodes on the screen, absolute position won't be useful, but between two parents, it would be useful to find that the leftmost parent is always the first parent.
The text was updated successfully, but these errors were encountered: