Whrere is the PDF-Bugfix in XDP v15.1?

[handrawn]

one possible issue is, as I understand it, that magix are resposible for compiling the installers [having taken the marketing and distribution on board]; they may have other priorities...

[Guest]

Could be. But then again Magix is actually selling a defective product since May (when 15.1 was released). They surely can't have any interest in that?

[ernie-f]

This is a poor and well known behavior. I bought a bug and they sell it as a update to be fixed. Maybe as a feauter like the squoosh thing.
Magix this is terrible. If I would treat my customers so like You treat us, I'm out of bussines. PLS change that immediately.

[handrawn]

well magix have an extensive product range, the question is how much of a priority is xara to them?

v15.1 actually fixed a lot of things wrong with v15.0 but not the PDF issue apparently; why i don't know, but perhaps it is not logistically practical to issue fixes 'at the drop of a hat' they have to wait in a 'queue'

[handrawn]

Ernie - it is bad, however I get the feeling [no more than that] that xara would have to make a case to magix for pushing this fix out ahead of the next update in terms of compiling/distributing, especially after the unplanned work that went into ver 15.1 itself

[Jonopen]

Could a temporary way around this be for Xara to make available the updated/fixed export filter file(s) so they can manually be replaced. A bugfix of this type should be available to all, not just current subscribers.

[ernie-f]

Could a temporary way around this be for Xara to make available the updated/fixed export filter file(s) so they can manually be replaced. A bugfix of this type should be available to all, not just current subscribers.

It is an absolute impertinence to output a faulty version and then to keep the errors ready for subscribed users only. Xara/Magix do your homework and correct the delivered bugs for everyone.

[iamtheblues]

Ernie - it is bad, however I get the feeling [no more than that] that xara would have to make a case to magix for pushing this fix out ahead of the next update in terms of compiling/distributing, especially after the unplanned work that went into ver 15.1 itself

Steve, my heart bleeds for Xara - no, it really does!! (where is the sarcasm smiley when you want one?)
If my memory serves me right Xara wasn't forced at gunpoint to sign up with Magix. The worst day's work it ever did.

[Guest]

Well, I'm not exactly sure who's to blame here....
Yes, Magix is responsible for marketing and sales, but does that really mean that they have any kind of control concerning the product's release cycle?
And not to forget, (if my memory serves me right) XARA had their moronic subscription service that doesn't differentiate between functional upgrades and bugfixes even before they officially joined forces with MAGIX.

Don't get me wrong - not really a MAGIX fan, either.
I always had the impression that MAGIX is the place where software goes to die...

[handrawn]

magix and xara have been in 'partnership' for 10 years or so - technically magix owned xara from that point, and as far as I am aware they still do, aithough xara operates as a seperate entity

xara have recently given [magix has taken ?] control of marketing and distribution - on this forum [no link sorry] a xara employee mentioned that a hold up re the last update was [in part] due to magix having not complied the installation package - so my understanding is that wheras xara produce the program code, magix take it from there to produce the .exe installers

I am not sure what priority xara product has in the magix product range; prudence prevents me from hazarding a guess - but yes if they are doing this they are a factor in the release cycle...