[bug] Hydra tabs

[d.healey]

@Christoph-Hart I'm fine with them all being on init. I just don't want to have to re-add editor tabs each time I reopen HISE.

[Christoph Hart]

Does the information that you can double click on script files in the File Browser to open them in a tab make you stop requesting this :) ?

Also if you press F12 it will jump to the definition of the currently selected text token which is my preferred way of navigating (aside from the Find all occurences window).

[d.healey]

@Christoph-Hart said in [bug] Hydra tabs:

Does the information that you can double click on script files in the File Browser to open them in a tab make you stop requesting this :) ?

I rarely use the file browser, I almost always have either the project tree or the api browser visible. Also I just noticed that when I have an expansion loaded the file browser shows the expansion's files rather than the project's. Just give me 5 editors by default and I'll leave you alone :)

Also if you press F12 it will jump to the definition of the currently selected text token which is my preferred way of navigating (aside from the Find all occurences window).

This is useful!

[Christoph Hart]

Just give me 5 editors by default

NEVER!

I'm still trying to convince you that there is a better workflow (because you would have to select each tab, click on the drop down and select the file you want to edit each time you load HISE which is annoying).

Next idea: if the text cursor is in the string of an include statement, it will open the included file in a new tab when you press F12 (that's actually how VisualStudio and XCode work).

// onInit
include("SomeFile.js");
include("PathsWorkToo/SomeOtherFile.js");
//                       ^
// just click here and press F12

[d.healey]

@Christoph-Hart

Next idea: if the text cursor is in the string of an include statement, it will open the included file in a new tab when you press F12 (that's actually how VisualStudio and XCode work).

I like that idea but... I would have to keep one tab always set to on init and go back to that tab each time I wanted to open an include (I think this is a little more effort than selecting from a dropdown). I'd still have to manually add a tab and select from the drop down when I want to go to one of the built in callbacks.

What about a goto project file popup like in Sublime Text or Atom, and probably VS (I think it's CTRL+P in Sublime)?

Oh and a shortcut key to add a new editor tab.

[Christoph Hart]

and go back to that tab each time I wanted to open an include

@d-healey Use Ctrl+Backspace to navigate back. HISE => VIM

I'd still have to manually add a tab and select from the drop down when I want to go to one of the built in callbacks.

Yes that's a valid point, I just don't use them too much :)

What about a goto project file popup like in Sublime Text or Atom, and probably VS (I think it's CTRL+P in Sublime)?

the Find all occurences window does exactly that (if you use the f prefix).

[d.healey]

@Christoph-Hart

Use Ctrl+Backspace to navigate back. HISE => VIM

No worky on my superior OS :) Neither does CTRL+SHIFT+F either or a bunch of the other shortcuts.

I will give the new system a fair trial before passing judgment, but an add new script editor tab shortcut key would be mighty helpful.

the Find all occurences window does exactly that (if you use the f prefix).

How do I use the prefix, just add f in the search box?

[Christoph Hart]

How do I use the prefix, just add f in the search box?

Yes. If the search term has a f prefix, it will limit the displayed results to files only. This also works with symbols s, functions (fn ) and variables (v).

[d.healey]

@Christoph-Hart What am I doing wrong here?

The F12 thing for included files is great, except it doesn't work if the script is in the global scripts folder.

[Christoph Hart]

@d-healey you need a space between f and the filename

[d.healey]

@Christoph-Hart Ah ok that makes sense!

[d.healey]

Now I get the best of both for (int i = 0; i < tabs->getNumTabs() - 5; i++)