Last week, i was thinkin about automatically wordWrap SciTE's Calltips. Currently, one can define calltip.abc.useescapes.
After that, newlines \n entered within an ApiFiles entry leads to a newline within that Calltips content.
Would'nt it be far more nicely to optionally let scite decide automatically where to put such a newline, based on the function declarations length ?
First - I started a Websearch - because sometimes such generally nice Ideas are already implemented in other SciTE Forks, givin hints on what has to be done. At first sight - SciTE.ru seemed to allow such a Feature, so i took a closer Look at their way on handling stuff which effectively adds 3 new Scintilla messages, one of them handling a fixed position calltip-wrap position. (not included, but here just for a reference ).
What i came up with now can be found here It does what its designed for, but as im hardly a C-Novice - dont expect perfectness and - it might be improved in the future. Its build around a wordWrap Function published by Sean Hubbart at c-programming.com. It wraps a Functions Documentation Entry based on the size of that functions Declaration. Adds; 3 SciTe Environment Vars:
calltip.*.use.manual.escapes has been added to preserve current behaviour.
calltip.*.max.wrappos allows us to set a Maximum Width that a Calltips function Documentations Text can extend to.
calltip.*.show.funcdocs can be set to Zero, effectively showing only the functions declaration and ommitin the Documentation.
License: BSD-3Clause
As always - feel free to use the code, but dont sue me if it bites your stuff :=)
Happy Autums-, Marcedo