A smaller update this time, but an update just the same: this one relating to Plug-ins.
View SharpMT FAQ: FAQ
Download: .NET Framework, version 2.0 (required to run SharpMT 3.2.1)
With regards to the Plug-ins, there’s two different audiences for the changes…
Developers: I got a request for better control over the TextBox that is selected when a Plug-in is called. Part of that request was that when a Plug-in had its own GUI that focus be returned to the TextBox when the Plug-in was done: this works now, and I think of it as a bug fix. Another part of that request – the request for better control – couldn’t be done: the TextBox is disabled while a Plug-in is running, but there’s a workaround… the Interface for SharpMT Plug-ins now has a new property: ReplaceSelectedText. If this is true, any selected text in the active TextBox will be replaced; if false, new text will be inserted into the TextBox… so, if you’re writing SharpMT Plug-ins, you will need the new DLL with the updated Interface for your Plug-ins to run in SharpMT 3.2.1.
End users: Having said the above, as a user of SharpMT, you shouldn’t notice a big difference with the current application. The Plug-ins that I include will insert text, just like they always have… but what the new property will do is allow other Plug-ins some more freedom when it comes to text manipulation. For example, a Plug-in could now take in some selected text and replace it with a complete URL based off the selected text. In some cases, this can be set up by an end user using the custom tags, but if other data needs to be collected (via user or from another server) then a Plug-in has to be used.
For the most part, these were things that should have been behaving this way all along, but I never got around to it. Well that and I’m guessing you’ll see a new Plug-in announcement in the near future… nothing drives features and bug fixes like an active user!