Jump to content

raptor

Members
  • Content count

    37
  • Joined

  • Last visited

About raptor

  • Rank
    Member

Recent Profile Visitors

559 profile views
  1. Hi, maybe these workarounds could help a bit untill this area of a program gets improved (hopefully): https://forum.affinity.serif.com/index.php?/topic/51458-affdes-lockunlock-workarounds-and-tips/
  2. This is just a small tip/warning but it took me a while to figure out what was going on. Since Designer has the Pixel persona one has to be aware that there is the second type of selection - the pixel selection. The first type is obviously the object selection (selection box). If you are working with both types of selections (switching to Pixel persona and back) at one point you may forget to clear the pixel selection (deselect) or you may create the pixel selection accidentaly. And that might cause problems/confusion later on. This happened to me: While in Draw persona I selected a pixel object and noticed that the selection (bounding) box is completely off the object and has a different size: I thought that it had to be some kind of a bug. It took me a while to figure out that it is in fact a forgotten (or accidental) pixel selection. So ultimately Ctrl + d solved this issue. So if something is off with your object selection box or you get any sort of weird behavior alway try Ctrl + d. Maybe this is too obvious but you never know... Anyway I just wanted to share this.
  3. Hi MEB, thanks for the reply. Yeah, it looks like the info about the Pen tool feature is mixed up with info about the Node tool. Thanks for logging it. Recreating the node handles using the Pen tool while holding Shift can be a feasible workaround until (and if) we get something like angle snapping for handles in the future.
  4. Aff. Designer 1.6.4.104 According to the manual I should be able to select a node (via the Node tool) on an already drawn curve and Shift+drag the handle to constrain it to a 45deg intervals. It doesn't work. Shift+drag just slides the handle along the imaginary line defined by the original orientation of the handle. From the manual Drawing curves and shapes > Edit curves and shapes: Is this supposed to work at all? Maybe I just misunderstood the info in the manual. Or is it indeed worded incorrectly? Maybe it should read "The Shift key constrains the node to 45 degree intervals". Then it would make sense.
  5. Thanks a lot, Gabe. I don't understand why it is like that (I would expect the artboard presets to be independent on document resolution) but at least I know how to work around that now. On the other hand it's not a big deal at all. I am planning on doing my own artboard presets anyway (including "CSS pixel resolution").
  6. Aff. Designer 1.6.4.104 Windows Hi, I am confused by the resolutions of the artboard presets. For example why is iPhone 5's artboard size 426.67px x 757.33px? Hardware resolution of the iPhone 5 is 640px x 1136px and "CSS resolution" is 320px x 568px. The size values of the artboard preset are not even whole numbers. Maybe I am missing some crucial information/knowledge here. Can anyone shed some light on this? Thanks.
  7. raptor

    Feather effect on vectors

    I agree. This is one of the basic features that I really miss and makes the Designer incomplete (at least for me). I have been waiting for any sign that this feature is being actively developed (or even considered) for a long time. I know they had this feature in early versions but decided to remove it because they were not satisfied with the results. I guess it is in limbo right now. No mention in a roadmap. If any Serif developer is reading this could you please update us on this? Is it silently being worked on? Is the work on this being considered? Or is it completely in limbo? Thank you.
  8. Hi carl, thanks for the reply. I noticed that too. The documents were not the same size. One document was 2000 x 2400 px and the other was 4000 x 4000 px. I might have accidentally switched to other documents though. I am not 100% sure as far as this switching theory is concerned. It is just guessing. At the time I didn't have time to investigate the bug (I just took quick screenshots) but I will try to reproduce it ASAP.
  9. A. Photo 1.6.2.97 Hi, a strange thing happened to me concerning macros in Affinity Photo. I created a simple macro consisting of 2 steps: 1. duplicate 2. transform ... move +38.8px Screenshot: I saved the macro to the Library and used it on several occasions without any problem. Then after a while it suddenly failed - it gave me totally unexpected result (the object was resized etc.). I checked the settings of the transform item and found out that the program had adjusted some of the settings! I did not touch the settings of the macro at all after I had created it. This is the screenshot of the adjusted/corrupted settings: Note: I was switching between documents and using the macro in both of them. I don't know if it is of any importance but it could be a clue. Maybe the corruption occured after the switch to another document but I am really not sure. I will try to reproduce and record this strange behavior but it may take some time. This thread is likely related to this issue: https://forum.affinity.serif.com/index.php?/topic/53164-macro-records-but-will-not-perform/#comment-268520
  10. raptor

    Scripting

    I also would like to see a scripting support. In my opinion a real professional software should support at the very least scripting and ideally plug-ins/addons. I often keep coming across problems/annoyances that could be solved by scripting. Macros are extremely limited. I also vote for python.
  11. raptor

    Macro Limitations

    I agree. It is even more important considering the programs have no proper scripting support.
  12. Hi Nezumi, if I understand you correctly you want to make a marquee selection on a layer and than crop it. This is my workaround: 1. Make a marquee selection * 2. Invert the selection 3. Delete the selected pixels 4. Deselect I have created a macro (named Crop Layer) from these steps and have it in my Library so I can quickly get to it: * Warning: don't resize the selection once you make it because of this bug (still not fixed ): https://forum.affinity.serif.com/index.php?/topic/37131-aff-photo-transforming-a-selection-causes-it-to-have-soft-edges/
  13. When you click on a macro in your Library palette A. Photo always switches to the View tool (the hand) afterwards. This is really not what I usually want. Almost every time I want to use the Move tool. So every time I use a macro I have to manually press V or click on the Move tool icon. It kind of disrupts the flow. Please make it customizable which tool will be activated after clicking a macro. For example, you could add support for tool switching to the Macro editor (so activating any tool would be registered as a step). Or make the program remember the last active tool before using a macro. Or at the very least change the default automatic switching from View tool to Move tool. Similarly I would prefer the Move tool to be activated after I have created a new document. Now it also defaults to the View tool. I can easily navigate the view with the Move tool but I cannot select and manipulate objects on canvas with the View tool. So the Move tool is much more useful as a default. Thank you.
  14. Definitely this. +1000 I was very surprised not to see HSV(B). There is nothing wrong with it and it is everywhere. For me it is much more intuitive than HSL. HSL is indeed weird. Right now I have to learn HSL because of Affinity instead of just using easy HSV(B) right away. This is what puzzles me: In certain areas Affinity apps just copy Adobe apps (too much) with all the Adobe shortcomings but in this case they totally deviate from the standards and replace HSV(B) with HSL.
  15. I just want to ask whether this issue was worked on or not. When I evaluated the recent version (1.6.0.89) I found out that the issue was still present. I thought that it had already been fixed but then I noticed that it ruined some of my work - luckily it was just some testing/evaluation work.
×