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

big smile

Members
  • Posts

    325
  • Joined

  • Last visited

Reputation Activity

  1. Thanks
    big smile reacted to Jon P in PDF import issues   
    We often tag posts with a report number, but that's mostly just for internal use and we don't do it every time we make a report.
    I mentioned it's reported earlier in this thread, so often we'll let you know that it's logged when you report an issue
  2. Thanks
    big smile reacted to Jon P in Publisher: How to make inner margins appear?   
    They don't on the Master Spread, it's like it is being treated as a single spread.
    I can see what you mean but need to try suss out how to reproduce this from scratch
  3. Thanks
    big smile reacted to Callum in Beta question   
    Hi BigSmile,
    Once a beta build has been patched into the release version you should be able to open your beta files with the release version of the app
    Thanks
    C
  4. Thanks
  5. Like
    big smile got a reaction from Move Along People in Publisher: Working with imported Publisher files: Selecting pages and resizing   
    That works perfectly. Thank you so much!!
  6. Like
    big smile reacted to Joachim_L in Publisher: Working with imported Publisher files: Selecting pages and resizing   
    Everyone has a different workflow, mine is to keep pages separate. This means I would have setup as A5 portrait, facing pages, starting left. So if needed you can export or import as separate pages.
    Right now you have to use the Vector Crop tool to get the placed document smaller. Of course you can select which page to show. Click the placed document in the layer panel and have a look now at the top context toolbar. There is a dropdown, where you pick the page that has to be shown.
    But I must admit, that in the current 1.7.3.481 is a small render glitch not always showing the correct page, depending on the used zoom level.
  7. Like
  8. Like
  9. Like
    big smile got a reaction from IgorRock in Request: better handling of imported styles when copying and pasting   
    Issue:
    In my Affinity Publisher documents, I tend to use the same text styles. When copying and pasting text between the documents, the styles get duplicated with a number added at the end. This happens even if the styles are identical. Example:

    ^ These are all the same style which have been duplicated when copy & pasting between documents. 
    Solution:
    When copying and pasting between a document, Affinity should ask the user how handle duplicate styles rather than just numbering them.
     
    Here is an example of how it could work:

    This dialogue box would pop up whenever copying and pasting text in situations where Affinity would currently just duplicate the style.
    This dialogue box would be optional, activated first via an option in preferences, so users who like the current handling of style can chose not to activate the option. 
    Merge Styles - Keep incoming definition This option will cause the two styles to be merged. All values will follow the source document. 
    Merge Styles - Keep local definition This option will cause the two styles to be merged. All values will follow the local document. 
    Create new style - This will create a new style (which is how Affinity currently handles it by duplicating the style and adding a number to the name).
    Additional options:
    Clear Overrides - Any differences between the local and incoming style will be discarded. 
    Keep Overrides - Any differences between the local and incoming style will be kept as overrides. 
    Save Overrides as character style - The differences can be saved as a character style. 
    Example:
    I have  "Document A" which has  text that has a style called "English translation". This is just Helvetica, bold text 12pt. 
    I copy and paste this text into "Document B" that already has a style  called "English translation". If I select "Merge Styles/incoming" then the style from Document A will be used. If I click clear overrides, then any differences between the text in document A&B will be lost. 
     
    Who would this be useful for:
    This would be useful for users who regularly copy and paste text between Publisher documents. 
     
  10. Like
    big smile got a reaction from Jocarnail in GREP Styles   
    +1 for GREP styles and Nested Styles
     
    The Find and Replace is a powerful workaround, but being able to use GREP and Nested Styles would make things less error-prone (especially as Find and Replace doesn't allow you to save searches and it can be fiddly to enter in all the details on a repeated basis). 
  11. Like
    big smile got a reaction from Jocarnail in GREP Styles   
    Yup, I agree, the find and replace is too fiddly to use for multiple tasks (especially as you can't save searches). That's why I think Nested and GREP styles are an essential addition. 
    Plus, with find and replace, it's all too easy to forget to do it. With Nested and GREP  it happens automatically, so it makes things less error-prone. 
  12. Like
    big smile got a reaction from Felledk in Feature Request: Keyboard shortcuts for transform options   
    Affinity has a real good Keyboard Shortcut option in Preferences.
    Please consider adding keyboard shortcuts for the transform options so users can set their own shortcuts for these options.
    Example:
    I can set CTRL+Alt+CMD+X for Transform X. Then in future, when I press CTRL+Alt+CMD+X, the X field in the Transform panel will become highlight and I can type in the value, without needing to use the mouse to select the field. 
    Or I could set  CTRL+Alt+CMD+9 to the top right anchor point. Then when I want to change the anchor point of an object, I can just type  CTRL+Alt+CMD+9 without having to use the mouse.
    Mock ups:

     
    ^ A mock up of how it would look. Note that there is a new "All Affinity" option so you can use the same shortcuts across all the affinity apps (Photo, Designer and Publisher).

    ^ Once you've set a shortcut, you can type it and the relevant field will automatically become selected. 
    WHY WOULD THIS BE USEFUL?
    1. Automation
    Affinity doesn’t have scripting support, but it does work very well with automation packages such as Keyboard Maestro. 
    Being able to transform objects on the page is a key automation task. At the moment, this can be achieved by using a tool such as Keyboard Maestro to access the transform panel by emulating mouse movements. However, this is very prone to failure. Being able to enter keyboard shortcuts would ensure Macros are less prone to failing.
    2. Reduce repetition
    If you have a lot of objects to transform, using the mouse gets tedious. Being able to type keyboard shortcuts is more efficient. 
    POTENTIAL DRAWBACKS AND SOLUTIONS
    Coming up with separate keyboard shortcuts for the transform panel options may be cumbersome (e.g. CTRL+Alt+CMD+X is quite the command to remember). However, because this feature would be made available via the Keyboard Shortcuts option of Preferences, the user is free to set shortcuts that work for him/her).
  13. Like
    big smile got a reaction from Dan C in Publisher: Create a gradient mask   
    Wonderful and thanks for the awesome video!
  14. Like
    big smile reacted to Dan C in Publisher: Create a gradient mask   
    Hi big smile
    After creating your mask, make sure it's selected in the Layers Studio, then simply use the gradient tool to draw a greyscale gradient across the mask, as shown in my quick screen recording below -  2020-01-28 13-14-49.mp4
    I hope this helps!
  15. Like
    big smile reacted to Desmild in Feature Request: Keyboard shortcuts for transform options   
    Yes a transform shortcut would be very nice. I really miss the oppertunity to hit F6 to increase size of a object by 1% or 5%.
    It would be wonderful to increase length and width also with a shortcut.  
     
  16. Like
    big smile got a reaction from Krustysimplex in Request: better handling of imported styles when copying and pasting   
    Issue:
    In my Affinity Publisher documents, I tend to use the same text styles. When copying and pasting text between the documents, the styles get duplicated with a number added at the end. This happens even if the styles are identical. Example:

    ^ These are all the same style which have been duplicated when copy & pasting between documents. 
    Solution:
    When copying and pasting between a document, Affinity should ask the user how handle duplicate styles rather than just numbering them.
     
    Here is an example of how it could work:

    This dialogue box would pop up whenever copying and pasting text in situations where Affinity would currently just duplicate the style.
    This dialogue box would be optional, activated first via an option in preferences, so users who like the current handling of style can chose not to activate the option. 
    Merge Styles - Keep incoming definition This option will cause the two styles to be merged. All values will follow the source document. 
    Merge Styles - Keep local definition This option will cause the two styles to be merged. All values will follow the local document. 
    Create new style - This will create a new style (which is how Affinity currently handles it by duplicating the style and adding a number to the name).
    Additional options:
    Clear Overrides - Any differences between the local and incoming style will be discarded. 
    Keep Overrides - Any differences between the local and incoming style will be kept as overrides. 
    Save Overrides as character style - The differences can be saved as a character style. 
    Example:
    I have  "Document A" which has  text that has a style called "English translation". This is just Helvetica, bold text 12pt. 
    I copy and paste this text into "Document B" that already has a style  called "English translation". If I select "Merge Styles/incoming" then the style from Document A will be used. If I click clear overrides, then any differences between the text in document A&B will be lost. 
     
    Who would this be useful for:
    This would be useful for users who regularly copy and paste text between Publisher documents. 
     
  17. Like
    big smile got a reaction from Move Along People in Affinity Publisher: How to link text frames?   
    @haakoo Thank you so much for your help! 
  18. Like
  19. Like
  20. Like
  21. Like
    big smile got a reaction from Ruddi Hansen in PDF export defaults   
    When you create a facing-page spread in Publisher, the PDF export will give you the option of exporting as Spreads or Single Pages. By default, it is set to spreads. 
    It would be nice if in Preferences, you could select to set the default to Single Pages. 
    If I had a penny for every time I exported out as Spreads because I forgot to switch to Single Pages, I would be one rich big smile!
  22. Like
    big smile reacted to Catshill in PDF export defaults   
    I’ve previously indicated that the customisable preset should remember this setting. It happens to me a lot as well.
  23. Like
    big smile got a reaction from Catshill in PDF export defaults   
    When you create a facing-page spread in Publisher, the PDF export will give you the option of exporting as Spreads or Single Pages. By default, it is set to spreads. 
    It would be nice if in Preferences, you could select to set the default to Single Pages. 
    If I had a penny for every time I exported out as Spreads because I forgot to switch to Single Pages, I would be one rich big smile!
  24. Like
    big smile got a reaction from PaulEC in PDF export defaults   
    When you create a facing-page spread in Publisher, the PDF export will give you the option of exporting as Spreads or Single Pages. By default, it is set to spreads. 
    It would be nice if in Preferences, you could select to set the default to Single Pages. 
    If I had a penny for every time I exported out as Spreads because I forgot to switch to Single Pages, I would be one rich big smile!
  25. Like
    big smile reacted to Sean P in Add and Combine cause Designer to hang   
    Hi big smile,

    Thanks for the files. This is a known issue that is with development so I've passed your files onto them. 
    Thanks.
×
×
  • 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.