Come and get it, fresh from the oven! The vtk-fltk thing is at v0.2, muchos thingies fixed and improved. It's weekend. Overall the week has been quite productive, but it's still frightening that it's over. This weekend we're planning some serious shopping...

VTK is building on the Octane; as soon as it's done, I can test vtkFlRenderWindowInteractor on it. It seems there might be problems on Solaris as well, but that I can unfortunately not test (yet). And then there's still the little issue of testing it on windows. Yuck.

I've branched off from FlvtkInteractorWindow (but it keeps my fixes) and started vtkFlRenderWindowInteractor. I have done this so that my ideals of keeping things as simple as possible can be realised without hindrance. Click here for more information.

I rule. Actually mpatrol rules. All your bugs are belong to us! dscas1 is now seemingly rock-solid. In addition, I've upgraded to 2.4.2-ac20 and nvidia drivers 0.9.767... these seem fine, and I've now enabled AGP again. On this SMP work machine, 0.9.6 refused to work stably on a 2.4.x kernel with AGP enabled.

Thanks to the mpatrol memory allocation checker (and specifically its --dynamic mode) the bug has had its little head squashed. It turns out that it was hiding in a very old vtk class that I'd written *mumble mumble*.

These past two days have NOT been nice (due to this very elusive bug) but on the bright side, FlvtkInteractorWindow is now cleaner than ever before (all remotely potential problem areas were fixed) and this will shortly be available from my website.

AAAAARRRRRRGGGGGGGGHHHHHHHHHH I've been chasing the same irritating bug (in one form or the other) for the past 2 days and I'm getting really tired. If tomorrow is a normal working day (please please please) I might get it squashed and then get my life back to normal. Bugs have a strange effect on me.

Yesterday was a bad day for public transport. Down day! Sit! I spent 3 hours on trains and buses for a presentation of around 1.5 hours... at least the presentation (on fMRI) was really good.

I'm currently still spending some time on dscas1: mostly some cleanups and refinements so that I can hand it over to the FE boys to start playing with. Note to world: volumetric data is difficult to work with, purely because of the raw amound of data that one has to shuffle around.

We went to Cascades Japanese restaurant in the Hague last night. The food was absolutely divine and we'll definitely go there again in the future.