wb 073 beta 4

A new beta for winbuilder version o73 has been released. This newer beta contains a lot of important bugfixes that were somehow added during the works on previous beta editions.

Some of the most annoying bugs cause wb to completely wipe out the selected script whenever using the UI of the script - when you click on a button or wrote something on the text box for example.

Some other good features were also added along the way - my favourite is the option to launch a new window to edit the source code of the currently selected script. This is something I've been wanting to add for some time up to now but it's always been delayed until a good support for command line parameters was complete.

You can pass along a script as command line to wb using this syntax: <strong>WinBuilder.exe /open=myFile.script</strong> and this should open the mentioned script as expected,

If you use something like <strong>WinBuilder.exe /edit=myFile.script</strong> it will open the same wb window but will use the source editor tab as default instead of showing the script UI .

One last option is to run these scripts in unattended mode, this can be done using <strong>WinBuilder.exe /run=myFile.script</strong>

I'm quite happy about this next version - most features that were proposed nearly a year ago are pratically complete and after this beta we should be very close to release stable version 074 - it's been almost 6 months since the last stable was published so this should be a welcome update.

I've been noticing that reports on the discussion topic have been quite reduced lately - hopefully people are getting happy enough with the quality level of these latest wb versions (072/073) and therefore with little need to try out latest betas to see any annoying bugs fixed.

There also some features that weren't yet implemented - such as drag-n-drop support for adding attached files along with encoding of full subdirectories but over these last few months with the use of api.script this seems somewhat less trivial then before because it is possible to use "unpack"to extract the contents of self-extractable archives.

Next step is completing some of the tasks discussed on the bug tracker and after some "intensive" testing let's see if it's ready for a public release.

:)

-- Nuno Brito