GripsholmLion
-
Posts
100 -
Joined
-
Last visited
Posts posted by GripsholmLion
-
-
I was having trouble with cropping one particular image in Photo 2.3.1. I just got what you see in this video. I couldn't stop it from cropping from the top left corner, regardless of ratio, constraint, etc. I tried unlocking the layer, duplicating the layer, and so on. Other images can be cropped as normal.
I ended up pasting it into a new document and got on with my day, but I would love to know the cause because I have never seen this oddity before.
-
Fair point. We can still multi-select within an expanded group and then apply it once – but that does become inconvenient with larger, or especially with nested, groups. I think that it may just be configured this way to reduce misunderstanding or oversight with mixed object types in one group.
-
-
-
Which is precisely why that trope is so unconstructive.
-
Ah, the old trope of "works fine for me". The subtext of which, whether intended or not, is that the problem is somehow the reporter's fault.
I have recently experienced the first three of the above strange behaviours. Seeing the window under the OS menu bar occurred the other day and was definitely a "what the heck?!" moment – it is just as well that the draggable area is large enough to remain visible. The second oddity sometimes happens to me at random; today, it occurred after installing the 2.3.1 update. The third oddity I have not actually seen for some while; it has probably happened only once or twice in several years so I assumed that it had long since been addressed.
Incidentally, the traffic lights still refuse to show their icons when hovered.
-
I came here to report this cropping problem, so here is my example. It seems to be even worse at some angles than the previous example.
-
I really do not see the need to quote a post directly above your response. It is a very irritating habit of a lot of people on this forum. But since you did, you should note the wording of the sentence which you quoted.
I am well aware that files need an extension (I didn't fall down in the last rainfall and I have used Macs for two decades).
The point which I made (apparently not plainly enough) was that the suggested setting in Affinity appeared as though it may be analogous to the tick box in Finder's file info pane, which as we know determines the extension's visibility, and may therefore not be related to the OP's query.
As I described, my assumption was wrong because enabling that preference in Affinity did not change anything in file output. Extensions remained visible with this setting enabled (and the Finder preference disabled so that it would not override whatever Affinity did), which left me wondering what its actual function is.
Note, too, that I already suggested, albeit initially doubtfully, the Finder preference and I later had the chance to establish (see edit) that it fixes the OP's complaint about the Save dialogue. I'll be leaving it ticked for the same reason.
-
I assume from Walt's comment that this post was originally misplaced somewhere and an admin moved it into its own thread.
Anyway, +100 votes for this suggestion. One which I had been intending to make for ages and never got around to.
I tend to work in a "folder first" sort of way, if that makes sense, and my projects are always tightly organised (with which Hazel really helps, incidentally, for other Mac users reading this) and so it just makes no sense at all that I cannot drag and drop a folder onto [for example] the New Focus Stack dialogue box.
-
I can really appreciate your frustration, but do you not have a dedicated RAW converter? Any decent RAW converter should have functions such as adjusting multiple selected photos at once, copy-pasting adjustments from one to multiple other photos, creating presets from your adjustments, etc. As I do quite a lot of macro focus stacking and panoramas, I would rule out any RAW converter which lacked these functions.
-
@walt.farrell You may have misunderstood, I'm not sure. As I indicated in the first part, I can see the same phenomenon as the OP has, but I believe it to be intended behaviour and probably unalterable. A bit annoying, certainly, but probably more of a MacOS characteristic given that other applications behave the same.
The only possible setting which may alter that display behaviour in apps (I have not tested it yet) is the preference in Finder, as I mentioned above.My last comment from which you quoted was about exporting two files to test what effect the preference which you mentioned may have, as I was curious about what it actually does. Possibly no effect at all, as it turns out; or at least it did not do what I expected (as I outlined) which was to save one file with a visible extension and one hidden. Nor did it have any effect on the OP's compaint, though I did not expect it to, to be fair.
Addendum: I have tried changing that Finder pref and (for me at least, on Monterey) it did change the app behaviour so that Save dialogues showed the file extension. So @Ludwig Sonntag this may be your answer, as long as you don't mind its quirks; by "all" extensions, Apple isn't joking. Even app names in Spotlight are appended with ".app", quite pointlessly.
-
I don't much like this behaviour, either. However, since other applications exhibit the same, it is probably just following an Apple guideline.
You may find a different result if you enable the Finder preference to show all filename extensions, but as that is not actually needed for useful extensions to be shown anyway, I always keep it disabled and I have not tested for any difference.
@walt.farrell Oddly that Affinity preference appears to have no discernible effect for me. I had assumed that it influences the file output, analogous to the option in my screen grab below (part of the MacOS file info window), but I just A/B tested it and both of my test exports had their extension visible.
-
Just to be clear, I'm not about to support this suggestion if it would cause new problems, but...
I find that the need to drag the pipette* around means that the ability to sample externally has very limited utility because I cannot find a way to get the pointer to anywhere useful. Dragging prevents or interferes with a lot of navigational actions, including: triggering a hot corner (cannot trigger it); swiping between desktop workspaces (the sampler is lost); pressing the mission control key (ditto); and keyboard shortcuts. So it seems that to sample from another window, I have to do some prep: move Affinity out of fullscreen, ensure that the target window is in the same workspace, and place it in a reachable position.
What a faff. So if the target is not an Affinity-compatible file, I use one of the many third-party colour tools for MacOS which do not require dragging and therefore give their sampler easy access to any window or workspace. I venture to suggest that as a workaround.
*Which, incidentally, looks more like a chicken drumstick in the 2.x redesign.
-
-
-
I have always disliked this waste of valuable space. Zoom to fit... and it doesn't actually fit. Not funny when my most used screen is 13".
Interestingly, the wasted space in your example is, proportionally, not quite as bad as what I typically experience. I don't why that should be.
@MikeTO It centres OK for me, so that's an interesting quirk. Maybe it is down to different scrollbar view settings (mine is set to "when scrolling").
-
I think that such a change would impact many other users' ways of working and cause a great deal of annoyance. It certainly would for me at least, so I can only give my point of view.
A new option would, of course, be completely acceptable to all, but it is just my impression that Serif is not hugely enthusiastic about adding more preferences. Otherwise, I can think of a couple which I would request.
A keyboard shortcut to de-link would be handy here, I think. Type the first value; type shortcut; enter; job done.
In your case, as it stands, I think that I change in methodology is your only option. Perhaps crop to the print ratio if it matters which part of the photo is lost; or just resize to the shortest edge [I think] if it does not matter.
-
Can someone brighter than me tell me whether there is any situation in which using those corrective brush tools on a new empty layer would not require "current layer and below" for sampling?
I cannot think of one, so I am rather curious...
If there is no such scenario, could the assistant automatically enable that option for us when we create an empty layer and select a relevant tool which requires it?
It seems so obvious that I feel as though I am missing something; which would not be a first.
-
Rather annoying isn't it?
I was going to suggest that translucent colours should have a chequerboard background to make them clearly visible against the dark grey; obviously translucent rather than a visually similar opaque colour; and far more representative of the selected values. Or at least make the contextual toolbar and the colour palette consistent when using translucent values.
However, as it is closely related to your view, perhaps the developers will take just as much (or as little?) heed of it here.
-
I am not sure that this is a new issue. The extent to which it occurs may vary, but I have routinely experienced some delay with [probably] all versions of Affinity and on all Macs on which I have ever used it. As it is usually only slight, I have lived with it.
-
Would that be better than the Bake Appearance button?
-
I don't quite understand some aspects of your request. By "without a mouse", do you mean that you can't access this context menu with your Macbook's touchpad either? I found that a two-finger tap in the right places brought up that context menu as I would expect. But, of course, our touchpad settings may be different.
I was not aware that control-clicking has a purpose other than as a modifier for certain tools (and as a left-hander, I am very glad indeed that I don't need to use it often); so I can't say that I would notice if it didn't function.
As you have mentioned clicking, I assume that you use either the touchpad or another pointing device, but please accept my apologies for any misunderstanding.
By "hamburger to access the menu" I am not at all sure what you mean.
-
I was just musing on Bruce's comment about decimal point precision.
-
I often need to work to 1/100ths of mm, but for that I will obviously have the whole document set out in mm. I've probably never used more than three decimal places. But if Pšenda has a need for that much pixel precision, then I can appreciate how it would get awkward if the values are partly hidden.
The crop tool doesn't like this image (Photo on MacOS)
in Affinity on Desktop Questions (macOS and Windows)
Posted
Well, well. it seems that you are right. I wonder why this one image can consistently trigger it (it did it again when I tried your advice) when no other ever has (that I can recall).
Thanks.