Some small issues and FR's

[sl23]

I wasn't sure where to post this so I put it here.

I was just trying out the Snippets panel again. Here are some observations. I think it would be useful to implement some of them, though obviously the more the better!

1. Last used as default: When opening the Snippets panel, it defaults to the Arrows snippets, I suggest it be better suited to defaulting to last used. For example, I only use the Rainmeter Snippets, but it is awkward and often more time consuming to open Snippets panel, select the Rainmeter snippets file from the drop-down list and finally the actual snippet. Perhaps an option in the settings to allow current or suggested behaviour?

• Add CRLF on enter: When using the snippets panel, it traps keyboard focus. So using multiple snippets means constantly back and forward with the mouse/keyboard to shift focus between Snippets and Editor. Why? Because you double click to enter a snippet, then need to shift focus back to editor to press Enter key in order to create a new line. I suggest an option in settings to allow the Enter key to stay focused in the Editor, so you can Double click a Snippet, Press Enter key, then Double click another Snippet, etc, so as to avoid the constant shifting focus. OR... I think maybe better, allow Snippets to detect a new line in the Snippets file itself. Example: Plugin - ActionTimer=Plugin=ActionTimer\n so if the snippet itself contains \n then it also adds a new line to the Editor. This may alleviate the issue in certain circumstances.

• Allow tooltips in Snippets: This would allow users to set a tooltip for each Snippet. So when hovering a Snippet, a tooltip would be shown, if it has been set in the Snippets file. Example: Plugin - ActionTimer=Plugin=ActionTimer\n ; Place tooltip here So if the snippet contains a semi-colon, then a tooltip would be shown containing the text after it.

• UI Tabs need HotKeys: I have around 1400 text files that require converting to UTF16LE with BOM from UTF8. I am having to do this manually and found a small limitation in use of Tabs. There seems to be no way to select a Tab via a HotKey. Maybe I missed it? It would be good if there were a way to set a HotKey to move the Tab selection Left and Right.

I expect these are pretty intensive to implement, but I just thought they would be really helpful and useful.
Whatever you think anyway, no worries if you decide against them.
Thanks for all your work on CudaText!

[main Alexey]

>There seems to be no way to select a Tab via a HotKey.

if you install the plugin CudaExt, you will have such command in the Cmd Palette:
- Tabs: Activate next tab (global loop)
- Tabs: Activate previous tab (global loop)
plus several commands to activate (name has word 'Switch') next/prev tab in next/prev tab-groups.
It's ok for you?

[main Alexey]

>When opening the Snippets panel, it defaults to the Arrows snippets, I suggest it be better suited to defaulting to last used

as I see, last chosen snippet group is restored.
try this:
- open Cud (e.g. side panel is hidden)
- press icon Snippet_Panel on sidebar -> panel shows, some group is active
- with mouse click, choose different group, eg 'Math symbols'
- close app, run app ---> Snippet_panel auto shows and shows group 'Math symbols'

[sl23]

Thanks for the reply.

if you install the plugin CudaExt, you will have such command in the Cmd Palette:
- Tabs: Activate next tab (global loop)
- Tabs: Activate previous tab (global loop)
plus several commands to activate (name has word 'Switch') next/prev tab in next/prev tab-groups.
It's ok for you?

I often find plugins awkward to understand. For example, this one asks if I want to install with two options:
1. Simply click: OK,
2. Or, click OK: without HotKeys.
Isn't the plugin designed to add HotKey shortcuts? If not, what is the plugin designed to do?
If it is designed to add HotKey shortcuts, why would you want to install it without HotKeys? Does it simply add new commands to CT accessible via Buttons? How do I add HotKeys? I installed with HotKeys, but cannot find how to change them. It would be helpful if the Config Toolbar plugin could allow users to specify Hotkeys there for any command. Then when a new plugin, like the Cuda-Ext one, is added, users can set a HotKey to its additional commands.
I found that commands are in fact within the Config Buttons dialog via Commands.

as I see, last chosen snippet group is restored.
try this:
- open Cud (e.g. side panel is hidden)
- press icon Snippet_Panel on sidebar -> panel shows, some group is active
- with mouse click, choose different group, eg 'Math symbols'
- close app, run app ---> Snippet_panel auto shows and shows group 'Math symbols'

This is correct. But close the Snippets panel and reopen it, you'll find it always resets to Arrows.
I also have some small issues with the Code and Snippets toolbar buttons. I asked before how to set up the Code Tree button to open and close the sidebar. This works ok. I have however added a snippets toolbar button. If I open the sidebar via Snippets button, I cannot then go back to the Code button. The Code button just opens and closes the sidebar showing the Snippets. I have to restart CT with the panel closed and then open the Code button to show the Code Tree.

I think this sidebar should have a small toolbar showing all relevant panels available so you can switch between them. This way a single toolbar button would be needed just for open and close. The Sidebar panel should then remember it's state on open/close and restart. I think this is typical behaviour with sidebars. But I know it is a lot of work and would be happier to have a button to open and close the Code Tree as I have now, but then have a separate button that opens/closes the Snippets. But when I click on either button, it shows the relevant panel, instead of just open/close, it also selects the correct panel. Whichever is easier.

Thansk very much

[main Alexey]

1) about CudaExt plugin and install dialog with OK / 'OK without hotkeys'.

CudaExt just adds commands to the Cmd Palette menu (menu item 'View / Command Palette').

a- if you press 'OK without hotkeys', commands will be added w/o new hotkeys (see them in the CudaExt's install.inf file).
b- if you press 'OK', commands will be added with new hotkeys (per install.inf).

you can change any hotkeys of course.
via Cmd_Palette, focus a command there (without Enter) and press F9.


2) about Snippet_Panel.
I cannot see how current 'group' is changed when I do this:
- call SnippetPanel
- choose some group
- click sidebar's SnippetPanel button 2 times (hide -> show)
--> old group is restored.

give your steps how to 'loose' old selected group in SnipPanel.

[main Alexey]

3)
>I also have some small issues with the Code and Snippets toolbar buttons. I asked before how to set up the Code Tree button to open and close the sidebar. This works ok. I have however added a snippets toolbar button. If I open the sidebar via Snippets button, I cannot then go back to the Code button. The Code button just opens and closes the sidebar showing the Snippets. I have to restart CT with the panel closed and then open the Code button to show the Code Tree.

I cannot see what you do, this is description of your custom config in Cud's Config_Toolbar plugin.
start a new topic, and post there your configfile of Config_Toolbar (find it in the 'settings' folder).

give me steps what you do. i will try to repeat your steps with your configfile.

you can also make the video or screenshots and post it to the Github 'issue':
https://github.com/Alexey-T/CudaText/issues

[main Alexey]

4)
you asked to support \n in SnippetPanel.
i made new macro instead: ${eol} . it means the newline char (LF).
grab the changed plugin from git and test:
https://github.com/Alexey-T/CudaText/tr ... ppet_panel

[sl23]

Bit busy at present. Tried #4, didn't work for me. I only updated the __init__.py file though seeing as the other files are years old.

[main Alexey]

4) after you updated the __init__.py file, update also your snippets in the data/clips/FolderName/*.txt file. ie, add macro ${eol} to your snippets. then changed macros will insert newline-char.

[sl23]

Excellent work thanks very much!
I'll get back to you soon about the other issue.