Jump to content

woefi

Members
  • Content count

    87
  • Joined

  • Last visited

About woefi

  • Rank
    Member

Profile Information

  • Gender
    Male
  • Location
    Austria

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Well, this feature "looks" like the already familiar, very useful feature from old Indesign CS5 "Add Unnamed Colors": https://helpx.adobe.com/indesign/using/swatches.html It does nearly the same, but just not quite right (e.g. slightly, but consistently wrong colors / not applied to original object) so that it's completely useless to me. (read: Yes, I will not use this at all.) And given that the awesome Affinity team already spent as much time implementing it to this level – it'd be a shame for them to stop 2 meters in front if the finish line and call it a day.
  2. sure, but what's the more likely use-case for a dtp-app? You don't want to lose oversight of your assets. A (pre-defined) simple set of project related color-swatches being a part of it -besides linked Images and consistent typography.
  3. So, since the first beta came out I keep testing and hoping that the colour palettes finally work "right". Now with release .238 (mac) this bug is still not fixed. Obviously whats happening is, Designer scans all the colours using "RGB-view" and includes shadow effects and placed images, which produces: A) way too many color swatches (if you have an image placed or a text with simple shadow effect) B) the wrong colour values if (it should be clear, we are talking about a dtp-app) the colours are mostly CMYK. C) the colours are not global AND are not used by (or applied to) the objects (in which the function found it to begin with) Especially in desktop publishing, you have to have a clean view over used assets, links, colour-swatches, fonts used in the document. Unlike in a photograph, you cannot use a "slightly brighter" red or a "subtle darker" grey in different places of your pages, just so that the overall "feeling" is the same. These must be, by default, "global colours" and you have to rely on the accuracy! I understand there is "some" complexity as all three apps re-use the same engine. Most users probably don't need this behaviour in Photo and some more need it in Designer, but in Publisher it is essential to have consistent values across multiple related documents.
  4. Why does the Command "create document palette from document" recreate a new palette over and over again? Instead of updating the existing one? Also these colours should be GLOBAL colours by default - at least please give us a preference for this or an option.
  5. This. I also am used to work with low res or unretouched versions of photos in my documents, and upon finishing the project after several weeks of changing things, a simple task of replacing all the images with what is the approved version, by opening a seperate Finder window (or explorer for win). And from there flick those pics in. It’s literally a task of seconds even for a multi-page brochure. If I had to do this with a command (replace) and getting a picker window, and then for each one had to navigate to the right folder, I would go nuts! Of course it is absolutely mandatory to keep all the positioning parameters, like: scale, offset, rotation, auto fitting, visible layers, crop box/media box, and so on. (the way, indesign does it)
  6. I noticed a bug in the appearance of the navigator palette. I'm viewing this on a non-retina-display. the zoom-percentage (186%) is slightly blurred, while for the swatches pallette, the opacity percentage (100%) is sharp(er) Although I know, text has to be a little bit antialiased, but this seams to be a bug.
  7. I just tested this. It works. This is exactly what I wanted. Thank you, @DM1! This context-sensitive bottom row is really hard to understand. I never know if an icon is a toggle switch or a button... and it really makes no sense to change the dpi via a (percentage?) wheel-button or is it a download progress indicator?
  8. wow. just wow. I have high hopes on affinity, but this UI is not easy discoverable... not at all
  9. OK, first sorry @MikeW, didn't want to offend you in any way, but your point did not explain why every other pdf-viewing program is able to retain the original measurements. Internals do not and have not to matter for the enduser. I made a test and yeah... designer for mac also imports the files using points... I manually changed the units to mm and voilá: now its right. (on the desktop at least) So why would this not work on the iPad... What does not smell right is that the iPad-menuitem for changing this is called "resize" I don't want to resize anything...
  10. Excuse me, but EVERY pdf I ever created is displayed with the right measurement on various systems and viewers (adobe or 3rd party). Every fileformat has its internal unit-system but also some metadata to remember at which target-units you created it. So the question is: why does Designer-Mac respect those and Designer-iOS not?
  11. I use the iOS version of Designer to open (and convert) my illustrator files. I know that Designer‘s „import“ reads only the embedded Pdf-part of the ai-file, which is sad and on top of that on iOS it has problems with custom fonts (as there is no real font management on the iPad) But one problem drives me crazy: I make my designs and occasional floor-plans in Millimeters and every single imported file comes in as points. As I learned in other places in this forum, there is an option „resize“ which you can use th change the units to milimeter, but that resizes the documents contents the wrong way. Of course, because I don‘t really want to „resize“ - I want to „change the units“ or „KEEP ORIGINAL UNITS“ on import So please, if that‘s a feature request or a bug report - This works in the desktop version.
  12. Although I use the metric system, I still use points for text as it's industry standard. So this is enabled.
  13. Thanks for finding this option! Sadly this does not do all the things I expected... My Situation: I use Illustrator to draw some blueprints/plans of our home with exact scale 1:100. This means 1 millimeter on the plan equals 10 centimeters in reallife (hooray metric system!) Now moving my files to Designer and everything is now in points, which I would describe as a „bug“ (you should ALWAYS keep the same units of the source file!). If I do the trick to change the units, all is now displayed in millimeter, BUT with the unchanged pt-values - a 1 meter wide door which was 28.3 pt upon importing is now 28.3 mm - not 10mm which would be the original scale. I wonder if this has to do with the fact that designer is not able to import the raw illustrator-part of the file - only the pdf compatible version. And here it matters, HOW Illustrator chooses to export the pdf-part... Anyway, obviously at this stage there is no good workflow to move thousands of ai-files accurately to designer.
  14. I'm sorry but it wouldn't matter if I sent a PDF with 1200dpi (rasterized) parts to my (various) print shops – through their RIPs it's recognized as <IMAGE> and gonna be rasterized at 300 or 400 dpi at best - which you can see (tho there are ways of including 1-bit TIFFs at around 2400dpi). Imagine you would print a page mostly full of text, which you had rasterized before output, and then think about the amount of data such a multipage-pdf would have... And as alternative to this, only rasterizing parts of the page (as Affinity does now): On paper you will see the border at which pixels take over. I'm talking about the output on a 4c-professional printing-press of course, which I'm doing for 26yrs. That's what publisher, or DTP in general, is mostly about, I guess.
×