-
Posts
11,297 -
Joined
-
Last visited
Everything posted by GarryP
-
Your document UOM is millimetres rather than pixels so that might be the first problem. Your curves have stroke widths that are not integer pixel widths so that’s probably the second problem. Your curves have “Align: Centre”, so unless you have stroke widths divisible by 2 pixels, that’s probably another problem. Edit: Also, none of the individual curves (that I have looked at) in the Curves layer are individually aligned to the pixel grid, so that’s probably not helping, but I don’t know what you want to achieve. As for snapping, we can’t see what your snapping settings are so we can’t tell if you are using the correct settings for what you want to do.
-
Zoom In and Zoom Out set to... F15 and F16?
GarryP replied to nezumi's topic in V2 Bugs found on Windows
You might not have seen that I recently edited my earlier post to give extra information about F15/F16 being for tablet zooming on Windows. -
Zoom In and Zoom Out set to... F15 and F16?
GarryP replied to nezumi's topic in V2 Bugs found on Windows
I see the same shortcuts (F15 for “Zoom In” and F16 for “Zoom Out”) in the Photo/Miscellaneous section of the Shortcuts but, in the “View → Zoom” menu I see “Zoom In” is Ctrl+= (equivalent to Ctrl++) and “Zoom Out” is Ctrl+- However, in the Photo/View section of the Shortcuts there is a “Zoom → Zoom In”, set to Ctrl+= and a “Zoom → Zoom Out” set to Ctrl+- I’m wondering what the difference is between the “View” Zoom In/Out and the “Miscellaneous” Zoom In/Out. Edit: Ah, I’ve just found out that F15 & F16 were added for tablet zooming on Windows: https://forum.affinity.serif.com/index.php?/topic/138904-affinity-publisher-for-macos-192/ Maybe those options in Miscellaneous should be renamed to “Tablet Zoom In” and “Tablet Zoom Out” to make that clear. So this looks like it’s not a bug, as such, but rather some confusingly-named options. -
Grabbing a Skew handle_EDIT
GarryP replied to evtonic3's topic in Affinity on Desktop Questions (macOS and Windows)
I don’t use the skew functionality via the layer handles very much, but when I do it seems to work fine for me. When you say that it doesn’t let you grab it easily, does that mean the mouse pointer changes from the ‘skew pointer’ before you have a chance to use it or, when the ‘skew pointer’ is there you cannot perform the drag action, or something else? Would you be able to upload a video of the problem so we can see what’s happening? -
Grabbing a Skew handle_EDIT
GarryP replied to evtonic3's topic in Affinity on Desktop Questions (macOS and Windows)
I can’t see what the original problem was, because it’s gone now, but it might have been more useful if you had kept the original problem intact and added a post explaining what the solution was, so that other people might be able to benefit if they have the same problem and search the forums for it. There are all kinds of ‘odd’ problems that have simple ‘fixes’ which aren’t mentioned in the documentation and it’s good to have them in the forums for people to find. Even when the problem was simply that we did the wrong thing or had the wrong idea about something, we probably won’t be the only one who makes that mistake so telling people about it could help someone who is ‘in the same boat’. -
If you keep any (non-trivial) software open for long periods of time there can often be a tendency for it to ‘bloat’ with various cached items, and similar, taking up memory as things are ‘kept close’ for quick use. That’s not to mention memory leaks which can cause an application to ‘accidentally’ grow in memory use (and I’m not saying that is the case here). Have you tried closing Publisher and then launching it again? I would usually recommend closing most applications at least once a day, if possible, to help to ‘keep things fresh’. Just for comparison, Publisher 1.10.6, on Windows, after launch, with no open documents, should use about 420MB of memory, maybe a bit less, maybe a bit more, depending on fonts etc. Try launching Publisher, without opening any documents, and leaving it for five minutes or so. If, by then, it is taking up more than 500MB of memory then you might need to look at figuring out how to reduce that footprint, and someone can probably help you with that.
-
To try and give a bit more detail to what Kasper-V has already said above… The sundial is in Derbyshire, England, which is in the Northern Hemisphere. (I am assuming that the sundial is installed in the place where it was designed to be used, and not taken from elsewhere.) The thread title tells us that the sundial is vertically-mounted, rather than horizontal. In order for it to be usable we can also assume that it was installed on a south-facing wall (or similar), since it is in the Northern Hemisphere, otherwise the sunlight wouldn’t fall directly on it and, therefore, the sundial wouldn’t be easy to read. Since the Sun rises in the East, and the sundial is in the Northern Hemisphere, and we are looking towards the North when reading the sundial, the sunlight will first hit the sundial, at dawn, at a low angle just above the horizon to the East (on our right), which will cast a shadow on the sundial on the left, e.g. near the 7 A.M. position. The Sun will then continue to move West, and behind us, with the shadow angling further ‘down’ and to our right moving towards midday (12) at the bottom of the sundial. After midday the Sun will continue moving West with the shadow angling further ‘up’ and to our right towards the 6 P.M. position after which the Sun eventually goes down on the Western horizon. I hope that helps.
-
Clicking outside a selection to deselect
GarryP replied to mxm's topic in Feedback for the Affinity V2 Suite of Products
That would make sense because of the way that tool works, that and the Flood Select Tool. I’ve amended my earlier post to mention these. -
Clicking outside a selection to deselect
GarryP replied to mxm's topic in Feedback for the Affinity V2 Suite of Products
Unless I have totally misunderstood what you have written, the existing functionality already lets you do what you want. See my attached video where I make a selection with the Freehand Selection Tool to make a pixel selection and then click somewhere which isn’t part of the selection to cancel the pixel selection. The same 'deselection by clicking outside of the selection' technique can be achieved in all of the Selection Tools that I have tried. Edit: The same 'deselection by clicking outside of the selection' technique can be achieved in most of the Selection Tools except the Selection Brush Tool and the Flood Select Tool and the difference comes about because of how those particular tools work. If that’s not working for you then we will need to see a video of what you are doing. 2024-01-26 08-45-25.mp4 -
What is this grid
GarryP replied to mckeeld's topic in Affinity on Desktop Questions (macOS and Windows)
It might help others who have encountered the same issue, and have found this thread, to know what it was and how to remove it. -
The Affinity applications have no keyboard shortcut search facility, although one has been requested a few times, .e.g: https://forum.affinity.serif.com/index.php?/topic/194638-search-engine-in-keyboard-shortcuts/ The one you are looking for, in case anyone else wants to know, can be found in <application>/Layer/Convert to Curves, see attached image.
-
Image frame properties as studio panel
GarryP replied to Intuos5's topic in Feedback for the Affinity V2 Suite of Products
As an alternative to the original suggestion, to reduce the number of panels, how about putting the icons from that pop-up to the left and right of the zoom slider, as in my attached (crudely-done) mock-up? (The icons could still be available when the child image was selected.) I don’t know how the Anchor control would fit into this, maybe a pop-up icon to the right of the others, but it might be better than having another panel to organise as this sort of thing will only ever be needed when manipulating Picture Frames (or have I forgotten something?).- 3 replies
-
- affinity publisher
- image
- (and 6 more)
-
I believe that the developers very much understand the requirement that some users have to be able to change the UI font size – some of the developers would probably like to be able to do it themselves if they use higher-resolution screens. But the knowledge of a greater need for something doesn’t necessarily equate to that thing being given a higher priority, perhaps because of other internal/external pressures that we either know about or don’t know about. Basically, Serif do their thing how they do it and some stuff gets done and other stuff has to wait. As I said above: And that’s just how it is.
-
Serif usually don’t comment on possible changes or timescales for possible changes. If something gets changed then it’s usually mentioned in the beta forums https://forum.affinity.serif.com/index.php?/forum/32-beta-software-forums/ and that’s when we users get to know about things prior to the commercial updates. As you already know, this is something which has been requested many times and Serif are aware of those requests. All we users can do is wait and see if anything happens.
-
If using the Undo is no longer a possibility then there’s no way to turn the curves back into text because the software has no way of knowing which fonts (can be multiple fonts used in one frame) were used to create the text in the first place. A curve is just a curve. The History Panel, as with most other panels, can be shown via the Window menu, e.g. menu “Window → History”.
-
Is this issue related to the title: “Pointer will not change to reflect the tool in use”, or the text in the post itself: “you cant see very clearly the edge of the tool”, or both? Those seem to be different issues to me so it might be useful if you can explain some details. Also, if you can give us a full-screen screenshot or video which shows the issue then that might help us to see the problem.
-
Clicking outside a selection to deselect
GarryP replied to mxm's topic in Feedback for the Affinity V2 Suite of Products
I thought they might be selecting layers until I re-read the text and noticed that they said “any selection tool” which kinda gave me the idea that it might be pixel selection instead. Once we find out what they’re doing we will have a better idea of where to go next. -
Layer names not preserved when exporting Designer to pdf
GarryP replied to Caden's topic in V1 Bugs found on Windows
Welcome to the forums @Caden I just opened your AFDESIGN document in Designer 1.10.6, exported it to a PDF 1.6 (with Include Layers set to ON) and the Layer is named correctly as far as I can see in Acrobat – see attached image. There’s a chance that the website you are uploading the PDF to isn’t working properly, or it needs certain things to be certain ways, but we can’t know that as we don’t know which website you are using. There’s also a chance that the website is rejecting PDFs that have not been created in Adobe applications, I’ve heard of that happening before. If that’s the case then you might not be able to do much about it. -
Clicking outside a selection to deselect
GarryP replied to mxm's topic in Feedback for the Affinity V2 Suite of Products
@mxm Are you talking about layer selection or pixel selection? Also, which Affinity application(s) are you referring to? Since you mention “any selection tool” (my emphasis) I am going to assume that you mean pixel selection (either in Photo, or the Photo Persona or Publisher, or the Pixel Persona of Designer) as there are more pixel selection tools than layer selection tools. With the pixel selection tools, the functionality you want is already there, as mentioned by Hangman above: click on an area outside of the current pixel selection and the pixel selection will be deselected. This should happen no matter which Mode the pixel selection tool is in. If none of the responses in this thread have covered the issue you have brought up then you might need to show us a screen recording of what you are trying to do so we can understand it better. -
Thanks for supplying the video. Unless I’m missing something important from the video, I believe the problem you are having could be because you have "Select object when intersects with the selection marquee" switched ON. When that option is switched ON, if you marquee drag across the ‘face’ of a layer, the marquee is intersecting the boundary rectangle of the unfilled layer (it’s actually totally within the boundary rectangle, which counts as an intersection) and therefore the unfilled layer is being selected. Have you tried switching that option OFF and seeing if you can do what you want to do?