Oxidizer 0.1
Well, after a day of server errors from SourceForge I've finally managed to get Oxidizer 0.1 released.
The changes for this version...
Multithreaded renders for all still and animations.
Palette number is remembered if a user switches between colour map and palette.
Attempt to use a 'batches' value of less than one results in a warning sheet.
Oxidizer how has a version number.
Fixes for the following bugs
1526625 Variations tab freeze on coefficient edit
1526613 Batches variable >= 1
1526599 color maps not saved
Colour map bitmap displayed when loading a flam3 xml file using a colour map.
Potential plans for the next version are...
Bug fixes.
Update flam3 code if necessary.
Add a Toobar optionally a floating one.
Do some of the feature requests at SourceForge.
4 Comments:
Noob warning..
Embarrassed to expose my ignorence here, ahem, but I haven't been able to compile the CVS source in XCode, or even load the project. What am I not doing right: I checked out the latest CVS release, started up XCode 2, cmd-O to open a new project, select oxidizer.xcodeproj, and then I get nothing? Or is it the project.pbxproj I should load? (still get nothing). Sorry for the noob questions...would like to understand how to follow the CVS developments!
Don't be embrassed we all have to start somewhere, beside I can't see that you did anything wrong.
The first queston that comes to mind is what version of XCode are you using, I'm on XCode 2.4
The about window gives these version numbers.
Component versions
Xcode IDE: 759.0
Xcode Core: 757.0
ToolSupport: 733.0
XCode versions tend not to be backwards compatiible and I've never actually tried loading a project into an older version to see sort of error to get.
oxidizer.xcodeproj is the correct file to open, so open that in XCode.
Now you say you got nothing, what do you mean exactly, no project window,
an empty project window. Don't forget to check the window menu, I once
spent a few moments in a bit of a panic when I could not see the project
window. It turned out to be at the bottom of the screen, only the title
bar was visible :0)
I've just tried creating a fresh checkout and it all seemed to work
so I don't think there's anything wrong with the CVS repository
unless there's a absolute file path in there that should not be.
Dave
Ok, upgraded to 2.4 (mine was at 2.0 - never used it before!) and now everything looks fine :)
A bit scary though, that a slightly older (well, a year, I guess...) version couldn't even load the file, or at lest inform me that it was an incompatible version.
Xcode - only for those stout of heart developers who know what they're doing I suppose...!
Yes, its a bit poor really. I can't understand why they could not make the
newer versions backwardly compatible for such a simple project. Not
having an Error Message box is just plain lazy.
I've added a note in the README about needing XCode 2.4.
It's good to know that the CVS repository does compile on someone elses Mac though :-).
Hope you enjoy all the changes.
Dave
Post a Comment
Links to this post:
Create a Link
<< Home