Last update brings new search and search & replace dialogs for the text editor. But it shows that the dialogs are not very handy to use. Each editor opens it's own search dialogs and if you change the current editor, the dialogs of the other editor are still shown. That may lead to confusion about what search dialog is for what text editor. On the other hand, if you like to replace some text with another and whould like to do it in more than one program, you need to open the search & replace dialog in each of that progams and retype your replace text.

In short: it is not very comfortable.

In this update the dialogs became global, but they are still for a local text editor. If you select another editor, the dialogs automatically switch to that editor. Now you are able to quickly replace text in more than one text editor without retyping the replace text.

As always: feel free to download, install and test the new update and leave your comments! - Thank you!

Hello, I have tried the latest version and find the comments text size in Chinese or Japanese is still smaller than in English. Always it's hardly to read comments, anyway make it fine?

Hi,

I don't have much ideas about Japanese and Chinese characters. IMHO it looks like the characters are overlapping each other and therefor are hard to read. What if someone try to insert spaces between any character? Will it become okay to read than?

The current text editor component "FastColoredTextBox" is marked to support Japanese and Chinese character sets, but it seams that it is not very good. I've checked other free editor components, but none of them are able to show the correct AS syntax.

What do you think?

Glad to hear you, I tried using vscode to edit project and it looks good. Plz check the SS (). But vscode can't instead of kide, kide is still the first choice
One more thing, I find no options to edit comments text size individually. If it does I think things would be better

I chacked the code of FastColoredTextBox when it comes to string drawing. FCTB uses a fixed character width to display the strings and tries to press each character into that fixed space. To do that, FCTB draws each character separately at it's predefined place. When it comes to characters who's width is bigger, FCTB zooms that character to even fit into that raster.

Other editors uses a dynamic with for characters that are bigger than the predefined with. "All I need to do" is to change FCTB to act the same. So if a character is bigger than the normal font width, the size for that character must be expanded. That will be a very huge change in the editor. Think about mouse click to set the cursor or selecting text, ... In any such a code location, the fixed character width mus be replaced by a dynamic character width. To find a specific character location in a line of proportional characters, you have to calculate the width of each character befor that character.

Another posibility to fix the problem is to use two character widths instead of one for a wider character. That will prevent to calculate each and any character width in a line. But for that we'll need to identify a character that is a Japanese or Chinese character (maybe by the integer value of the character).

I get it, I see many programmers who have entering Chinese strings demand will add codes to determine it. Hope your new version

Please see >this< for a test update. Use it with care!