In the works for v1.2

[Guilect]

V1.2.0
added -- command system.run, allow you to programatically start other applications
e.g. system.run "notepad.exe"
added -- commands graphics.GetScreenWidth and GetScreenWidth, returns the resolution of the screen
corrected -- some typographical errors in the help manual.
added -- example race_mini
added -- option on make exe to optionally compress exe. If using XP AND using a custom icon, do not compress)
(this is a temporary work around until it is figured out why XP and custom icons and compression do not want to play together correctly. Non compressed and XP and custom icons work fine. Every combination works fine with Windows2000.)
fixed -- bug in Timers when using generated exe. It works fine in the IDE though.
added -- 'save as' to Brutus TileMap editor
added -- ability to change exe file info
changed -- menues. added properties, redo, uppercase, lowercase, whitespace to edit menu; moved Register to Help menu
In the IDE : added crtl+w to close current window
fixed ctrl+N to open new window
ctrl+Tab now current window has focus
added -- Pi as a constant
added -- functions ArcSin(x) and ArcCos(x); (where x is in Radians)
changed -- the behavior of the system.pause command. It no longer uses lots of CPU cycles.
added -- command CopyRegion(Source_ImageIndex, Dest_ImageIndex, Src_X, Scr_Y, Width, Height, Dest_X, Dest_Y)
added -- command system.GotFocus, returns wether or not the Brutus2D window has focus.

[OddChild]

Can you add a save as button for brutus map... and fix the save button.

[Guilect]

Funny thing.
I fixed the save issue months ago.
Never put the fixed exe into the distribution package, it
stayed in my working directory. Doh!

I will add a 'save as'.

[Guilect]

oddchild,
I know you are actively using the tilemap editor and this save bug is bugging you so here is v1.0.2 of the tilemap editor.

The next release will have the 'save as'



Get your copy here:
brutus.pewtersoftware.com/BrutusMap.exe

[OddChild]

just noticed the post. lol... Downloading the new version. Thanks a ton!

Are you going to skip 1.2 and go for 1.3 since you added quite a bit to your workload?

Also, are each release beta, and only whole numbers real releases?

[Guilect]

The next release (hopefully soon) will be v1.2.0.
The next release after that will be v1.3.0.

If a fix to features released in a version are required then the last digit will get bumped. For example, v1.2.0 gets released. There is some new feature in it. This new feature has been seen to have a bug in it. The fix is quick and easy, then I would do a quick release of a new package and call it v1.2.1. Then, after adding new functions and features the following release would be v1.3.0.