-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Add control with last interactive Git outputs and traces #10307
base: master
Are you sure you want to change the base?
Conversation
5cfe121
to
906017d
Compare
@PeterMinin, you could try https://ci.appveyor.com/project/gitextensions/gitextensions/builds/45223566/artifacts. If it was not such complicated, I would rather place the git output in the lower left corner in order to have it visible always. |
Nice! Changing hotkeys could be sensitive, but probably OK here... |
Thanks @mstv! This looks useful already. However my idea was to keep output from multiple commands, so that you could return to it after you've done something else. I think that would also mean writing the commands themselves, otherwise it would be hard to navigate. I took a look at the code to see if it's easy to implement that way. Although Also I guess it would be nice to show some placeholder before there is output to show. |
cc433c0
to
63a2b45
Compare
yes. Maybe ttal size too?
Probably
Related to this PR?
I do not want that there, maybe context menus on the tabs (in addition to AppSettings, as for other tabs) I also want:
No direct comments on the code. |
... but forgot to push the update button.
Could you elaborate? |
I liked the tab better than this panel
Compile error Still no major code comments, I will review (likely approve) when we agree on the display. |
63a2b45
to
1932647
Compare
I don't need it always - but if, switching tabs is a nuisance. It is becoming a killer feature for me. Toggle it using
My bad. Removed. |
I don't like it, sorry. It looks very untidy. I would have thought that we'll have a new tab of some kind.... Also, any new controls should be encapsulated as UserControls (or whatever) and not be coded directly in FormBrowse. We should be decoupling and encapsulating elements as much as possible. |
I should have marked it as draft / PoC more clearly... Extraction to a dedicated control is planned for after getting a consensus on the UX. The variant as Tab is available in the first commit. But believe me it is not very usable. |
Expandable/movable windows would be great, but it'd either require 3rd party controls (💰💰💰) or custom implementations (⌛⌛⌛). |
1932647
to
484ebd4
Compare
5c7d681
to
80400ba
Compare
80400ba
to
5563845
Compare
0dc5afc
to
8bfbfa4
Compare
and vertical tabs Refs: gitextensions#10307
8bfbfa4
to
41bb16d
Compare
and vertical tabs Refs: gitextensions#10307
41bb16d
to
4ab7f2d
Compare
and vertical tabs Refs: gitextensions#10307
4ab7f2d
to
d96ddbc
Compare
and vertical tabs Refs: gitextensions#10307
d96ddbc
to
3b79ca2
Compare
What is really missing yet? Consider please that the variant to display the output control as panel is not the default. Who does not like it can switch back to the Tab variant. |
Fixes #10206
Proposed changes
as well as with trace output
Ctrl+9
for toggling panel visibility and focusingScreenshots
Before
After
Test methodology
Test environment(s)
Merge strategy
I agree that the maintainer squash merge this PR (if the commit message is clear).
✒️ I contribute this code under The Developer Certificate of Origin.