lets improve PROP_CORNER_TEXT? about cudatext HOT 32 CLOSED

if we add multi-line feature, we need

• separare BG-color and font-color for all lines
• separate Tags (int) for lines
• separate removing of lines from n lines

it is hard to add. I want it simple

from cudatext.

Added.

• add: PROP_CORNER_TEXT supports multi-line text
• add: Editor.get_prop/set_prop: PROP_CORNER_FONT_NAME, PROP_CORNER_FONT_SIZE

from cudatext.

fixed now.

from cudatext.

Looking good:

from cudatext.

or hard-coded padding 2-3 px

from cudatext.

do you know plugins that uses this API?

none. it is very new.

that it doesn't support multiline mode.

yes it does not. LSP diagnostic is bad here - line is long, so last editor line will be overplaced. API is for SHORT lines.

from cudatext.

last editor line will be overplaced

its not a problem, diagnostic will be shown only if caret is on line with error. use case: user reads error text (no need to use mouse at all) and fixes error. and corner text is gone.

from cudatext.

then it is thje same as using embedded dialog at the bottom?

from cudatext.

dialog is for list, list can containt warnings, hints.. dialog can be hidden, Console can be opened (to read prints). so line is very convenient. don't you think? what use cases do you have in mind for this API?

from cudatext.

• show unicode-name of char there
• show 'Vim mode is active' mark

from cudatext.

i see code for displaying "R" for macro recording. is it working? i don't see "R" after using Record macro command.

what if lsp will have this feature disabled by default? one line. will it interfere with other plugins?

from cudatext.

I see 'R' after I call 'start/stop macro record' from cmd-palette.

from cudatext.

what if lsp will have this feature disabled by default? one line. will it interfere with other plugins?

it will not.

from cudatext.

I see 'R' after I call 'start/stop macro record' from cmd-palette.

try with "keep_sel_font_color" : true,

from cudatext.

what if lsp will have this feature disabled by default? one line. will it interfere with other plugins?

it will not.

but every ed.set_prop(PROP_CORNER_TEXT, '123') will overwrite text that was already added there by another plugin.
do you think plugin devs should get existing corner text and add own text to it and the remove what was added in the end?
or API is new and will be changed?

from cudatext.

try with "keep_sel_font_color" : true

fixed.

from cudatext.

do you think plugin devs should get existing corner text and add own text to it and the remove what was added in the end?

yes, I thought that plugins can add the text, or they can restore old text when removing own text.

from cudatext.

reopened if we need to discuss it.

from cudatext.

Simpler multiline painting:
If newlines have been found just paint all lines with the same color.

and no need for tags, etc.
it's ok for plugins to overwrite each others corner text, i think. it's just temporary info. (like statusbar)

from cudatext.

another thing: make non-monospaced font available for corner text.
(this can be enough to read long lsp diagnostic message)

from cudatext.

• add: Editor.get_prop/set_prop: PROP_CORNER2_FONT_NAME
• add: Editor.get_prop/set_prop: PROP_CORNER2_FONT_SIZE

from cudatext.

@veksha if you forgot about it:

• add: Editor.decor: DECOR_GET_ALL now can return all items for given line, if "line">=0

from cudatext.

thanks for new changes!

small issue: if some lines have unicode emoji and some doesn't we will get gaps between them:

from cudatext.

paste the Console command here.

from cudatext.

ed.set_prop(PROP_CORNER_FONT_SIZE, 15); ed.set_prop(PROP_CORNER_FONT_NAME, 'default') ; ed.set_prop(PROP_CORNER_TEXT, '🙂text\n'*3 + 'text2\n'*3 + 'text3')

from cudatext.

i think the border is not working after you added multiline support.

from cudatext.

fixed it too, later. currently ok?

from cudatext.

pulled last changes. yes, now ok.

from cudatext.

good...

from cudatext.

напрашиваются еще настраиваемые интервалы внутри/вне блока
PROP_CORNER_PADDING
PROP_CORNER_MARGIN
PROP_CORNER2_PADDING
PROP_CORNER2_MARGIN

from cudatext.

not needed, IMHO.

from cudatext.

any padding >0 is bad for code: now I use TextOut which fills the BG. with padding: I will need to do additional FillRect..

from cudatext.