About a year ago I bought a Zaurus SL-C700. Tt's a truly wonderful machine; without doubt the most powerful PDA you can get your hands on (well, actually, the Zaurus line is, the SL-C700 model is a bit dated, though I have yet to find a machine in Sweden which can match this two year old model when it comes to performance). And there are a _lot_ of apps to it. With something like the pdaXrom it's extremely powerful, since all X applications are available. So you do not only get access to PDA applications, you also get access to the whole Linux "product catalog". And with a 640x480 screens, it works very well.
My problem is that I suspect that there's some kind of hardware malfunction with my unit. It often crash without warning, often many times a day. And applications will often lock up or make the whole system slow, util it all just crashes. Very, very sneaky. And since I've bought it from Japan, I can't really just send it back. It's really annoying, because it prevents me from using the PDA.
Hmm, perhaps I should get one of these instead?
Monday, February 28, 2005
Wednesday, October 27, 2004
Regression testing, the new black
It's taken me at least three days to convert Ember to Eris 1.3. In the meantime Ogre 0.15.0 was released. And glory! Ember compiles without modification against the newest Ogre. I'll try to stick to the point release as far as I can. It itches to change to PagingTerrainManager though...
Back to the Eris woes though. For some reason it's impossible to change to orientation of a Ogre node which is a child of another Ogre node. The solution is to let all nodes be children of the root node. But this is just an interim solution. Took me some days to find out though. I still can't understand how the change in eris affects ogre in such a way. Is has probably something to do with some code path not being follow in the previous Eris. I don't know.
Damnit!
And that's why we all love regression testing, and hate the lack of it.
Anyways, here's a screen of Ember in it's current (pre Eris 1.2, pre Ogre 0.15.0) state.
Back to the Eris woes though. For some reason it's impossible to change to orientation of a Ogre node which is a child of another Ogre node. The solution is to let all nodes be children of the root node. But this is just an interim solution. Took me some days to find out though. I still can't understand how the change in eris affects ogre in such a way. Is has probably something to do with some code path not being follow in the previous Eris. I don't know.
Damnit!
And that's why we all love regression testing, and hate the lack of it.
Anyways, here's a screen of Ember in it's current (pre Eris 1.2, pre Ogre 0.15.0) state.
Subscribe to:
Posts (Atom)