Developer forums (C::B DEVELOPMENT STRICTLY!) > Plugins development

Editor Tweaks plugin

<< < (4/7) > >>

oBFusCATed:
If it is in the main menu one can setup a key shortcut for it :)

carra:
You are right... I learned about that AFTER my last post.

BTW: with the shortcut, my previous idea would work even better: you just press Ctrl+??, enter a character (or 2 at most, usually) and hit enter: done. Quite quick and totally flexible. No need to save configuration options, no large submenus.

Kalith:
I didn't know about this plugin until quite recently when bug #18795 happened to me. It has been fixed now, but I still think that the plugin behaves strangely...

The default setting is to have "Editor caret buffer" (which is not a very explicit name, by the way) equal to 4, that is the plugin will try to always keep the caret 4 lines away from the borders of the view (at least that's what I think is the intended behavior).

The thing is, if you position the caret somewhere and scroll away so that it is no longer visible :
[*]after typing a first character, the caret will be visible and located at the topmost/bottommost visible line
[*]for each consequent character, the view will scroll one line at a time until the line on which the caret is positioned is the 4th visible line (or the n-4th one)[/list]
This is very confusing... But maybe this is intended behavior ?

Anyway, this is a quite an uncommon and undocumented feature, plus it is not clear how to disable it (Settings -> Editor -> EditorTweaks settings -> Editor caret buffer = None).

MortenMacFly:

--- Quote from: Kalith on November 25, 2012, 07:53:34 pm ---Anyway, this is a quite an uncommon and undocumented feature, plus it is not clear how to disable it (Settings -> Editor -> EditorTweaks settings -> Editor caret buffer = None).

--- End quote ---
Thats just because you used recent nightlies where it was on by default. If you have a fresh installation, its off by default and won't harm unless you turn it on. Sorry for the inconvenience.

Kalith:
No worries, I was more concerned about C::B being at its best for the 12.11 release :)

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version