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

PabloNeirotti

Members
  • Posts

    29
  • Joined

  • Last visited

Reputation Activity

  1. Like
    PabloNeirotti got a reaction from Sean P in Can't load files anymore on Affinity Designer 1.8   
    That has been fixed in 1.8.2. Thank you.
  2. Like
    PabloNeirotti got a reaction from cinebox in Artboards pasteboard background color   
    Since there is no update on this issue, I'd like to necro bump this.
     
    The whole UI is too dark to have such bright surface surrounding the document. Please let us toggle a full dark mode or something while using Artboards!
     
    The current workaround is to draw a huge rectangle, colour it dark grey, and then lock it so I can't accidentally click it. It just feels odd I gotta extend the UI's theme manually.
  3. Like
    PabloNeirotti got a reaction from LilleG in Pixel perfect mode   
    Hey there!
     
    I've seen a lot of posts regarding this, but hey, let me put it from my perspective.
     
    Affinity Designer is the fastest workflow I ever had, but gets really slowed down by the fact that it insists on not using round, natural numbers for coordinates and sizes. It's fine for drawing, but for UI design, it is just a chore of every 1 minute going back to what you just did, adjusting the additional 0.3 on this coordinate, remove the 0.5 on that width, etc... The micromanagement is killing me.
     
    I've followed the guides, read all about the snapping, how it works, and so on. But I still get these floating point values on everything I move and create. It just plain doesn't works.
     
    If this mode cannot be accomplished through existing settings, how about a "Pixel perfect" checkbox on the Snap manager, so that all coordinates of new objects, or existing ones without floating point, remain like such until I force them out?
     
    Basically, not letting objects use floating point until I force them to.
     
    I have read reasons why devs find this like a grey area, but maybe this illustrated another solution, or something closer to it. I don't remember how Photoshop handled this (aww, already forgetting it!) but this was never an issue out of the other million issues it did have.
     
    Cheers! :)
  4. Like
    PabloNeirotti got a reaction from DonaldDymn in Pixel perfect mode   
    Hey there!
     
    I've seen a lot of posts regarding this, but hey, let me put it from my perspective.
     
    Affinity Designer is the fastest workflow I ever had, but gets really slowed down by the fact that it insists on not using round, natural numbers for coordinates and sizes. It's fine for drawing, but for UI design, it is just a chore of every 1 minute going back to what you just did, adjusting the additional 0.3 on this coordinate, remove the 0.5 on that width, etc... The micromanagement is killing me.
     
    I've followed the guides, read all about the snapping, how it works, and so on. But I still get these floating point values on everything I move and create. It just plain doesn't works.
     
    If this mode cannot be accomplished through existing settings, how about a "Pixel perfect" checkbox on the Snap manager, so that all coordinates of new objects, or existing ones without floating point, remain like such until I force them out?
     
    Basically, not letting objects use floating point until I force them to.
     
    I have read reasons why devs find this like a grey area, but maybe this illustrated another solution, or something closer to it. I don't remember how Photoshop handled this (aww, already forgetting it!) but this was never an issue out of the other million issues it did have.
     
    Cheers! :)
  5. Like
    PabloNeirotti reacted to ronnyb in Spotlight support   
    +1  Yeah, that and adding the non-default Layer names as well to be searchable via Spotlight...
     
  6. Like
    PabloNeirotti reacted to MattP in Spotlight support   
    Nice suggestions - I'm sure we can get these sorted soon :)
  7. Like
    PabloNeirotti got a reaction from ronnyb in Spotlight support   
    Hey all!
     
    As always I'd like to thank your continuous support and updates put into Affinity Designer. It is truly starting to become a flawless experience.
     
    There is one thing that I struggle with every day though. I open many different files daily, scattered in different directories, so I use Spotlight to open all my files.
     
    Two improvements I'd love to see are:
    .afdesign are treated as Other, instead of Images. So actual images, websites and other files get priority before it, and .afdesign files get mixed up with "other" files I don't care about. It'd be great if OS X considered .afdesign as Image instead, like .psd - is this something the OS allows you to do? I know Apple can be quite close sometimes often. Photoshop did this one rare thing well, which was filling up the "Notes" section of the Spotlight information of the file with all the text found in the document. This is strange but Photoshop actually nailed that, because I could freely search a file for "what I remembered it had inside" as opposed to remembering the exact words that made up the filename. This could really improve my workflow, and it's safe to assume at least some other people too :). Hope you sometime have time to implement these. I'd be super thankful for it.
     
    Cheers! :D
     
    P.S: I am aware that I can reorder File Type Priority on Spotlight, but when I don't wanna search for .afdesign, I don't want "Other" to clutter the whole search. It beats the purpose of Spotlight xP
  8. Like
    PabloNeirotti got a reaction from Patrick Connor in Spotlight support   
    Hey all!
     
    As always I'd like to thank your continuous support and updates put into Affinity Designer. It is truly starting to become a flawless experience.
     
    There is one thing that I struggle with every day though. I open many different files daily, scattered in different directories, so I use Spotlight to open all my files.
     
    Two improvements I'd love to see are:
    .afdesign are treated as Other, instead of Images. So actual images, websites and other files get priority before it, and .afdesign files get mixed up with "other" files I don't care about. It'd be great if OS X considered .afdesign as Image instead, like .psd - is this something the OS allows you to do? I know Apple can be quite close sometimes often. Photoshop did this one rare thing well, which was filling up the "Notes" section of the Spotlight information of the file with all the text found in the document. This is strange but Photoshop actually nailed that, because I could freely search a file for "what I remembered it had inside" as opposed to remembering the exact words that made up the filename. This could really improve my workflow, and it's safe to assume at least some other people too :). Hope you sometime have time to implement these. I'd be super thankful for it.
     
    Cheers! :D
     
    P.S: I am aware that I can reorder File Type Priority on Spotlight, but when I don't wanna search for .afdesign, I don't want "Other" to clutter the whole search. It beats the purpose of Spotlight xP
  9. Like
    PabloNeirotti got a reaction from MattP in Spotlight support   
    Hey all!
     
    As always I'd like to thank your continuous support and updates put into Affinity Designer. It is truly starting to become a flawless experience.
     
    There is one thing that I struggle with every day though. I open many different files daily, scattered in different directories, so I use Spotlight to open all my files.
     
    Two improvements I'd love to see are:
    .afdesign are treated as Other, instead of Images. So actual images, websites and other files get priority before it, and .afdesign files get mixed up with "other" files I don't care about. It'd be great if OS X considered .afdesign as Image instead, like .psd - is this something the OS allows you to do? I know Apple can be quite close sometimes often. Photoshop did this one rare thing well, which was filling up the "Notes" section of the Spotlight information of the file with all the text found in the document. This is strange but Photoshop actually nailed that, because I could freely search a file for "what I remembered it had inside" as opposed to remembering the exact words that made up the filename. This could really improve my workflow, and it's safe to assume at least some other people too :). Hope you sometime have time to implement these. I'd be super thankful for it.
     
    Cheers! :D
     
    P.S: I am aware that I can reorder File Type Priority on Spotlight, but when I don't wanna search for .afdesign, I don't want "Other" to clutter the whole search. It beats the purpose of Spotlight xP
  10. Like
    PabloNeirotti got a reaction from MattP in Pixel perfect mode   
    Hey there!
     
    I've seen a lot of posts regarding this, but hey, let me put it from my perspective.
     
    Affinity Designer is the fastest workflow I ever had, but gets really slowed down by the fact that it insists on not using round, natural numbers for coordinates and sizes. It's fine for drawing, but for UI design, it is just a chore of every 1 minute going back to what you just did, adjusting the additional 0.3 on this coordinate, remove the 0.5 on that width, etc... The micromanagement is killing me.
     
    I've followed the guides, read all about the snapping, how it works, and so on. But I still get these floating point values on everything I move and create. It just plain doesn't works.
     
    If this mode cannot be accomplished through existing settings, how about a "Pixel perfect" checkbox on the Snap manager, so that all coordinates of new objects, or existing ones without floating point, remain like such until I force them out?
     
    Basically, not letting objects use floating point until I force them to.
     
    I have read reasons why devs find this like a grey area, but maybe this illustrated another solution, or something closer to it. I don't remember how Photoshop handled this (aww, already forgetting it!) but this was never an issue out of the other million issues it did have.
     
    Cheers! :)
  11. Like
    PabloNeirotti got a reaction from monk in Pixel perfect mode   
    Hey there!
     
    I've seen a lot of posts regarding this, but hey, let me put it from my perspective.
     
    Affinity Designer is the fastest workflow I ever had, but gets really slowed down by the fact that it insists on not using round, natural numbers for coordinates and sizes. It's fine for drawing, but for UI design, it is just a chore of every 1 minute going back to what you just did, adjusting the additional 0.3 on this coordinate, remove the 0.5 on that width, etc... The micromanagement is killing me.
     
    I've followed the guides, read all about the snapping, how it works, and so on. But I still get these floating point values on everything I move and create. It just plain doesn't works.
     
    If this mode cannot be accomplished through existing settings, how about a "Pixel perfect" checkbox on the Snap manager, so that all coordinates of new objects, or existing ones without floating point, remain like such until I force them out?
     
    Basically, not letting objects use floating point until I force them to.
     
    I have read reasons why devs find this like a grey area, but maybe this illustrated another solution, or something closer to it. I don't remember how Photoshop handled this (aww, already forgetting it!) but this was never an issue out of the other million issues it did have.
     
    Cheers! :)
  12. Like
    PabloNeirotti got a reaction from A_B_C in Pixel perfect mode   
    Hey there!
     
    I've seen a lot of posts regarding this, but hey, let me put it from my perspective.
     
    Affinity Designer is the fastest workflow I ever had, but gets really slowed down by the fact that it insists on not using round, natural numbers for coordinates and sizes. It's fine for drawing, but for UI design, it is just a chore of every 1 minute going back to what you just did, adjusting the additional 0.3 on this coordinate, remove the 0.5 on that width, etc... The micromanagement is killing me.
     
    I've followed the guides, read all about the snapping, how it works, and so on. But I still get these floating point values on everything I move and create. It just plain doesn't works.
     
    If this mode cannot be accomplished through existing settings, how about a "Pixel perfect" checkbox on the Snap manager, so that all coordinates of new objects, or existing ones without floating point, remain like such until I force them out?
     
    Basically, not letting objects use floating point until I force them to.
     
    I have read reasons why devs find this like a grey area, but maybe this illustrated another solution, or something closer to it. I don't remember how Photoshop handled this (aww, already forgetting it!) but this was never an issue out of the other million issues it did have.
     
    Cheers! :)
  13. Like
    PabloNeirotti got a reaction from ronnyb in Pixel perfect mode   
    Hey there!
     
    I've seen a lot of posts regarding this, but hey, let me put it from my perspective.
     
    Affinity Designer is the fastest workflow I ever had, but gets really slowed down by the fact that it insists on not using round, natural numbers for coordinates and sizes. It's fine for drawing, but for UI design, it is just a chore of every 1 minute going back to what you just did, adjusting the additional 0.3 on this coordinate, remove the 0.5 on that width, etc... The micromanagement is killing me.
     
    I've followed the guides, read all about the snapping, how it works, and so on. But I still get these floating point values on everything I move and create. It just plain doesn't works.
     
    If this mode cannot be accomplished through existing settings, how about a "Pixel perfect" checkbox on the Snap manager, so that all coordinates of new objects, or existing ones without floating point, remain like such until I force them out?
     
    Basically, not letting objects use floating point until I force them to.
     
    I have read reasons why devs find this like a grey area, but maybe this illustrated another solution, or something closer to it. I don't remember how Photoshop handled this (aww, already forgetting it!) but this was never an issue out of the other million issues it did have.
     
    Cheers! :)
×
×
  • 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.