I'm finding the following issues with the TAdvRichEditor - they can be replicated by using the attached project.
I'm using C++ Builder 11.1 and the latest TMS controls...
The editor works fine for a while but, after creating a reasonable amount of text, the following happens
CTRL+B with nothing selected no longer works. The toolbar's Bold icon isn't selected and I have to click it to go bold. Same for Italic, etc. This is very frustrating as the keyboard shortcut should toggle bold, regardless of anything being selected
After clicking Bold on the toolbar, the font and fontsize changes - it shouldn't
Sometimes resizing the control horizontally makes words on the edges disappear - see the screenshots. Resizing again can make them reappear.
As I'm using the control in a note taking app, I often copy and paste things into it from various sources, including web pages. But once the text contains plenty of text, often with different fonts, then these problems become apparent.
It's incredibly frustrating because the control is just what I need. But these issues make it so hard to use in practice.
With respect to actions on the toolbar, it is by design that these apply on the selected text. When there is nothing selected, clicking on bold will have no effect. It has effect on what is selected.
With respect to actions on the toolbar, it is by design that these apply on the selected text. When there is nothing selected, clicking on bold will have no effect. It has effect on what is selected.
I understand. I'm not sure why you did it that way - Word, Wordpad and most rich text editors let you do something like CTRL+B to switch to Bold and then CTRL+B to go back to normal. It interrupts the flow of typing to have to select things...
Since doing a full rebuild of the app, I haven't seen the disappearing words problem, so it looks like a bad build... I'll keep an eye on it...
Additionally, it is only the keyboard shortcuts, like CTRL+B that won't work unless something is selected. If I click the toolbar I can toggle the selection. Surely, both the toolbar button and the shortcut should work the same way...
