Phil Haack
Phil Haack
| and the messages clutter up the lines and the graph. See, I'd rather solve **that** problem. Not sure how exactly, but I could imagine a layout that ensures that...
Sweet! Thanks for helping!
What I'd really like to do is more intelligently lay out the graph so the messages don't overlap too many elements. But I do like the idea of showing the...
Not even the commit hash? There should be some identifier. Otherwise it's just a bunch of black context-less circles. Can you photoshop (or Paint.NET) up a mockup of what you...
OH, interesting. I wonder if the text should be smaller without the mouse over. That way you can see enough of the commit message to make sense of it. I...
I was thinking you'd just redraw the entire graph if the setting is changed. It's kind of a core level setting. I'm not sure what the "trigger collection" is. ;)
Is there any reason not to use triggers? I just haven't dug that deeply into it to understand.
@mdonatas Yeas, that's the current behavior. Because we don't refresh our UI graph when commits go away. I'd like to have it show all commits, but that'd be a little...
We could embed git2.dll and extract it on first run.
Note that I also tested this on ASP.NET Core 3.0 and it still doesn't work.