Slickedit V11 simple usage Evaluation

Slickedit V11 is a stable and long-term version of slickedit V11, which is ready for use immediately. After the Server Load balancer instance is installed, it is found that the Server Load balancer V11 is better than the old V10 and V9. I just lost my custom menu settings (but I still find many problems to solve ). V10 and V9 usually reset all custom menus and toolbar. Some custom buttons are reset. V11 is a lot better.

However, after importing the V10 configuration directly, there are still many problems. I encountered a very strange interface refresh problem. When I read the code, I clicked a tag, and the symbol window did not respond. The refreshed content is only visible after I click the symbol window and let the focus pass. Later, we found that this was not the only one, but also other defs and other windows. I am very disappointed that I finally found that I still need to delete the sta file in the setting directory and force slickedit V11 to compile all the macros. This behavior caused the loss of all my custom menus, and I had to configure another tsf-t.

There are also some macros, which only have the ex code without the ecode. V11 will be loaded after the configuration of V10 is imported, and a macro version is incorrect when it is started. Slickc stack errors keep popping up when you try to close it. Finally, we need to use the task manager. Very uncomfortable. The most terrible thing is that when the V10 and V10 coexist, it is because of the previous settings, so it began to have a strange problem: some macros even include some built-in Macros in the V10 directory !! It's a mess in use. It's true that ft is dead. At last, I packed and backed up my V10 configuration, and then the entire V10 was removed. Then install V11 on the original seat of V10.

The configuration migration of slickedit's new and old versions is really troublesome. But this time, as long as you know not to coexist, do not use the old sta file, or reconfigure the custom menu, the migration is still intolerable. Because slickedit upgrade from V10 to V11 costs nearly $200. The new purchase is $299. So for those users who want to pay for it, if 1.6 k RMB is dumped, will they still care about the migration configuration problem? However, for those of us who use the XX version ~~ Migration configuration is troublesome.

The annoying thing has passed and finally slickedit V11 can be used. From the perspective of the interface, there is basically no major change, but the tab and combo box controls have become Windows Standard theme that can be embedded with Win XP. But with this change, the interface looks much more comfortable. The ComboBox Embedded in the toolbar has been well adjusted this time. The status of the small button seems to be neat, so you can have a good mood after reading it.

At present, I have used a simple day. I found that the functional changes mainly involve the search function, the bracket highlighting function, the code auto-completion function, and some improvements to the operation interface of the original dialog box.

The search function has been greatly improved this time. Search can now highlight all matching results in the full text as in emeditor. This looks very convenient at a glance. Unfortunately, I did not find the clear highlighted button ~~ It should have been provided. However, the macro command for clearing the highlighted result from the user manual is clear-highlights. I created a button for it on the toolbar. In addition, search supports searching in certain parts. For example, you can specify that it can only be searched in string, function, or comment. These ranges can be set using the color option. In addition, you can create multiple search result lists (not as if there was only one search list ). Search results now uses tabs to manage multiple search results. You only need to specify the output goal during the search. Finally, the find/find in files/replace in files functions are separated by independent tabs, each of which uses independent tabs for settings. It is much easier to use than the original integrated interface. The find & replace dialog box still supports the dock. I tried to dock it under the screen and try to facilitate searching. It is a pity that this is not easy to use, because although the form can dock, but the control in it is not optimized for the dock, option 1 expand beyond the height of the dock window will not be seen. It is of little practical value.

Then let's look at the bracket highlighting function. This feature was originally a feature available in all the current cat and dog editors. slickedit, which has been at the top of the 200-dollar high-end editor for 88 years, has only started to support V11. The original v8-v10 had to always use a buggy bbhlite macro to achieve simple brackets matching highlight function (it is precisely this macro engaged in my V11 reported wrong version of the error life and death can not go back not available ~~). Now we can see that brackets matching are highlighted. However, in actual use, it seems to be a little slow. The reaction speed of highlighting is far slower than that of uestudio or emedit. At least 10-20 milliseconds of latency. But What surprised me was that this slickedit provided not only the brackets highlighted, but also the macro commands such as # ifdef # else # endif were highlighted !!! That is to say, if the cursor stays above # ifdef, the corresponding # endif will also be highlighted. Wow Kaka is so cool. It is so comfortable to use this function in Linux code that is filled with such macro switches. It seems that slickedit will do its best this time !! No one can match the highlighted feature this time.

