MoonaticDestiny

I didnt know you could gradient noise through the gradients stops. Im just finding out. Thats such a very weird way of working because gradients is mainly for color. Not noise. You dont gradient noise. You gradient color. If you wanted to gradient noise you should add a noise fx to a layer and then use the transparency tool to gradient the noise instead. I say that Noise should be an FX in the FX studio because currently noise only has 1 property, the opacity property in the color studio. Noise should have more properties that you could change like the color of the noise, the size of the noise, the blend mode of the noise, the opacity of the noise, the intensity of the noise, and different types of noise. These are properties that appear in an FXs context menu. You dont have these properties in the color studio for the Noise. Theyre unavailable. Thats why I say Noise should be an FX because it needs to have other properties that you could change other than just opacity. What a weird way of using noise in the gradient stops. Its an FX thats being applied to the gradient stops.

The color studio icon displays the color for both the color and stroke fill. It should not be like that because you already have a color indicator for the stroke fill. Which is the stroke studio icon. So the color studio icon should only be displaying the color for an object with a color fill. Not a stroke fill. So you need to create a 3rd icon that is an outlined circle icon to represent the stroke fill to an object. That way the color studio represents an objects color fill, the outlined circle represents an objects stroke fill, and the stroke studio can represent a strokes width. This would then allow users to perform their studio gestures to change their color or strokes value. Please watch the videos below. It explains more in detail. Theres also a mock up of the 3 icons at the bottom. At the end I reference the color and stroke studio combined. I talk about combining both studios here in this forum on how they need to combine. fill issue1.mp4 fill issue2.mp4

I found another issue while trying to solve this issue. Theres actually ✌️2 color indicators in the app and 1 of these color indicators is WRONG because its indicating the color for both the color fill AND stroke fill when it should just be the color indicator for the color fill. I will make a whole separate forum post about it, and I will quote this post with the new forum post.

I want to also note that if a user taps the stroke studio icon then the stroke fill should be above the color fill and if a user taps the color studio icon then the color fill should be above the stroke fill. Color Studio --- Color Fill above Stroke Fill Stroke Studio --- Stroke Fill above Stroke Fill

So what happens when an object with both a color fill and stroke fill is selected? What should be above what? The color fill or the stroke fill? The answer is the color fill. The color fill should be above the stroke fill.

Stroke and Color studio combined. Now, if I select a stroke I can change its color and width. No more going to the stroke studio only to find out that the color property of my stroke isnt there.

So first you need to remove the noise slider from the color studio. Noise is not a property of color. It has no reason to be there. Make it its own FX in the FX Studio. Remove the noise slider and bump everything upwwards. Then you need to remove swatches out of the color studio and make it its own studio. You cant have a HIDDEN studio within another studio. Look at the photos below for reference.

So the issue is the "color indicator" that the stroke studio icon changes to depending on the color of your stroke is FOOLING users into thinking that the color property of their stroke is in the stroke studio when its not and its causes workflow disruption and we're forced to stop, think a bit, and go to the color studio because thats where the color property of our stroke is. On top of that, Serif, divided the stroke properties, color and width, into 2 studios and it shouldnt be like that because these 2 properties relate and go together. Its time to combine the stroke and color studios into 1 studio to solve this issue.

Heres a video of me talking about an issue thats happening with strokes in AD v2 for ipad. Strokes have 2 properties, a color property and a width property. Both of these properties have been divided into 2 studios, the color studio and the stroke studio. This should not be happening. These 2 properties should not be divided nor split into 2 separate studios. They need to be together and the color and stroke studio FINALLY need to combine into 1 single studio. Its long overdue and it needs to happen. This isnt an issue on the desktop version because youre allowed to have multiple studios open. On the ipad you cant have multiple studios open so the solution is to combine these 2 studios into 1 studio that holds all the properties to an object or stroke. Stroke3.mp4 Stroke4.mp4

So I actually made a mistake for the artboard contextual menu. I forgot to add the lock icon. The lock icon because locking an artboard is something that you can do in affinity designer so users should have the ability to lock their artboard QUICKLY if they click on an artboard. So its nudge, lock, duplicate, delete, and deselect. Below is an image of the new artboard contextual menu. NOW we are done with the artboard contextual menu.

