Who says there?s no such thing as a free lunch? While SAPIEN?s service releases for PrimalScript are usually used to correct bugs or make minor tweaks to functionality (mainly in response to user feedback), we sometimes feel the need to go all-out and incorporate fairly significant new functionality. PrimalScript 4.1, build 532, is just such a service release.
There is the usual array of fixes, to be sure: The undocked Output pane can now safely reside on a second monitor, for example, and a number of PrimalSense fixes have been made to work inside unnamed functions, work better with PHP, and so forth. We?ve also made some fixes to ?not quite bugs,? such as changing the PrimalScope debugger to display variable values which exceed 50 characters, just to help make the product easier to use. A full list of all the fixes is available at http://www.sapien.com/support.asp – just follow the link to the product?s Change Logs. Thanks to everyone who kindly brought these items to our attention over the past few weeks.
But there?s far more than just fixes in 532, which is why we?re making such a big deal of it. Windows PowerShell can now be launched right from the Tools menu, providing convenient access to the shell. We?re also giving you the option of capturing script output from Windows PowerShell into the Output pane?and we?re intercepting calls to Write-Debug and capturing those into a separate Debug pane, helping to keep your debug output separate from your script output (it?s a great debugging trick). And speaking of output capturing, we?ve responded to a number of users who miss the old ?Output Tab? from version 4.0, and we are now providing an option to use the tab instead of the new Output Pane (you?ll find this checkbox in Tools > Options > Text Editor > General > Redirect Output to View).
Also by popular request, the ?Find in Files? feature also gives you the option to display results in a tab, just like in version 4.0. So you can decide on a case-by-case basis where your results should go.
And the list goes on: You now have the option to highlight the current line, helping you keep track of your cursor more easily (another common user request). Document tabs now have an individual ?X? icon to close that tab (yet another user request). Document tabs also have a fold-down menu button to display all open documents, allowing you to quickly select one when you have a lot of tabs open (you guessed it, another user request).
Finally, back on the Windows PowerShell bandwagon, Enterprise edition picks up a new project template for Windows PowerShell cmdlet development, meaning starting a new snap-in and cmdlet is as simple as File > New > Project. This feature leverages Enterprise?s existing support for C# and VB.NET, making PrimalScript the only environment capable of creating both Windows PowerShell scripts and cmdlets!
So check it out! If you don?t already own PrimalScript, you can find a trial version at www.primalscript.com/downloadtrial.asp. You?ll have a full 45 days to see what you think. If you already own PrimalScript, you can go to the same Web page to download build 532: Just select the ?Repair/Update? version when installing the trial and your registered copy of PrimalScript will be updated ? there?s no need to re-register.
One thing we want to highlight in build 532 is the large number of new features and fixes which were politely brought to our attention by our users. We do listen; while we refrain from commenting on what we?re up to until we?re ready to release, most of what we do at SAPIEN revolves around the feedback our users provide and the suggestions they make for improvements. So while we can?t always accommodate every request, know that your requests are heard and given serious consideration. Browse back through the support forums on www.sapien.com and you?ll find nearly every item in build 532 mentioned as a request. We truly appreciate the time you?ve taken to make these helpful suggestions and to politely call various items to our attention?and we?re glad to be able to act upon so many of them with build 532.
And if you?ve made a request, or pointed out a problem, that isn?t addressed in 532, please don?t think we?ve ignored you. We haven?t; we?ve just worked what we could into build 532, and we can assure you that everyone else?s input is still under consideration for future builds? not to mention version 4.2, which is definitely getting underway.
Enjoy!