In terms of Automatic Code Completion, slickedit was already doing its best in this respect. But this time I made a great improvement, and I have made great strides. When uestudio was used, it had a very Sb Automatic completion function. It is all the words entered in your code. It will be remembered and will be prompted after you enter two letters. This function is really silly, but it is really useful for one or two times. V11 also supports this time, which is called word completion. This word completion has the lowest priority. It is placed at the end of the automatically completed list, and can be freely disabled or determined to list the number of words. The function similar to the automatic function name completed by sourceinsight is now available by SE. When V10. Another good improvement is to provide the syntax expansion function in the form of Automatic completion. For example, if you press a SW, a switch (...) appears in the automatic Completion list (...) {...}, the screen is displayed only when you select it. Unlike a space, it is simply a sb that makes it too late to close the door. This function is of practical value. However, the show light bulb function is now added, that is, a small light bulb prompt will appear in the row number column when Automatic completion. This is a little familiar with Eclipse, but this time se is also playing this, it feels a little effective. As long as this light bulb is displayed, the entire editing area will be shifted to the right due to the wide expansion. After the light bulb disappears, it will be moved to the left ...... It will be dizzy. I just switched it off. In addition, the auto-complete settings can be said to be meticulous to the extreme, even the list display does not show the icon and classification of things can be customized for users, this is quite good. For this automatic success, I conservatively scored 9.5 points (out of 10 points ). The remaining 0.5 are waiting to be added to the future V12 and v13 ......

For the original interface layout, V11 has indeed improved a lot. In the past, se had been lacking in the ease of use of the interface, and now it is really much better. First, V11 also locks many windows. For example, backup history can also be used by the dock to the edge (I like backup history very much, it is really an invincible regret. I have set the maximum number of backup versions to 200, which is enough to see my BT ~~ It is really Ctrl + S according to the reflection of the two letters, press one, so that the version of my backup increases quickly ~~). There is also the references window, you can switch the display of the preview area or not. I like the new layout that can close the preview area very much. In this way, the references window will be able to dock to the side, and the vertical display area will be much larger, while the preview will be able to fully utilize the symbol window, which saves the trouble of switching, it should have been designed like this!

There are too many advantages. I am too lazy to talk about other advantages. Now I am complaining about disadvantages. In the history of slickedit, it seems that the minor version number is 0, which is a relatively buggy thing, such as V9 and V10 ~~ In particular, v10.0 is really a fear of me and will crash. Later, I used v9.04 until the patch 10.01 was released. This time, v11.0 also has many bugs, but fortunately the stability is still very good and 10.03 is equivalent. Currently, two major bugs are found. A new RegEx evaluator tool appears to be used. This tool is really awesome. It is too convenient to write regular expressions. You can replace some professional regular expression tools. This means that every time I enter and exit the debug view of slickedit, vsapi is triggered. DLL error (not a fatal error, but an ugly dialog RegEx. ex ). If I disable the RegEx evaluator, it is okay when I enter the debugging view. If I exit, an error is returned. If you enter the debugging view when you open it, an error is returned. It can be determined that there is a bug in this stuff (it should be a problem with macro writing ). However, it can be comforted that functions other than displaying an error prompt do not have any impact or cause other problems. Besides, slickedit's debugging interface will not be used for Embedded debugging.

Another bug is that I have been tossing for a long time. It may be the problem with vsapi. dll: One of the basic APIs provided by slickedit: _ gettextcolor () is useless !! This interface is also listed in the V11 user manual. This function is also declared in builtin. e, but it cannot be used !! An undefined function error is reported when a call is made !! I searched a macro from the original V11 and found that this interface was not used in it. No wonder it was not found by developers. It is not clear whether the new version has removed this interface or whether it is a call bug. This error makes it impossible for me to use a macro in V10 to implement the High Brightness function similar to sourceinsight. It took me half an hour to read the code and rewrite the Macro. This problem was solved by bypassing this interface.

Finally, let's talk about the comment wrap feature that I was looking forward. After the test, we found that Chinese characters are not supported! Alas, the English name of slickedit, which has excellent support for Chinese characters, was finally ruined by the newly added comment wrap. Unsupported Chinese Style: 1. the wrap function is invalid when you enter Chinese characters. If the specified width is used, no line is left. 2, as long as the wrap function takes effect, all the Chinese characters in the comments that have been broken will disappear into a bunch of messy characters. I think it may be because I have hidden the higher bits in the double byte, or why. If you still write comments in Chinese, do not open this function. If you write comments in English, I tried it.