THIS! They did this with the new context menu in v2. Its so upsetting. Im gonna make a whole video about. I like adjusting FX in V1. Not V2. Adjusting FXs in V2 is SO BAD because of the new context menu being split into two. One at the top and the sliders on the left. Im gonna make a whole video about it as well. Sigh. Theres so much that needs to be done. Im just focusing on this new contextual menu because it needs to happen.

Heres a new image of the interface below with the new contextual menu. We removed the help button and placed it next to the edit menu to prevent accidental triggering that caused workflow disruption for right handed users. We removed the deselect and delete button at the bottom left of the interface because they caused workflow disruption for left handed users and theyre now located on the new contextual menu. Theres a new contextual menu that appears depending on what object you have selected. Selecting an artboard reveals a contextual menu containing 4 actions. They are nudge, duplicate, delete, and deselect. The personas are now displayed for faster toggling into where before it required an extra step for users to toggle into. and thats it for now. Thats solves most of the issues. This is just a mock up. A blueprint to help you for a future build, Serif.

The photo above 👆, THIS is how the affinity designer app should look like minus the top bar icons that I removed for the time being. THIS is how its supposed to look like. THIS is what the app should be and its going to look even better once tool and studio customization happens later on. Im literally giving you all the design logic and evidence to make these changes. This is not me making interface changes just because. Theres design logic behind this. We can make this app better for right and left handed users.

Heres the mock up of the help button. You take it from the bottom right corner and move it next to the edit menu. Thats it. No more workflow disruption.

Now, we moved the delete and deselect buttons into the new contextual menu. The help button though needs to be placed else where. You probably want to place it next to the edit menu. Thats the only place I can think of where it would be good to place and then what you might want to do is allow users to hide this help button. Just how you allow users to hide the undo/redo buttons, do the same for the help button. Also, those undo/redo buttons shouldnt even be at the bottom right of the interface because they too cause workflow disruption. Its a good thing you can hide them. So let me do a mock up of where the help button should go. Give me some time.

The artboard contextual menu is done. Its done. This is all you have to do. I already did the dreaming for you. You just have to do the work and implement it into your app. This is easy. Its the others that need more work and explaining. So artboard contextual menu is done. We can check that off our list.

Heres the mockup of the artboard. Its super simple. Nudge, duplicate, delete, and deselect. In adobe illustrator for ipad, these are the same actions that appear when you select your artboard only here I added the deselect action to go with the other 3 actions.

So we removed the bottom left and right icons because of workflow disruption. Now lets talk about the contextual menu for artboards because thats the easiest one. Sigh. Again, I dont have the adobe illustrator app but please look at it for reference. Theyre doing it right. So In adobe illustrator for ipad, when you select an artboard, a contextual menu appears at the bottom of the artboards. On that menu there are 4 actions. A nudge action, a duplicate action, a delete action, and the deselect action. Its that easy and thats all that needs to go on the artboard contextual menu. Let me see if I can mock it up for you. Give me some time.

So continuing the blueprint for the contextual menu for a future build, Im leaving these images below for reference. All Im doing is removing the icons. I dont want to say "removing." Im just taking them off the UI for right now because theyre going to be placed somewhere else with better design because the current location is bad design. Very bad. I will continue adding to this forum when I have the time. Im going to talk about the actions that need to be on the contextual menu, the ones that go under objects, the ones that go under artboards(because that ones the easiest one), and why those actions need to be on the contextual menu.

Please watch the videos below. I made a video about an issue thats happening in the affinity designer v2 ipad app. I cant put it into words because its too much to explain and it doesnt translate well into words. I really need @Ashor anyone from the development team to please watch it. I get it. This issue will not be solved right now, but I just want to start a blueprint for it already for future builds. I also want to provide an article from Vectornator that explains more about this contextual menu and how its a better workflow for their users. They call it "Quick Actions." https://www.vectornator.io/blog/vectornator-4-0-preview-quick-action Im really sorry about the video quality. I had to upload it at 640x480 and in 2 parts because 720p and 1080p took very long to upload. Watch it in full screen mode. CONTEXTUAL MENU1.mp4 CONTEXTUAL MENU2.mp4