Vertically split tabs, keeping the link-views feature

Question

Vertically split tabs, keeping the link-views feature

janwilmans opened this issue 11 years ago · 6 comments

I would be nice to view multiple tabs are the same time, so you have a filtered and an unfiltered view on screen at the same time.

Answer 1 · 2019-06-28T10:51:31.000Z

What a great idea! May I add to it:
Multiple side-by-side tabs/views/panes visible would be great when working with multiple threads.
Presently I filter each threads with [Tn] and filter each thread into separate tab/view. Also it would be great they all are lining up with time field, thus only left tab shows time etc. This would be very helpful when working with inter-thread communication/callbacks.
Also, maybe Thread# could be added as a field.

Answer 2 · 2019-06-28T14:27:17.000Z

Thanks for your suggestion! unfortunately the controls I'm using don't lend themselves for vertically splitting. I am working on a new version based on Copperspice and I'm going to include this feature there!

Answer 3 · 2019-06-28T20:35:40.000Z

Fantastic! Keep up the good work. DebugView++ is a very nice and useful tool. Actually I just recently realized the tab feature "hiding" under the File menu - shame on me. Tabs are so efficient for having multiple filtered views. So I will use tabs a lot now, thanks!

Answer 4 · 2019-06-28T21:48:36.000Z

Having different filter-sets and linked views is one of the most powerful features indeed! :) thanks for your feedback!

…

On Fri, 28 Jun 2019 at 22:35, ViggoK ***@***.***> wrote: Fantastic! Keep up the good work. DebugView++ is a very nice and useful tool. Actually I just recently realized the tab feature "hiding" under the File menu - shame on me. Tabs are so efficient for having multiple filtered views. So I will use tabs a lot now, thanks! — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#135?email_source=notifications&email_token=ABNITBEY3MZ7N3MYADPPPVTP4ZYZ3A5CNFSM4APWSRR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY3DJNI#issuecomment-506868917>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABNITBF5OR4PEMNZBDUGIDDP4ZYZ3ANCNFSM4APWSRRQ> .

-- Jan

Answer 5 · 2019-07-01T10:12:55.000Z

May I ask why "Clear Log" was changed from Ctrl-X to the more (imho) cumbersome Ctrl-Shift-X ,-) ?

Answer 6 · 2019-07-01T11:45:23.000Z

because it was shadowing (ctrl-x cut), which could have been solved differently, but also because CTRL-X, did not clear the view, but the buffer behind it. Some of us lost an important log-buffer one to many times with an accidental ctrl-X and we decided a more difficult shortcut would be in order... Greetings, Jan

…

On Mon, 1 Jul 2019 at 12:12, ViggoK ***@***.***> wrote: May I ask why "Clear Log" was changed from Ctrl-X to the more (imho) cumbersome Ctrl-Shift-X ,-) ? — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#135?email_source=notifications&email_token=ABNITBHPPQCCTYKQ2LTWD63P5HKCRA5CNFSM4APWSRR2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODY5VFHY#issuecomment-507204255>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABNITBBVKGOZ2GD2MYTLUHTP5HKCRANCNFSM4APWSRRQ> .

-- Jan