Jump to content


  • Content Count

  • Joined

  • Last visited

  1. Here the system overview and the file. The computer is very busy until I cancel the development. System Software Overview: System Version: macOS 10.14.6 (18G4032) Kernel Version: Darwin 18.7.0 Boot Volume: Macintosh HD Boot Mode: Normal Username: Christoph (christoph) Secure Virtual Memory: Enabled System Integrity Protection: Enabled Hardware Overview: Model Name: MacBook Pro Model Identifier: MacBookPro11,4 Processor Name: Intel Core i7 Processor Speed: 2,2 GHz Number of Processors: 1 Total Number of Cores: 4 L2 Cache (per Core): 256 KB L3 Cache: 6 MB Hyper-Threading Technology: Enabled Memory: 16 GB Boot ROM Version: SMC Version (system): 2.29f24 Serial Number (system): C02RL0JPG8WN Hardware UUID: 80965D9C-DB9F-5A94-8DC1-CD58BB17A86B P1020064.RW2
  2. I opened a raw file taken with my lumix DMC-GX8. The picture appears for a short moment and after this it is displayed as if the opacity would be 0%. When moving any slider, the picture appears, but after the move it disappears again. Disabling metal resolves the issue.
  3. Hi Leigh, please reread the question again. If you have only a little bit of understanding what masks are used for, you will find, that you didn't answer it at all. What was asked for is some meaningful way to EDIT existing masks. If you edit masks you get a black and white picture of the mask. If you are not able to see your photo, there is no meaning in this functionality. That is editing blindfolded. To make it useful the edit mask should be displayed as overlay to the photo. As for the erase brush tool, there seems to be something wrong. For me it only paints black irrespective what color I choose.
  4. In addition to that the character baseline doesn't work in this case. If you change the baseline, the marker and, if there, the red underline from the spell checker are moved, but not the character.
  5. When I'm using the transparency tool and I'm selecting some objects I do this with the clear intent of having transparency on this object afterwards. So I really don't see, why it would lower productivity if there is transparency added. This transparency may be even 0. I don't want you to change the workflow. But I don't agree with your point that initially handles would make no sense. One basic principle of UI design is that there needs always be a visual feedback to any of the user's action. Right now I have no idea, if I hit the right objects before I start dragging. The other thing is that currently Affinity is a brand-new product so that nearly everybody is a beginner coming from other programs. Also I think that the majority of users will not make a living of using Affinity everyday. A lot of users need a powerful program every now and than. So it's harder to get used to all the rough edges in usability.
  6. I'm not new to software development. In fact I was in the business for over 20 years. But your ideas of usability seem quiet weird to me. I have an object with no transparency. I want to have some. So I use the transparency tool. I click on an object. So the expectation is, that now there is some transparency. For some odd reasons after clicking this transparency is zero. This is a usability problem found in many open source projects. There should be a reasonable start value. The user doesn't know if she really successfully activated the tool for any object. The status bar still says "click object to select it." You should be in a state where the object is already selected and this doesn't make any send. It says "Drag handles to change selection's fill." But there are no fucking handles right now. If you want to deter beginners that's the right design decision. Otherwise you should think again. It may be helpful to look at the discussions within the Blender community concerning UI last year. Blender is a great tool, but a lot of thinks are unnecessary difficult, because the developer doesn't care about first time user of a tool.
  7. Obviously I didn't make clear what I mean. After you click the object there should be something visible to drag from. But there isn't. There is no visible feedback until you drag. If you immediately start dragging you might not notice. But when you first click and then think a little bit about what's next, you are lost. Handle - what handle?
  8. It is supposed to work in two steps: - Click on an object - drag the handles But - after clicking there is no handle. The handle appears only after you start dragging.
  9. Two finger tap is so much more convenient to open the context menu so that I have never bothered to look for alternatives. You are right. ctrl-alt-drag works as expected, if you get a little used to. What I'm struggling with is that double tap on an object doesn't just select it but also switches from move tool to node tool. Since I'm usually using the touchpad I'm used to start dragging with double tap. If I start outside any object this is working perfectly fine. But if I do it on an object the application switches to node tool. Here alt and ctrl modifiers have different meaning. At least for me it would be nice to be able to switch of this behaviour. This is certainly nice for mouse users but a little bit problematic for touchpad users.
  10. Nice to have some new tutorials. It took me some time to figure out how to use ctrl-drag selection. By default ctrl-click brings up the context menu. To use this kind of selection, you first need to go to preferences and change this. Maybe it would be a good idea to change this default. I would never ever thought of using the ctrl-key to bring up the context menu. To me, the combination of ctrl-drag and alt-drag would seem useful, too. But currently it doesn't seem possible.
  • 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.