Here’s a new version of my Electric Editing plugin. Did you know the first version came out in April 2005? Unbelievable how time flies! This version is built against DXCore 11.1.7. Here’s the download: CR_ElectricEditing-126.96.36.199.zip
Of course, as ever, if you don’t know what Electric Editing is, please check out this page, the various linked blog posts and the comments for the background info! Have fun!
Version 188.8.131.52 of Electric Editing is now available here: CR_ElectricEditing-184.108.40.206.zip
This build is compiled against DXCore 10.2.5. Unfortunately I noticed, a bit late, that 10.2 changed a few things that broke assembly references with the older build. My apologies for any inconveniences! Oh, and of course if you don?t have a clue what Electric Editing is, check out this overview with the various posts linked from there!
Version 220.127.116.11 of Electric Editing is now available here: CR_ElectricEditing-18.104.22.168.zip
This build is compiled against DXCore 10.1.7, and tested in Visual Studio 2008 as well as 2010. Enjoy! Oh, and of course if you don’t have a clue what Electric Editing is, check out this overview with the various posts linked from there!
Yesterday, Developer Express released new versions of their fantastic tools CodeRush and Refactor! Pro (I already blogged about the latter today). I have made new versions of my two CodeRush plugins available, both compiled against the new CodeRush version 1.1.28. An important change was made to the OpenToolWindow plugin (find the original announcement for that one here), to make use of a property in the CodeRush core that’s now public. So if you want to use OpenToolWindow with CodeRush >= 1.1.28, be sure to download the new version 1.0.1 of the plugin! (On the other hand, don’t use this new version if you are on an older version of CodeRush!) Electric Editing doesn’t have any important changes in itself, but it has been changed in a few places where methods in the CodeRush core had been made obsolete. Get the download for the new version 22.214.171.124 from the plugin’s own page.
A new version is ready, for the download please see the plugin’s own page. These are the more important news, apart from smaller fixes:
The whitespace hint lines are now drawn with a delay, which greatly improves the performance overhead when navigating around with the caret quickly. The delay can be configured in the options.
New Emacs style scrolling is available. This means that scrolling starts not only when your caret is actually in the top or bottom lines of the text editor, but a few lines before that. This makes it much easier to follow the scrolling text with the eye. By default, scrolling happens in chunks instead of single lines, which also speeds up redrawing quite a bit, especially when also using Structural Highlighting. The line offset where scrolling starts as well as the size of the scroll “chunk” is configurable in the options. It’s also possible to scroll by single lines by setting the scroll percentage to 1, but still keeping the offset scrolling at the same time.
The options have been split up to use several pages instead of only one. That concept wasn’t very extensible 😃 For restructuring reasons, you’ll have to reconfigure any settings you might have made before, sorry about that.
Two bugs have been fixed in this one:
When an electric delete operation was triggered while the caret was in virtual space, the caret would jump to the start of the virtual space, often the start of the line. This could happen to you, for example, when you had a new line inserted somewhere (maybe because you had used the electric semicolon in the previous line) that you didn’t want. You’d hit delete to get the next statement in the next line to move to the caret position, but the caret (together with that next line statement) would instead move to the start of the line.
When the caret was within the “block” of a for statement, meaning the code surrounded by curly braces following the for statement, the electric semicolon would not trigger. This happened because the plugin couldn’t distinguish between the caret being between the parentheses following the for statement (the part with the variable initialisation, evaluation, modification, where electric semicolon obviously doesn’t make much sense) and the caret being in the code block behind that part.
I’m not going to make the same mistake again as last time and try to provide an updated version in the old location… so, although there are only a few fixes, the current version has its own place on this page. Here’s the link to version 1.1.3: CR_ElectricEditing-1.1.3.zip
In this version, the checkbox that can switch on and off the whole plugin functionality should finally work correctly. A bug has also been fixed that occurred after an electric semicolon had been entered: the next electric backspace deleted far too much code. I have tested this version in my VS.NET 2005 beta 2 installation and it seems to work just fine. A bit unexpected, but nice 😃 So, have fun with it! There have been two other posts on the plugin to this point. The first one, here, has information on the installation procedure, while the second, here, describes some of the functions in more detail and has important information on the compatibility of the electric semicolon function with standard CodeRush settings. If you haven’t read them, it’s recommended you do so.
In a recent post, I announced a plugin that would bring a few features from nostalgic Emacs days to the modern world of Visual Studio 2003 and CodeRush. I received some feedback on that first version and now the Updated, Fixed and Obviously Much Better New Version™ is available. To start with, here’s the download link again, for the current version: CR_ElectricEditing-current.zip
If you need instructions to get the plugin installed, review my first post on the topic, please. Now, what can that fantastic plugin do? I’ll show you some screenshots and provide some explanations with them.