Jump to content

rumo

Members
 View Profile  See their activity

  • Posts

    53

  • Joined

  • Last visited

 Content Type 

Everything posted by rumo

  1. rumo
    Thanks again for the detailed answer, @thomaso. It worked!! I already had a Studio Preset for my workspace, though I did not find a file for it. Anyway, like you suggested, I copied the three folders from ~/Library/Application Support (one for each app) and the three .plist files from ~/Library/Preferences and pasted them to the Shared/Public folder of my second user account. I also saved my custom shortcuts to the shared folder. I then switched to the second user account and copied and pasted the files and folders in their respective Library folders. I then restarted my Mac (seems not to work without). Now the Affinity suite on both of my user accounts looks exactly the same. Again, thank you so much!
  2. rumo
    Thank you very much @thomaso for taking the time for your quite detailed reply to my question. I really appreciate it. As for your suggestion above: this is what I already did, but without any effect. Maybe I picked the wrong folders (didn’t find any for the workspace or custom shortcut settings at all). Could you elaborate which folders and files do I need to copy? That sounds pretty tedious. I might give it a try, but it’s likely not worth the hassle. If it works manually I’d be happy. I don’t change my settings that frequently after all.
  3. rumo
    Hello there, I am still using the Affinity Suite V1, but I think this applies for V2 as well. I have a Mac with two user accounts and want to use my Affinity Suite on both on them, and I want my settings, workspaces etc. to be synced between the two. I have searched this forum and the web and didn’t found a working solution so far. I wouldn’t mind if I had to manually copy the necessary files. Can anyone help me with this? Note: I bought the suite here at the Affinity Store and currently run MacOS Ventura. Regards, Johannes
  4. rumo
    I have a related question, and since I am still on V1 I decided to post here rather than opening a new topic: Why are rounded corners slightly off perspective when applied after transforming an object into the isometric grid? Please see the two images attached. On the left: square object, rounded corners, transformed into curves, then transformed into isometric view (fit to projection layer). On the right: square object, transformed into curves, then transformed into isometric view (fit to projection layer), then round corners applied. It is the one selected in the path view (second image). As you can see, when I apply cound corners in the isometric view, the perspective is off enough to look weird/not correct – it is even more obvious with more rounded corners and/or smaller sized objects. Am I doing something wrong? Or has this been fixed in V2? Best regards, Johannes
  5. rumo
    I second this, like in the old thread.
  6. rumo
    @claidheamdanns I fully agree with your point of view. Without GREP styles I still miss a crucial tool. Whenever a project requires more then basic typography, like kerning punctiation or other microadjustments, I am lost without Indesign. I was told that the staff has it on their list, but that was two years ago.
  7. rumo
    +1. Came across this today. This is a basic typography feature, not something worth some kind of workaround. Looks like the more I use Publisher, the more I ran into those "missing basic typography features".
  8. rumo
    That’s a feature not easy to spot. I’d still like an option to have select/deselect not logged by the timeline, but the ability to branch the protocol is a completely different approach. I have to try and test it. Thanks Walt!
  9. rumo
    Yeah, but that’s still a workaround, not a solution, right? Thanks nonetheless @Johannes.
  10. rumo
    Thanks mate! Never thought of this, but it definitely is a better workaround (there could still be an option though).
  11. rumo
    Has this one been solved yet? Came across it recently and thought it would be my printer. Then prints from Apple Preview turned out to be fine, as always. So I ended up doing the same workaround as @Johannes.
  12. rumo
    +1 . You can’t do sophisticated typography without it.
  13. rumo
    Hi, is there any way to NOT have the select/deselect command included in the protocol? I have tried to get used to that ever since I switched from Indesign, and it looks like I can’t. For example, when I go back in history (protocol) to undo something to just have a look like it looked before and then deselect the current object to really have a proper look without disturbing blue lines around it, I can’t redo that because the protocol logged the deselect as an action. So whatever changes I did, I have to do them again. I doesn’t make any sense to me why select/deselect should be part of the protocol at all. Or didn’t I get something here? Best, Johannes
  14. rumo
    If we can open IDML files, are there plans that we can also export into IDML at some point? It would be just vice versa I guess. Thanks for the updates and all the necessary efforts. I appreciate it. However, I would be glad to see a world-ready paragraph composer, first-line only base grid fit, a pipette tool that can copy styles and GREP implemented. Then AfPub would finally be a full Indesign replacement for sophisticated book projects. 👍
  15. rumo
    Thank you very much in return @Jon P. I appreciate that. Maybe adding a feature similar to the World Ready Composer would solve the issue. And I have confidence that the you are interpreting the font correctly. However, neither Fontlab nor fontdrop.info nor Typeface have this feature and render the font as it is supposed to be, without any issue. What do you think about that?
  16. rumo
    @Alfred Cheers mate, that post got lost in translation somehow. My bad. Thanks Jon, it’s on its way.
  17. rumo
    My pleasure, @thomaso. Update: The font also works fine the Typeface font organizer and also in Fontlab 7. So unless I am not mistaken (possible) it is likely to be a bug in Publisher. I hope that somebody from the tech staff sees this thread and reaches out, so I can sent them the font file for investigation.
  18. rumo
    The text is set in German, and nothing happens when I change the language. Also, since the font only works in Indesign CC when the Adobe World-Ready Paragraph composer (aka. global) is activated, I thought that there might be something similar in Publisher. But I clicked myself through all options in the glyphs, paragraph and text box panel, without solving the issue.
  19. rumo
    Of course not ;). It is a pre-production version and some joints still need to be smoothed out. But that is not related to the problem I have with Publisher.
  20. rumo
    Hi guys, I am experiencing a weird behavior of Publisher with a preproduction font that lays heavily on the contextual alternate Opentype feature. The problem: The font is valid and works fine in Indesign CC 2021 and the Typeface font manager as well as on fontdrop.info. However, when I turn on the contextual alternatives in Publisher, all of them are rendered except for the ones related to the lowercase "i" (like "is", "in" etc.) . See first screenshot for Publisher (blue), second for Indesign CC (black). I am able to reproduce the issue. Please note that I can only provide the font file directly to the support staff. Cheers, Johannes Latest version of Publisher macOS Mojave (latest) Hardware Acc.: On
  21. rumo
    I still second this. Dear Affinity staff, this is a must have in the field of editorial design.
  22. rumo
    Any news on this? I know it’s about 3,5 years after the initial post, but I tried to to the exact as @PDL: I have exported DNGs from Capture One and imported them into Affinity Photo's Panorama tool. Stitching works fine, but I can't export the document as a DNG, so it can't be fully edited in Capture One. Since DNG is an open format I wonder if it is difficult to bake it into Affinity Photo?
  23. rumo
    Any update on this? The workaround is nice, but this option is a must for typographers, actually.
  24. rumo
    Hi @Gabe, sorry for the even longer delay in return. This happened in several documents, but I have to check back to see if it still happens after the latest updates.
  25. rumo
    Hi folks, is there any way to tell Affinity to NOT track a deselect, caused by a mouse click, as part of the protocol palette? Because for me, this is somewhat annoying. Coming from Adobe last year, I am used to go back in time, watch a previous state, maybe copy a certain element and then go forth to the latest state. Now with Affinity, as soon as I click somewhere on the canvas in the previous state (for example to get rid of a visually distracting selection), the protocol changes and I can’t go forth to my latest edit. Best, Johannes
×
×
  • 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.