Jump to content
You must now use your email address to sign in [click for more info] ×

postmadesign

Members
  • Posts

    487
  • Joined

  • Last visited

Everything posted by postmadesign

  1. Global colors can only be added to document palettes, I believe
  2. I am not completely sure, but I do believe that I was at least able to drag the layers. I can't remember if the renaming worked OK
  3. Oh, I noticed something else that seems to be buggy in the layers panel: I can not seem to be able to rename a group. See the small screen capture: group names bug.mov
  4. I am having difficulty arranging layers in the latest Beta: I can not drag the layers in any way. The only way to change the order is to use the buttons on the toolbar. I can select and group multiple layers, but I can not drag layers into or out of the group as well. Also layer selection feels rather slow. I hope you can fix this? iMac 2011 (no Metal), El Capitan
  5. This is a huge improvement! I tried it on an A3 file that had one hi-res image. It was 15,3 mb in the previous version. In the update and after newly linking the image, the file size was only 1,1 mb! This is a big deal, as it makes for much less hard-drive clutter without loss of performance. Will this method of linking also be available for Designer?
  6. I can understand this, yet I hope they see the sense in my request. It is not a completely new feature, just porting a feature from one part of the suite to another. As these programs share the same codebase this should be quite doable. It is a feature which can be helpful to a lot of designer I think, so I hope they will consider it.
  7. I would still like to know if you plan on adding this feature. It would be very useful, and surely it can not be too hard too implement?
  8. Thank you for this, I have not really tested all improvements, but I did notice some stutter when moving objects with Snapping turned on. When I switched it off, or used the Alt modifier, everything was much 'snappier' I will have a look at the snapping options to see if it changes anything.
  9. @iaing I have been using FEX since version 1, when it was still a free app. I know it quite well, and most of the time it did a decent enough job. But the newer versions do not support auto activation for CS5, so I tried FontAgent Pro, which did offer this. It seemed to work OK, but overall it was very slow activating and deactivating font, and its database is way more complicated that FEXs. The newest version (9) is supposed to do auto-activation for Affinity apps, but Publisher crashes on start-up every time I tried this. After running into some more problems I switched back to FEX, only to have other problems there... I guess a lot of my problems are caused by having an older Mac (2011) with lots of fonts and old stuff on it which causes problems. I just ditched auto-activation for now as it was more trouble than it was worth and simply manually activate what i need. I tried RightFont and quite like the simple interface, although I have not put it through its paces. I will probably stick with FEX for now and might switch when I get a new Mac. As for the specific Affinity problems you describe: especially the fact that activated fonts are not shown correctly is annoying, and it might catch you out if you are not careful, when exporting to PDF for print. I hope this gets fixed.
  10. I am slightly confused by the following issue: I have Auto-Activation set up in RightFont, a font manager I am testing. Its is supposed to auto activate fonts for affinity apps. However I tried this with the app store version of designer, but though it does activate the font. When I manually activate the font it does not change the appearance in Designer. The font is displayed as the default fallback font no matter what I do. I have to close and re-open the document for the fonts to show up correctly. Note that when I activate a font I have not yet used and then use in Designer in the document it does so correctly. Why is this in the beta thread? Well because the Beta apps do offer the correct font auto-activation. After activation the appearance changes directly. What I don't understand is why the Beta works differently than the app-store version. Has the code for this changed in the 1.7 versions? And if not why is there a difference? Will the 1.7 version once released behave as the 1.6 app-store version or the 1.7 beta?
  11. A thing I really miss in Designer is the Font Manager that Publisher has. If I have a missing font in Designer, I don't get a full readout, only a small pop-up, and it is not possible to get detailed info what is missing. This is why I really need this, because even if it is not a layout application, I would use quite a lot of fonts in my design, so having an overview would help. As this is already in Publisher this should not be too hard, right :-) Also I noticed that font auto-activation from FontExplorer works quite well in Publisher, with fonts updated almost immediately, but in Designer the displayed replacement font does not automatically change and I have to close and re-open the document for it to properly display the fonts.
  12. This is a typical example of not knowing you needed something, and now you know you really do. Great work!
  13. I have been wondering about this for another reason: The App-Store apps are all sandboxed, the Serif store version is not bound to this (I believe?). The issue is with font auto activation: I have FontAgent Pro installed, and it works well for the Beta versions I have installed, but not for the app store versions. I wondered if this has something to do with it being sandboxed? Also could the non-app store version potentially be less limited in the ability to add plug-ins to the software?
  14. I have an issue with a font manager called FontAgent Pro. It has a font auto activator, which is very handy because I use many different fonts and don't want to have these activated all the time. I run into the issue where the auto-activation works very well for the Beta versions, but not for the app store release versions. How can this be? Is the way the app store version is sandboxed a limitation for this to work? If this is the case, is it possible to update to the non-app store version of Affinity Designer (sold in the Affinity Store) as I believe this does not have the sandboxing?
  15. I have been working with something similar, and instead of creating an artboard as a symbol, I created an asset out of it. I can just drag the artboard in, change the name and its ready to go. Is there any benefit to using symbols instead. As you said the guides are not treated as something that can be changed afterwards. If there is nothing that needs to change for everyone artboard, an asset seems simpler, no?
  16. I had some success in creating an asset out of an artboard. I set up the artboard up as I wanted, with margins, guides, grid etc. then created an asset out of this (make sure you have the artboard selected with the artboard tool). Set the view mode to "list" in the assets window, as the preview is invisible, but you can just drag it on the canvas and have an artboard exactly like the other one.
  17. It seems I have found the problem: it appears that FontXplorer has some kind of problem with fonts that appear to be activated and visible but are not actually really activated at all. I am not sure what causes this, but after deactivating and re-activating the fonts, they are correctly embedded. InDesign CS5.5 had given me warnings of missing fonts, even though they had been activated in FEX. Reactivating these fonts solved this problem. As these issues seemingly did not occur in Affinity, I assumed it was an indesign issue. Now it seems it is indeed some kind of issue with FEX. If I run into more issues or find what causes them I will get back to you, thanks! I might try it with another font manager to see if I get better results.
  18. I am using el capitan, I am not sure if this makes a difference?
  19. I tried clearing the font cache in the app (reset fonts) but to no avail. Here is a simple document with 4 fonts, 2 embed, 2 don't. I attached both the afpub file and the PDF. I hope this issue can be cleared up. Test_fonts.zip
  20. It is very strange, I did another test with the exact same settings, and still some fonts are converted to curves, some not. They are all OT or TT fonts, no embedding restrictions... Some are activated by FontXplorer, some system fonts. Sometimes when using 2 fonts in a text box, the one is converted, the other not... This is really frustrating as I can not find a pattern, and it seems a serious issue.
  21. Perhaps related to this, but when I paste from Email or from a note in a PDF (acrobat) the text is formatted, even if the original was not? I have to explicitly paste as unformatted text. This is different from indesign and does not make much sense to me.
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.