Jump to content

Jeff C

Members
  • Content count

    17
  • Joined

  • Last visited

About Jeff C

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @swenpaylay The reality, whether with Serif or any other developer, is that not every bug is caught before release. That's not because of bad testing programs, it's just the nature of software development that you can not catch every bug 100% of the time. This is precisely why you shouldn't upgrade applications you rely on until those new releases have been in the wild for a little while. Surely, if you used Adobe in the past, you were very used to this. I don't know any creative professional (myself included) using Adobe's stuff that upgrades their primary device as soon as a new release comes out. They wait until it's been out there for a little while, and and usually only upgrade one release behind the current. Bugs are an inescapable part of software, and just like you wouldn't upgrade your OS on the same day you have a deadline to meet, you shouldn't be upgrading apps you rely on until you have some room to rollback if things don't go well. Turn off your auto-updates. And if the bug is such an issue that you can't work at all with that version, then FFS join the beta program to get the fixed release early, or downgrade to a previous version. You have options, you just don't seem to want to use them. So if you feel like there is a lack of sympathy here, maybe that's why. Or you can just stay angry I guess, but that doesn't help you, or Serif, or anyone else.
  2. No kidding. And they know that, obviously. Surely you’re not saying you want Serif to push out a release that hasn’t been fully tested yet... right? That’s what beta is for. It’s part of a perfectly normal software development process. They’re saying if you can’t wait for the actual release, then beta might be an option for you. That’s not hostile toward users - it’s the opposite. There’s no need to excoriate Serif for that. The real hostility I see is in your comment, and it’s unwarranted.
  3. If you're using a textured screen protector (e.g. the one from PaperLike [dot] com) even a plastic ruler can scratch it all up. Or a bigger problem is that holding a ruler on the screen often means you're touching the screen in at least one other place, which isn't caught by palm rejection and therefore causes issues with drawing the straight line with the pencil. Other apps handle this by having a tap-and-hold gesture to get the equivalent of using Shift on a keyboard. That's really what we're looking for.
  4. That's mostly what I do now.
  5. It would be super useful to have font presets so that we could save certain reusable font styles & sizes for quick access between documents. If I’m lettering a comic page, for example, and close that file to work on the next page, I need to reset my current font, size, and style instead of continuing with what I was using previously. It’s cumbersome to have to reset the size, leading, and font face each time I switch files.
  6. Thanks for your time on this, MEB. For others reading this thread later, I think a workaround for now seems to be turning off "Edit All Layers" in the menu within the Layers palette. So far, that seems to help prevent accidentally selecting the bottom, locked, layer while drawing.
  7. Agreeing with owenr above. If locking a layer doesn’t completely prevent editing, then I wouldn’t consider it a lock at all. It’s actually very important to be able to protect layers like this. When painting or drawing, it’s very easy to find yourself working on the wrong layer. If you’ve done so for 30 minutes and are beyond the undo limit, the piece can be ruined.
  8. Ok, thanks. That deliberate selection makes a bit more sense I suppose. The issue Chris_K is referring to (and which is apparently causing the bug I started this thread with) is that in iPad those locked layers are getting selected without deliberately selecting them in the Layers Palette. So what's happening is that I'm drawing and realize, after some time, that all of my lines are on the wrong layer - the locked layer that I did not select.
  9. Thanks MEB So the intended behavior is that you can edit a locked layer so long as you select it first in the Layer Studio? And the known-issue described above by Chris_K is what is causing me to (accidentally) select that layer and therefore edit it. Is that correct? Without that known issue of being able to select locked pixel layers, I think it's really odd that one can edit a locked layer at all. In all other programs I've used or as long as I can remember, locking a layer protects it from edits of any kind. And while I realize that Affinity is doing a lot of things differently (which I love), I think that one is counter-intuitive and will be hard to relearn for people like myself migrating from other apps. I'm not sure I see the benefit of only locking selection and transformation and not edits.
  10. Hi Chris, thanks for the quick reply. Yes, this is always with pixel layers. If I understand correctly, you are saying that it is intentional that locked layers can still be edited (drawn on, painted on). Is that correct? If so, that seems like a really strange behavior for the lock feature and is the opposite of what one would expect when locking a layer.
  11. This is on an iPad Pro. I usually lock the bottom-most layer as my background. And after drawing or painting a bit on new layers, I often find that Designer has shifted focus to that bottom locked layer and put my paint/drawing on it even though it's locked.
  12. Cool. Thanks for the confirmation, Sean.
  13. In Designer, any guides I’ve created disappear when I change to the pixel persona, or when I select a pixel pencil or pen tool. If I go to the menu and select Guides, they come back, but disappear again as soon as I choose pen or pencil tool.
  14. Jeff C

    Guides

    July now, and I’m seeing this on Designer for iPad. I can’t use guides at all on pixel layers with pencil or brush tools.
×