Jump to content
You must now use your email address to sign in [click for more info] ×

GripsholmLion

Members
  • Posts

    100
  • Joined

  • Last visited

Posts posted by GripsholmLion

  1. Can I just check that "Command B" was just a typing error and you know that it's just B to select the brush tool? I'm sure that you know that, but really I cannot think of any other possible cause than thinking that you have selected the brush and not realising. I know that you said that it works in 1.x, but I'm having to clutch at straws here! I tried hard to replicate the problem on my Macs, but couldn't.

  2. I can appreciate from your video why you are raising this point.

    However, I cannot replicate the problem except on one occasion by making an error when I moved the selection itself immediately after duplicating its content; this prevented me from subsequently using the pick tool (V) to move said content until I disabled the selection (CMD D). That may be a bug or intended behaviour (ie. not allowing me to work outside of the selection); I am not sure.

    However; if I follow this procedure, I cannot induce this problem at all. I was unable to record a video, so I will list my exact steps:

    1. Made a selection from a photo in AP
    2. Duplicated its content with either CMD J or copy/paste
    3. Selected the pick tool by hand or with V
    4. Moved the pasted object
    5. Finally, disabled the selection with CMD D

    I have repeated this several times and, as long as I did not move the selection, I could move the new content regardless of whether the selection was still active.

  3. You really want either the current or both behaviours. I assume that the current behaviour was intended to favour the application of subtle effects without accidentally over doing them with an overlapping stroke. For instance, if you want to brush in some effect with consistent translucent opacity, the current behaviour prevents overlapping strokes from doubling that opacity.

    To me, this makes much more sense as a safe and usable default if there is no option for any other behaviour. That said, there probably should be a tick-box option on the context bar to enable over-painting in one stroke for times when it is desirable. I played with the settings a little bit, but flow appears not to be a substitute for this.

  4. If you mean the option in the accessibility page of system preferences, no other application which I have ever used needs that in order to tab through such UI elements. The option on the Shortcuts tab of the Keyboard page, "Use keyboard navigation to move focus between controls", is normally sufficient. And if the accessibility setting is needed for Affinity, why does tabbing work correctly in many other parts of the UI, such as the values in the transform palette?

  5. 35 minutes ago, hdcel said:

    It's much easier to control the brush for the blur on certain areas.

    Is it though? If you can control that brush, you can control a brush on a mask just as easily.

    It is not as easy to see where exactly it has been applied with this method as it is with a mask; and it is not as flexible as the already-suggested filter and mask.

    What you seem to be asking is "why can't I hammer this screw in; I don't want to use a screwdriver."

  6. You may have misinterpreted the point which I was making with that particular word: I intimated that if InDesign focusses in on whatever happens to be selected during a zoom, it (the software) is presuming that the user wants to see that object more closely, despite the fact that there are many occasions on which I would be looking closely at some other layer object which happens not to be selected. I wouldn't wish to have always to preselect the "right" layer just because the software is trying to be overly intelligent in its handling of zoom. That is what the zoom tool is there for.

    1 hour ago, artmischke said:

    As a mac user there is no touch screen - so no pinch zoom with 2 fingers... just a keyboard and a mouse

    I am a Mac user, as you can guess, but I can assure you that I have pinch-zoom available on all of my touch pads. It does not require a touch screen. So it is incorrect to state wholesale that Mac users do not have pinch-zoom.

  7. That bit confused me a tad, too, but I'm guessing that he/she is describing the different behaviours between zooming with Command + and the zoom tool (see the OP's second post). I have gaps in my knowledge about that tool, as I remove it from the toolbar and have probably used it only once.

    But I think that @artmischke doesn't like the behaviour of Cmd + (which always keeps the image still while zooming in/out). I must admit to a lack of sympathy for that position, however, because I like it that way and I think that it's logical behaviour.

    Perhaps, having a particular object selected may indicate that the user actually wants to zoom in on that, but this would be expecting the software to read our intention. What if I intended to zoom on some other object which is not selected?

    It really isn't practicable for Cmd + to do anything other than maintain the current position of the image while zooming in/out. If InDesign behaves otherwise, then perhaps it's being a bit presumptuous.😁

    For zooming on to a particular part of an image, I just pinch-zoom and two-finger swipe. However, (just surmising here) if artmischke uses a Magic Mouse, this is not an option (even though it really should be) because its swiping surface doesn't support pinch-zoom (or not in my version at least).

  8. It slightly annoys me, too.

    A computer program may consider it to be modified, but if I haven't actually edited, added, or removed anything, I don't. Computer logic versus human intuition, I suppose.

    It could be fixed by a preference: (1) ask whether to save (default) or (2) suppress the prompt and discard changes on closure. I would use that option if it existed anyway.

    In the case of getting a selection from another image, it may be just as well to place it and make the selection in situ.

  9. On 11/19/2022 at 11:18 PM, Ian69 said:

    I had very long start-ups on my intel-based MacBook Pro and iMac - around 30 seconds - with previous Affinity apps purchased though the Mac App Store. I’ve just upgraded to the version 2.0 apps, and have used this as an opportunity to switch to downloading directly from Serif. Huge difference - two bounces, then a two second pause, and they’re open. Finally working how they should be 😄

    That is my experience, too. Although 30 secs would have been quite acceptable...

    After reading [wading?] through much of this thread in January, I opted to buy directly. Whether the difference is entirely the result of that or partly some performance improvements as well, I can't say, but I have experienced a reduction in the region of 45 seconds in all cases.

×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.