Saturday, March 04, 2006

Universal Binary

At last, starting from v1.6.5, fennel DVDManager is now available as a Universal Binary.  This means that it's not only PowerPC-, but also Intel-compatible.  Yay!

5 Comments:

At 2:26 AM, Blogger graham said…

Hi. Any idea when 2.0 will be out? Is it still worth submitting ideas for 2.0 or is it frozen for features? Thanks

 
At 3:15 AM, Anonymous Anonymous said…

No *definite* idea yet, sorry… Be assured we're doing our best to make it happen as soon as possible though.

Regarding its feature set, it's (almost) frozen, indeed… unless you've got something crucial to add or very easy/quick to implement ;) !

Joke aside Graham, it's always better to send us your ideas/feature requests as soon as they arrive. Don't wait for any given version to do so. You know, any suggestion is considered and potentially added to our (huge…) To-do list. So we're now waiting for the cool ideas you've had ;) !

Bye. And thanks in advance for your feedback.

 
At 8:59 PM, Anonymous Anonymous said…

The word 'die', as in 'Die Hard', is a problem for the 'Pretty Format', as it's confused with the German 'Die'.

Any suggestions around that?

Graeme.

 
At 12:33 AM, Anonymous Anonymous said…

You're right; these words collapse in those languages. Fortunately, with our following explanation, everything should be clear again :) ! (Otherwise, feel free to ask.)

For convenience purpose, we've introduced some default patterns for our "Pretty Format" action for each language we've localised fsDM in; but those patterns aren't immutable. Indeed, if you think you won't need, for example, German-based formatting, in the "Pretty Format" sheet, simply remove this entire line via the '-' button, or double-click it to edit a part of this entry!

And suddenly, there's no more "Die" collapsing ;) !

 
At 2:02 AM, Anonymous Anonymous said…

Graeme, this (abnormal) behaviour of our "Search" action you're depicting here has already been reported to us. Alas, we've not been able to fix it yet due to our lack of a valid environment to reproduce, track, understand, and correct it.

Indeed, this bug is only affecting fsDM on Mac OS X v10.3 "Panther", which we don't support anymore since fsDM v1.6, as mentioned in our "Read Me.rtf" file… (simply because we only have access to Tiger-powered Macs now!)

But you have to know that we're more than willing to fix it if you (or any Panther user) can help us find some hints, test our attempts, etc. re this issue. Until then, all we can do is add a new item to the "Known Issues" section of our "Read Me.rtf", I'm afraid :( !

Thanks for the report, Graeme, sorry for the inconvenience, and please be assured we'll do our best to fix this situation as soon as we manage to put our hands on a Panther-powered Mac.

 

Post a Comment

<< Home