matisso

I don’t know, man. Maybe the wording of the other thread wasn’t clear enough. Maybe it just was added to a staff’s blacklist of some sort, because they don’t seem to give a flying f… about it whatsoever. Probably frustration and apparently a futile hope that a fresh start on it will get at least any response from them. Are you talking about Alt/Opt+dragging? Yes, it doesn’t change adjacent segments but comes with instant cusp nodes. Doesn’t exactly help to keep the flow of your curve. We’re talking about constraining control handles’ angles whilst dragging. PS. I recently noticed, that a (really useful, BTW) Illustrator plugin, InkScribe, offers one of the options that @JET_Affinity was mentioning, i.e. a modifier that locks the the adjacent handles to their original angles when dragging a segment.

That was clearly supposed to say “within Adobe environment” – it’s a busy day. Thanks for an extensive answer. Personally I started to learn all the stuff somewhere in the late 90s so Freehand was already becoming outdated at that time and Macromedia weren’t interested in developing it – or I just didn’t bother. That just goes to show there are even more ways to approach the process. Fingers crossed this thread will spark some reaction instead of ending up as yet another idle talk. regards, Matt

So, @MEB, is there any chance the staff at least reacts in any way? A simple reply would suffice, like “it’s planned at some point” or “we think this should work this way and consider this a complete feature” or anything that makes any sense. It really sucks to feel ignored as a customer. Provided you have worked within Adobe, I wonder – have you ever needed to alter this setting right in the middle of editing an object? Hey, that sounds like even more advanced way to do this. Cool idea! While there are two main approaches to the issue (and I’m at least happy that Adobe incorporates both of these) I don’t think there’s currently a tool that is able to freely merge them like this.

Probably, although I personally strongly prefer the one that is currently missing in Affinity. Current Photoshop has had a ‘Constrain Path Dragging’ toggle since a few versions back, which does exactly what we’re talking about. The moment they introduced the alternate behaviour I immediately toggled the thing on and never looked back… There is no keyboard modifier, you either use this mode or another, which of course can be toggled any moment, mid-editing. In my opinion it’s the best way from a user experience point since it forces no one to use an extra modifier to have the tool work the way he or she prefers.

Hello, Could you guys please work on improving / adding extra functionality to a node tool? I’m talking about segment dragging, which currently affects adjacent nodes’ orientation. If you draw something with a pen tool usually you get the angle more or less right, it’s the curvature that’s the most tricky part. The easiest way is to grab a segment to tune the shape but when neighbouring nodes change angles, that doesn’t make any sense. Font editing apps as well as Adobe apps maintain node angle during editing – so that segment dragging doesn’t become “editing a segment and the two adjacent ones”. I know that you can press Shift to keep node’s angle when dragging its handle, but you’re editing just a half of the segment this way. It’s nowhere near as comfortable as being able to drag a segment and alter its overall curvature. It’s particularly indispensable for work on logos, lettering, etc. There could be a keyboard modifier for altering this behaviour (as I am sure some people are comfortable with it) or preferably a toggle button. This has already been discussed here, but nothing happened in five years. @Ben, @MattP is there any work being done on it, or is this request dismissed?

That’s because they’re bitmap based, not vector (I know, weird for a primarily vector app). If you zoom in really close you will see all the fuzziness in its full glory. If you want true vector brushes, use a different app. I’m also waiting for Affinity to do it the right way…

Just a quick sidetrack, if you please: is there any work being done towards a DAM solution that would be useful for batch working with RAW files and also be able to save the edits to a separate sidecar files, or database? Currently, developing pictures one by one and also making it a one shot process with no option to go back and change develop settings make Photo useless for any extensive shooting session. You must rely on third party app for an efficient RAW workflow.

That’s pretty odd, I would assume this would happen in rather poorly designed fonts. Maybe the reason is somewhere else, or maybe the ones you mentioned do have bugs (not entirely impossible). However, given how popular Minion, Tahoma and Myriad are, it’s hard to assume no one else noticed it before using software other than Affinity, so maybe there’s indeed a glitch…

Does it persist if you change the font? Perhaps something has been overlooked in the font file itself.

Since you haven’t provided any example, I assume that would be, for instance, turning black cloth to white? In this case, like @Old Bruce said, masks and adjustments. But that may be a tricky one to nail. Light will bounce quite differently against black than white (so shadows in the original picture will look different that they would have if the object was truly white) and even if you manage to make it white, making it realistic and convincing will requite you to go quite the extra mile with additional adjustments and possibly some manual editing. There’s no easy way of doing it, I’m afraid. 16-bit file would be very good for that kind of manipulation since adjustments will be rather intensive and you’re likely to run into banding when doing such stuff in 8 bits. regards, Matt

So, over a year and a half have passed since this issue had been raised, may I ask how is this rolling? regards, Matt

+1 Definitely a must.

Sorry for being harsh here… My personal opinion – you'd better give up using Photo for RAW development and use anything else. Seriously. Issue #1, which IMO is serious enough on its own to neglect any others – no sidecar files saved with the development settings, making each of your development a one time better-do-it-right attempt. Such workflow (with external settings), obviously, is incredibly useful if you want to revisit your photo for various reasons – e.g. because the engine got updated and you might try and compare how it performs. Or you simply might want a different version of your photo – going back to RAW is as lossless as it can be, compared to adjusting the developed photo. I’ve used several RAW processors and most of them adapt this approach. If not, they keep an internal database of the settings, but nobody but Affinity thought it would be a great idea to make your settings go pooof when you hit the “Develop” button. Yes, there are presets, but this isn’t a realistic choice, you won’t be saving a preset for each photo. Issue #2 – if the rant above still keeps you from changing your mind about AP for RAW files, try moving the “Blackpoint” slider and watch your blacks go clipping in no time. It’s a really cruel joke. Now there are some nice things in it, particularly the option of making additional, localized adjustments by means of masks aka overlays, which can be prepared using advanced selecting and masking features that AP has (although it has its own faults, you can’t adjust all of the parameters when using an overlay, unlike in Lightroom). But it’s a small gain compared to the fundamental flaws this engine has. Move along and save yourself some frustration. Cheers, Matt

Hello, Today I needed such a simple drawn shape and thought I would do it in Designer, since I convinced my employee to buy a licence. However I ran into a strange and annoying bug – merely upon changing zoom level, the brushed stroke changes its appearance. I have included the link to an animated gif that shows the shape at 75, 100, 150 and 200% zoom and a source file as well. What’s even more frustrating, I actually discovered it after i had exported the PNG file at twice the resolution and found out it the stroke changed in it. Try opening the attached .afdesign file (Windows 10 at my end here at work) and clicking Ctrl + + and Ctrl + - and see the stroke going “alive”. Please see this: https://imgur.com/a/8F7DUB5 Regards, Matt brush-bug.afdesign

Good call. I was also lost many times the same way but somehow never thought of actually making a thread. cheers, Matt