Jump to content

thomasp

Members
  • Content Count

    89
  • Joined

  • Last visited

About thomasp

  • Rank
    Member

Profile Information

  • Gender
    Not Telling
  • Location
    Germany

Recent Profile Visitors

597 profile views
  1. Well with an application frame such as the ones Adobe is using (or every app set up like that under the sun, really) you can scale the app to easily fit other windows around it. I don't see the benefit of having the desktop peek through during color critical work - and worse - having the app interface vanish if you happen to click outside a document window by mistake. That is a usability sin IMO. I'm old timer enough to have experienced Photoshop 3 on the SGI which also had this floaty interface. 24 years on I do recall how annoying I found using that. Main point for me though are documents opening half obscured by the interface and the need to resize/zoom documents within the document borders all the time.
  2. Yeah I agree with the OP's thoughts about the separated mode. I use it all day (tabbed interfaces just feel so restrictive) and the daily annoyances in window management are real. I'd also like to see an application frame for separated mode making its debut to block out the desktop background. Using a neutral/dark wallpaper only helps so much I'm afraid.
  3. Phew, well assuming you are using an Intuos Pro or Cintiq (I am not familiar with their other product lines and driver software - if different) then you will be able to configure application-specific profiles and assign keyboard shortcuts to pen and tablet-buttons. A quick test on my end reveals that it's not possible to assign modifier key+mouseclick combinations this way. Therefore I think a way to do it might be to use a freeware app called Karabiner that among other things lets you create shortcuts and macros including mouse buttons, map your desired combination onto a keyboard shortcut and assign that in the Wacom prefs. I imagine something like mapping CTRL + ALT + RMOUSE to a button and holding that down while putting the pen down on the tablet, thus invoking LMOUSE should do the trick? I should point out I haven't tested this myself nor do I use that AP shortcut personally. Oh and: I was referring to the Mac version. If you are asking about Windows there might be other tools - like Autohotkey - to look into to achieve the same thing.
  4. Let me guess: Wacom driver 6.3.38-3 or 39-1 ? These seem to have a problem on mac where the pointer noticeably skips as soon as there's some background CPU activity. Total joke Apparently downgrading to 6.3.37-3 fixes the issue for now.
  5. Long time - but my Mac became unavailable soon after I posted that. I seem to have resolved the issue by installing the latest Wacom driver available for the OS.
  6. Thank you for putting the context help bar into windows in separated mode in this release! Not sure if it was by my request or an item long on your list but such a pleasure to no longer be flying blind. 🥰🥰🥰
  7. Yeah I just compared with another installation of Affinity (different OS version) and there I do not have mouse cursor at all on the canvas with paint tools active. Nice tip with the Wacom drivers, I have 6.3.30-something installed, 2018 era stuff. Will try out over the weekend, just have to do a backup first.
  8. First of all I'm not sure if it's a bug or a wrong preference setting: What happens is that the circle showing brush size only appears during a paint stroke (pen down on Wacom tablet) and with pen up (pen hovering above the drawing area) it show the standard OSX mouse cursor. During normal operations that leads to a situation where the mouse pointer and the brush size preview or any gizmo to interact with layer contents constantly alternate (flicker). I've only recently upgraded my OS from High Sierra to Mojave and also updated AP and AD. I'm absolutely sure that I changed nothing in my preferences and that the behaviour wasn't there in 1.7.3 on High Sierra. It affects both AP and AD 1.8.1 Also it seems to only happen when switching from another application to AP/AD via clicking into its interface (running in separated mode here).
  9. I just installed 181 for both AP and AD and was wondering what ever happened to this feature request? What would be the reason to not wanting to show the user context help in separated mode? I always feel gimped trying to do more involved masks/selections but the default tabbed interface is just too limiting (I always have multiple documents open and want to view them side by side).
  10. Just bumping this to voice my request for scripting features. In particular I dearly miss the ability to load/save/import/export files via shortcut, something the macro recorder does not allow. Also taking the opportunity to ask that if scripting is going to be added then please choose a language that is not locked down to one specific OS and ideally is a standard you can already find lots of resources to learn for. *cough* Python *cough*
  11. One feature I am missing from the Adobe camp is the ability to have the program save documents as a background task, allowing you to work on another document in the meantime. When you have to juggle large documents this is a very welcome ability. With AP in its current state however you have to just sit there and wait for any file save task to finish. I'm rather surprised at a quick glance the forum search did not unearth any earlier made request for this. Am I not using the correct terms? In the same vein I think it would be great to also have the program load in images in the background. Example use case is that you drag a series of large photos onto the program and start working on the first one that finishes loading. Then any subsequently loaded images pop in and steal your focus away. Comments related to 1.7.3's behaviour on the Mac.
  12. Hi Lee, yes indeed I'm running 10.13.6. I'm just curious at this point if this error is indicative of anything serious happening behind the scenes? So far I've not experienced any crashes related to AP.
  13. I noticed that the console on Mac is reporting a lot of these errors (marked red) for me when running Affinity Photo in the foreground: void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): AMDRadeonAccelerator prodding blockFenceInterrupt Only AP seems to trigger them - Designer for example doesn't. Other graphics intensive software using Metal acceleration also seems unaffected. I've seen this error attributed to GPU freezes, hence the curiosity. What's the meaning of it? Happening on D500 GPU's on a 2013 Mac Pro.
  14. As said - play with the spacing parameter: if set too high it creates a patchy brush streak that partially exposes whatever is under the current layer. It'll need to be really low to create a smooth, continuous look.
  15. Not sure what I'm looking at but playing around with the 'Spacing' value in the brush parameters can help if the Smudge tool is not behaving well. I've set mine very low for smudge brushes.
×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.