I've just updated XDPX. Had problems but eventually managed to get it to update.
Here are the latest updates (save others from wading through the updates page):
Printable View
I've just updated XDPX. Had problems but eventually managed to get it to update.
Here are the latest updates (save others from wading through the updates page):
Thanks for that Egg.
I wonder what this one means?
Attachment 118372
Transparency already are supported in PDF, is it concerning the gradated transparencies ?
Marc
Hi Mark - The last iteration of PDF/X supported was PDF/X3 2003 so this is a more recent filter.
This link might help https://en.wikipedia.org/wiki/PDF/X
I suspect that prior to this version transparency was handled by converting the transparent object to bitmap where as this new version may actually maintain the transparency. Mike Wenzloff knows a lot more about this stuff maybe he will clarify when he sees this.
I had to look up the support for multi-weight fonts. Here is what it says:
This is helpful. Many of the Google fonts get updated frequently which in the past would trigger those font not found messages even though the font was already installed.Quote:
Improved support for multi-weight fonts (July 2017)
We’ve made some significant changes to the way that Designer handles multi-weight fonts. Prior to this update if a font was updated so that its multiple weights were presented in a different structure, this could cause Designer to show missing font warnings for documents that had been created using the previous version of the font. Now any such changes to a font should be transparent, so you can update to a newer version of the font without encountering any problems with existing documents that use that font.
This update also has improved handling of the Bold button with multi-weight fonts. Prior to this update, Designer would not allow bold to be turned on if the selected text used anything but the regular variant of a font. Now it will work with any variant, automatically choosing the most appropriate heavier weight variant of the same font. For example if you have some Open Sans Light text selected and you press the Bold button, the text will appear as Open Sans Regular.
And the smart shape arrows provide hours of fun for the bored and/or easily amused.
but not in the PDF/X series up to now
here is a link to PDFA.org description, and a quote:
https://www.pdfa.org/wp-content/uplo...a-Nutshell.pdf
Quote:
In addition, PDF/X-4 allows the use of transparency, a PDF 1.4 feature forbidden in PDF/X until PDF/X-4.
The main premise for PDF/X-4 has little to do with transparency, it is for the allowance of mixed color-space tagged content. So for instance, one could have a tagged Adobe RGB image in an otherwise CMYK document color space and the tagged Adobe RGB would remain so in the produced CMYK PDF. This is late-binding.
In early-binding, all content would be converted to the destination color space for the PDF. This is what Xara products have always done—and still do with the new PDF/X-4 PDF filter. Until such time as there is both a document, color-managed space AND that the Native format actually works properly, this early-binding process is all Xara is going to manage.
As regards transparency, it took not using a PDF/X type of PDF export to maintain transparency in the past. And for print services requiring a PDF/X-4 pdf with transparency, I would need to run an action in Acrobat to ensure compliance when needed.
But the main thing, to me, is the fuller premise of PDF/X-4 is not met.
(And the bug of CMYK-defined elements turning black when outputting an RGB PDF version still happens.)
thanks MIke - I don't really need transparency in PDF/X - what you say about the rest is interesting, and I don't see me renewing just for that when I can use other programs for that sort of work if necessary that do it better :rolleyes:
nothing else there for me this time
@egg - thanks for the info
As far as I know, only Adobe products truly realize the fuller potential of PDF/X-4. Mixed content is still converted to a destination space in everything else. Not that I have tried in every application, just the ones I use. But I am unaware of others.
I would be remiss to mention that the PDF/X-4 file that XDP now produces (and the other applications I use that support PDF/X-4) is still a valid PDF/X-4 file.
Gary, I don't think those arrows are new to this update, it's the flowline arrows that are. Quite useful.
ok mike thanks for that too... I can use adobe when I need to...
Indeed they are Acorn, all 1x3segment lines ;)
Did anyone notice something different when trying to update today?
Thanks Egg.Quote:
Gary, I don't think those arrows are new to this update, it's the flowline arrows that are. Quite useful.
Not sure. My program prompted me to update and I did.Quote:
Did anyone notice something different when trying to update today?
@Gary,
Asked Kate to elaborate about this update in the other thread.
I don't see anything here for those who use the program for drawings/art.
:(
Not only for those.
It is time to realize that the development of the core part of the program is finished, the code is complex, the team is small, the application needs to stay fast as its biggest advantage with the rivals, so better to not risk with mixing the code.
With the price increase the paradox is that those pay more, who love the program most. Those who can see the things objectively already did not extend the subscription.
We need to realize now, in 2017, that it is the wasting of the time to propose anything here or trying to be cool and positive, the core program will be not developed, small additions, bug fixes and online content which going to be added in the future.
Seems to me to be more like a maintenance release than an upgrade. Mostly nonsense stuff of little use or interest to any designer or illustrator. Top of their list... Facebook, G+ and Twitter header templates - Really??? Anyone could make those up themselves in a few minutes. Adding a few photo filters... big deal, most free phone apps can do that and more. The ligatures upgrade is nothing more of a fix.
I too have 'subscribed' to Xara since the beta release of Xara Studio and have updated every time, albeit a few times through loyalty, but this 'upgrade' is taking the Mickey. I can't fathom Magix's pricing structure, the upgrades get smaller and the price gets higher!
On the subject of pricing, on the Xara homepage the pricing is as follows;
Web Designer 365 Premium... $100
Page and Layout Designer 11... $90
Photo and Graphic Designer 365... $60
Total for all 3... $250
But hey wait, you can buy all 3 in one program for just $299 !!! How would that entice anyone?
Got to agree with czehz and Signpig....tinkering at best and trivialities. I have to also agree strongly that most of the stuff theyare releasing involves bits and pieces that can be easily knocked up.
I thought they all did; you have to scale up the line before the green control "Drag to select style" appears.
There are 16 ends in all and you can apply these to either End.
All the controls are Resize, Rotate, End (A), End (B), Head/Tail (A), Head/Tail (B), Drag to select style (A), Drag to select style (B), Middle segment position.
They accept any Brush.
The Fill and Line colours have different effects.
The Head/Tail size is minimally constrained by the line width and maximally by the segment position.
One single 3-segment line of 8pt width and 180 px size for the Head and Tail will almost stop interactive changes for 3 seconds on a fast machine.
The functionality of the lines themselves is accomplished but all four are the same other than their starting state.
Unless I have missed Xara documentation, all the above has been discovered through experiment.
The Drag to select style control is poor as it vanishes at small scale, changes position and the cycle round the options is not intuitive; revolving round its own centre is the one with least effort.
The Head or Tail, when changed do not remain in a locked position so the line pattern can alter and the end points all need to be re-aligned.
Mostly a toy.
Acorn
Boy, I agree. The Smart Arrows are toys as they do not conform to the behaviour other Xara objects exhibit.
While they Snap to Grid, they do not Snap to Objects or Snap to Guides.
Changing a Head or a Tail should not alter the line's positioning.
Simple thing's like adding functionality to the meta-keys; Ctrl+"Drag to select style" to reverse the choice rather than cycling through 16 options.
Acorn
Thanks Acorn. I'm travelling and just now had a chance to try it. Works well.
John