XOJO PLUGIN HOW TO
XOJO PLUGIN UPDATE
XOJO PLUGIN WINDOWS

Once created, you can't change the border status. Please do that either in the IDE or in the Prepare event, so it is done before the control is created. We added the HasBorder property in the v22.4 plugin, so you can turn it on.

XOJO PLUGIN WINDOWS

You have four choices: kWrapNone for no wrapping, kWrapWord to wrap on word or style boundaries, kWrapWhiteSpace to wrap on white space or kWrapChar to wrap after any character.Ĭan the control have a border on Windows to look more like TextArea? If you like to wrap lines, you can change the WrapMode property. Now it works fine with ú í á æ þ ö é ð and ý.Ĭan we wrap long lines instead of scrolling?

XOJO PLUGIN UPDATE

We fixed the example and if needed, you can just copy the code from StartAutoComplete method to update your copy. The accented characters in UTF-8 are multiple bytes and the character functions didn't pick up the right completion. But that one was easily fixed by switching to string functions working on bytes. One client noticed, that auto complete in our example didn't work for accented characters. The focus can be lost, if the right click brings focus to another control or the window.Īutocomplete not working for unicode characters? If you have that problem, you can simply add a call to GrabFocus method to the ConstructContextualMenu and make sure the focus is set back to the control. But some customers had the problem, that focus was lost. You can use your own contextual menus with Scintilla.

XOJO PLUGIN HOW TO

How to avoid loosing focus with contextual menus? Let us show you a few tips, we gave to them: Tips and tricks for Scintilla Control Over the last weeks, we improved our example project and helped a lot of customers with using our ScintillaControlMBS (and DesktopScintillaControlMBS) control. Maybe you can add some information to help resolve the bug, an example project or steps to reproduce? (more) If you find a bug you also run into, please click the thumb-up button and add a comment with more details. Especially if the problem only occurred once and nobody knows why, there is nothing to do. The original reporter may have moved on or can't provide details on how to reproduce. Now it happens that some bugs get forgotten. If the bug can be fixed, it may get assigned to a developer, who may find a fix and then the fix goes into the next release after verification. Often it can be altered to gracefully report an error and not just assert. with a file name and line number in an assertion, someone can take a look on the code and guess how it may fail. Yes, if there is a way to locate it in source code, e.g. A bug report without a way to reproduce is difficult to fix.

He may have some questions about it and usually tries to get an example project made, if the reported didn't provide one. When you report a bug, it gets usually quickly reviewed by Robin or someone else of the Xojo team. The Xojo bug database has a bot, which performs various automated tasks.

Xojo plugin