LilleG

Filters and Adjustments respect a selection; Effects and Styles do not. Was that seen as either unworkable, or just not needed or much desired? I haven't found much use for either Effects or Styles on a selection. I was just trying things to see what it would do and what it wouldn't.

I'd be thrilled to have the realistic oils and watercolor brushes of Painter. And of course, just for fun, the Distorto brush. I wind up taking Designer files into either Painter Light (can't afford to upgrade to whatever the latest one is) or ArtRage to add a bit of texture and depth. I'd love to be able to do it all in Affinity Designer and Photo. I don't think it's likely to happen but one can dream.

I didn't know it either. So add my thanks.

+1 This would be such a big help. Way too often I wind up grabbing the node when what I want is a handle. Then I have to drag it back, which often involves a bit of back and forth-ing to get it exactly where it was. Which also involves some muttering of words my grandchildren should not hear.

Sounds like a big improvement. The current eyedropper is needlessly cumbersome. 3 basic steps are all you need. Click on eyedropper, click on desired color, click on placement area. Doesn't the current eyedropper already act as a loupe? Or am I misunderstanding that part of your request?

Yes! There are progress bars for other things but we need one for any time-intensive operation.

Just installed the new 26106 build and opened a NEF in it with no problems. My baby is no longer broken! Thanks, guys, for all the help and comforting. :) :) :)

Woo hoo! The newest Photo Beta just opened a NEF for me! :D :D :D

Sorry, but I think the old ones were much better. There's really nothing in the new ones that indicate what they do. Even Photo's shutter blades are only obvious once it's pointed out. Not all change is good. Especially when it's inconsequential surface appearance. If we have a voice at all, I hope you'll stay with/bring back the old ones.

I just meant no change in the result…that it still crashed with a NEF. And I saw the other thread. Thanks for following up on this.

I am so relieved. I was afraid it was a problem with my machine. Since it isn't, I know it will get fixed. Thanks for letting me know.

I just tried that. No change. This is at the beginning of the crash log, if that helps at all. Application Specific Information: *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[NSColorSpace model]: unrecognized selector sent to instance 0x7faf7acbf550' abort() called terminate called throwing an exception

I'm using a D90 but I've opened NEFs from it before in previous betas. The current Designer Beta has no problem with them. I wish I could remember if I had opened one in 25787 but I've had a number of other things going on and I simply don't.

As a matter of curiosity, where all are Photo Beta prefs stored? I've dragged Affinity Photo Beta to the Trash. Gone to User/Library/Prefs and dragged "com.seriflabs.affinityphoto.beta.LSSharedFileList.plist" to the Trash and deleted both. But when I re-download the newest beta (yes, the previous download was also trashed) and install it, it comes up with my previous non-default preferences in place. Where is it getting them? The reason it might matter is that if MountainLion has screwed up something in the prefs that is preventing Photo Beta from opening NEF files, then a new build is prolly not going to fix anything.

I'm just hoping that ML (which I suspect is the culprit ) hasn't created a permanent problem and the new build will work.

If I try to open any NEF file, Affinity Photo crashes…every time. Affinity Designer Beta can open the same NEF files with no problems. I really don't know if this is a new problem with this build or not. I'm sure I've played with this build but I don't know if I tried to open a NEF or just played around with other formats…TIFF, or PSD. I've reset and restarted the app. Repaired permissions and restarted the Mac. Relaunched the Finder (since that was the problem with the disappearing file icons.) Deleted, downloaded again, and reinstalled the app several times. The only reason I've included a small part of the crash log is because, as it says, it includes Application Specific Information. Well, I thought I was attaching it. And there's no option to do so now.

Ah, another CS3 user. Thought I was the only one still using that ancient but still very capable version.

I'm one of the 70+ users who squints and peers and hunches over the screen in Affinity and other "dark and low contrast" apps and dreams of a UI as easy to read as this forum. The dark UI is lovely but it's a pain to use. There should be a choice of light or dark UI. That way, everyone is happy and productive.

Glad to hear it. Being able to adjust the color makes it so much easier to see.

I tried to replicate it this morning, using the same image with the smallest possible crop selection. I couldn't get it to fail so apparently it was one of those occasional glitches that Mountain Lion seems prone to.

Mouse slipped while dragging the Crop tool which resulted in a teeny tiny area to crop in a large image. Got the spinning beach ball. Tried to back out with Cmd/Z. No effect. Gave it a minute or two then tried Quit. No Effect. Tried Force Quit. The Force Quit window said it was gone and the dock icon lost its open indicator. However, I still had the Affinity Menu Bar, the full workspace and the spinning beach ball with no way to get rid of either of them. Can't Force Quit something the Finder no longer sees. I wound up having to Shut Down my machine to get out of it. It doesn't seem like a situation that would likely occur often, maybe never again, and I didn't lose anything because of it but it seemed like it might be worth reporting. OS: Mountain Lion Photo Beta: 25787

A checkbox in the toolbar would be great.

Thanks, Lee. I was curious about this too. The link, along with others that I Googled yesterday, told me a lot more than I really needed, or wanted, to know about Lanczos but leaves the questions unanswered, except for speed, in relation to Affinity. Within Affinity, which is better? Any opinion on that? TIA

We do have a choice now but I would prefer non-destructive as the default since it is the one I use most.

I think csp was referring to Dan Margulis' books.