500 downloads in 30 days

ZeroBrane Studio has been downloaded 500 times during the last 30 days after the previous release on September 3rd. While this may not sound like much, it's still more than the number of downloads for the preceding three months. The number of downloads per day was about 10 at the beginning of last month and is more than 20 for the last few days. This does not include repository clones and snapshot/tag downloads.

I take that as a sign that users like the product.

You should get a copy of my slick ZeroBrane Studio IDE.


Hi Paul I'm not sure if this is the place to raise this, but I thought it was a ZB issue rather than a wx one. I'm running on Win 7, and I can run all of the wx examples in the Lua download by clicking on them. But when I open them in ZB Studio and run with f6, some run, some don't.

For example, veryminimal.wx.wlua and grid.wx.wlua run, but calculator.wx.wlua does not. (I should add that it runs OK from Scite). I get the message:

Program starting as '"C:\mike\ZeroBraneStudio\bin\lua.exe" -e "xpcall(function() io.stdout:setvbuf('no'); dofile [[C:\Program Files\Lua\5.1\examples\wxlua\calculator.wx.wlua]] end,function(err) print(debug.traceback(err)) end)"'. Program 'lua.exe' started in 'C:\mike\ZeroBraneStudio\myprograms' (pid: 4872). Any ideas? Thanks, Mike

@Mike, this is indeed the case; thank you for reporting this. I did test with some of the examples, but not with all. There are three that don't show their windows: calculator.wx.lua, dialog.wx.lua, and mdi.wx.lua.

All lua application are started hidden by ZBS (to avoid showing an empty console window) and then wxwidgets-based application windows are shown (using windows API calls based on the type of their window). It seems like those windows have different type as they are created as wxDialog and wxMDIChildFrame instead of wxFrame. I'll see if those can also be included to show them correctly.

If you need a short-term fix, you can open interpreters/luadeb.lua and change "return CommandLineRun(cmd,self:fworkdir(wfilename),true,false,nil,nil," to "return CommandLineRun(cmd,self:fworkdir(wfilename),true,true,nil,nil,".

@Mike, this has been fixed in the Github repository and will be included in the next version.

Hi Paul Thanks for a great response! Mike

Leave a comment

what will you say?