Search the Community

Hello guys, Just a humble suggestion for improving the user interface. I noticed that the toolbar has no hover effects on the tool-icons. This makes navigation a little bit less comfortable than on certain competition programs. I also noticed that the behavior of button is quite different from button to button. So what do you think of making a very subtle hover effect on the tools and buttons as you already have on (some of) the buttons in the top bar (beneath the menu)? Though the effect there is a little bit to weak, so I'd enchance it a little more. Some Buttons are great in that case (for example the little icons for layer effects, mask layer etc. in the layer panel but some don't have any (for example the dropdown-icon (opacity,...) or the 'Properties'-button in the stroke panel. I attached a little screenshot as an example for the hover effect. before (without (easy visible) hover effects): after (with (enhanced) hover effects): Cheers, Jay

I am currently using the Affinity Beta for PC and altough I am thinking to switch from Illustrator to Affinity Designer, there are some points that could need some polish. Most of them are minor UI changes. One of them, and maybe the biggest, is how Affinity handles layers. I cannot count how often I just wanted to drag one layer on top or below a certain one and ended up masking them or grouping together. I know there is a dedicated button to do that but I want to know exactly where my layer is right now and not guess and count how often I pressed to "move layer up" button. Second issue I had is the way Artboards are managed. Right now they simply behave like a regular layer which often leads to unwanted selections or movement of the artboard, when I just wanted to select an object. This could be easily improved by giving the Artboard tool more "power" and just allowing to resize or change artboards when the Artboard button is clicked. Otherwise I like the clean UI of Affinity Designer very much and hope that the developers will improve the software wisely and avoid it to become a second Photoshop or Illustrator with 1000 hidden menus and functions nobody can find anymore. Keep up the great work! Regards

Hi, I am new to AD but used PS/AI a lot and I have problem in work efficiency / speed when it comes to select objects. Normally I press "V" and I can be sure that I am in the move tool and start to click-drag a marquee selection. Unfortunately in AD I'm not. Because if the move tool is already active "V" toggles to the last used tool. And if I start my click-drag action to create the marquee selection - something other happens, e.g. I paint or what tool is ever active then. I couldn't find a setting option in the preferences to prevent that behavior. Is there something I overlooked? Thanks. Also thanks, for that great software package.

Hello This feature was requested by me when discussing a bug, so now I'm requesting it here at the right place. At the moment, when a user has OSX in a non-english language, the OS offers a translation of certain common font styles like bold, italic, regular etc. In a few applications made by Apple such as Numbers or Pages, and also in the Font Book app, these translations are used when selecting fonts from the fontmenu. Most professional design applications however use the original (non-translated) names in the font selection. At this moment, Affinity applications use the translated names, even though the rest of the user interface is English. I personally think the way OSX translates font styles is quite primitive, and I often encounter fonts where half of the styles are translated in Dutch, while the other half are not translated because the typedesigner chose non-traditional names for these styles. Other design-related applications ignore the OSX translations and use the original style names, which is more practical in a professional environment. As long as Affinity doesn't offer application wide translation, I personally think it's better for Affinity to ignore the OSX translations, because we now get a inconsistent user interface with two languages. I'm looking forward to hear how you think about this.

Upon clicking the paragraph alignment tool dropdown (normal left/center/right buttons work fine), displays dropdown for one frame and then crashes. Reproducible.

The white marker of the transform tab does not move but the selection within the 9 grid marker does enlarge. 1) Add object to page 2) Open Transform tab 3) Select top centre for transform anchor Observe: The white marker remains at top left (top centre marker is enlarged showing this is selected)

I chose English as my Affinity Photo UI preferred language. My main OS chosen language, however, is Canadian-French. When I want to access Help from its menu, I get the Canadian-French version, which is not ...helping. Now, I can switch the OS language to English but then the keyboard mapping is all messed up. Any ideas?

Hey guys, check out this nice interface for the Offset Path command in Autodesk's Fusion 360. I think something like this might be great for AD's command as well, similar to the current implementation of the Corner Tool UI

Hey there, in a document I changed the color of the grid in the "Grid and Axis Manager ..." from default lightgrey to a darker one and sved the document. After reopening the document the grid turns back to the lightgrey and I have to change it agian. Also the opacity sliders look wrong compared to the one in the bottom of the color-panel.

I am experiencing a few display errors (in 1.5.0.2 and still in 1.5.0.4): On the View menu I can only see the top half of the 'Grid and Axis Manager' option below 'Snapping Manager...' Going down the menu with the arrow key there are a nine presses when the 'selection' is off screen, so I presume there are at least nine more options? Also the last option visible on the Layer menu is 'Fill Mode' but from the down arrow key there is at least one more. When searching Help, only the top half of the final line of text in the results shows. Extending the height of the pop-up window does not help. When clicking the Snapping options drop down menu, the options in the bottom two grey rectangles do not display properly: there is no text, just what looks like cropped check boxes. This is on a 1366x768px Windows 8 (not 8.1) laptop. A couple of comments on the environment: Everything seems so BIG on a 1366x768 screen. The minimum width of the docked panels takes up a quarter of the screen width, that seems too much. It is more than AI, Corel Draw or Draw Plus (but similar to Inkscape) on the same resolution screen. Also a small icons option would reduce the top area which is about a fifth of the screen - about double that of AI (and bigger than CD, DP and IS). Finally, I agree with many others that a lighter environment would be good as an option - I generally prefer a neutral surround but it would be nice to have the choice of light, dark or inbetween. Grumbles aside, thank you for all the hard work and effort you are putting in to this.

On trying to reorder and configure the right sidebar panels to my liking, I have found that the drag and drop is pretty temperamental, in that sometimes it will think I want to add a tab to a panel when I would like a new panel, or vice versa. So this makes it tough to configure the sidebar the way that I would ideally like it to be, however because of this behavior I have been able to consistently crash Designer for trying to move/order panels. I think that part of the reason is that I collapsed the panels and tried to move multi-tab ones, but also I noticed that trying to reorder a panel to be at the top is hard. I would assume that more tolerance for how and where to place these tabs/panels would probably help with the behavior a little. Application: Designer.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.InvalidOperationException at Serif.Windows.UI.Studio.Controls.DockingManager.CreateUndockingScope(Serif.Windows.UI.Studio.StudioObject, System.Windows.Point, Serif.Windows.UI.Studio.Controls.UndockMode) at Serif.Windows.UI.Studio.Controls.DockHelper.Undock(Serif.Windows.UI.Studio.StudioObject, Serif.Windows.UI.Studio.WindowProfile, System.Windows.Point, Serif.Windows.UI.Studio.Controls.UndockMode, System.Windows.Rect) at Serif.Windows.UI.Studio.PageManager.OnPageHeaderDragStarted(System.Object, Serif.Windows.UI.Studio.Controls.DragAbsoluteEventArgs) Exception Info: System.Reflection.TargetInvocationException at System.RuntimeMethodHandle.InvokeMethod(System.Object, System.Object[], System.Signature, Boolean) at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(System.Object, System.Object[], System.Object[]) at System.Delegate.DynamicInvokeImpl(System.Object[]) at System.Windows.RoutedEventArgs.InvokeEventHandler(System.Delegate, System.Object) at System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, System.Object) at System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs) at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean) at System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs) at Serif.Windows.UI.Studio.Controls.DockingHeaderControl.OnMouseMove(System.Windows.Input.MouseEventArgs) at System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, System.Object) at System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs) at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean) at System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs) at System.Windows.UIElement.RaiseTrustedEvent(System.Windows.RoutedEventArgs) at System.Windows.Input.InputManager.ProcessStagingArea() at System.Windows.Input.MouseDevice.Synchronize() at System.Windows.Input.MouseDevice.PostProcessInput(System.Object, System.Windows.Input.ProcessInputEventArgs) at System.Windows.Input.InputManager.RaiseProcessInputEventHandlers(System.Windows.Input.ProcessInputEventHandler, System.Windows.Input.ProcessInputEventArgs) at System.Windows.Input.InputManager.ProcessStagingArea() at System.Windows.Input.InputProviderSite.ReportInput(System.Windows.Input.InputReport) at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr, System.Windows.Input.InputMode, Int32, System.Windows.Input.RawMouseActions, Int32, Int32, Int32) at System.Windows.Interop.HwndMouseInputProvider.System.Windows.Input.IMouseInputProvider.CaptureMouse() at System.Windows.Input.MouseDevice.Capture(System.Windows.IInputElement, System.Windows.Input.CaptureMode) at Serif.Windows.UI.Studio.Controls.DockingHeaderControl.BeginDrag(System.Windows.Point) at Serif.Windows.UI.Studio.Controls.DockingHeaderControl.OnInitialized(System.EventArgs) at System.Windows.FrameworkElement.TryFireInitialized() at MS.Internal.Xaml.Runtime.ClrObjectRuntime.InitializationGuard(System.Xaml.XamlType, System.Object, Boolean) Exception Info: System.Windows.Markup.XamlParseException at System.Windows.Markup.XamlReader.RewrapException(System.Exception, System.Uri) at System.Windows.FrameworkTemplate.LoadTemplateXaml(System.Xaml.XamlReader, System.Xaml.XamlObjectWriter) at System.Windows.FrameworkTemplate.LoadTemplateXaml(System.Xaml.XamlObjectWriter) at System.Windows.FrameworkTemplate.LoadOptimizedTemplateContent(System.Windows.DependencyObject, System.Windows.Markup.IComponentConnector, System.Windows.Markup.IStyleConnector, System.Collections.Generic.List`1<System.Windows.DependencyObject>, System.Windows.UncommonField`1<System.Collections.Hashtable>) at System.Windows.FrameworkTemplate.LoadContent(System.Windows.DependencyObject, System.Collections.Generic.List`1<System.Windows.DependencyObject>) at System.Windows.StyleHelper.ApplyTemplateContent(System.Windows.UncommonField`1<System.Collections.Specialized.HybridDictionary[]>, System.Windows.DependencyObject, System.Windows.FrameworkElementFactory, Int32, System.Collections.Specialized.HybridDictionary, System.Windows.FrameworkTemplate) at System.Windows.FrameworkTemplate.ApplyTemplateContent(System.Windows.UncommonField`1<System.Collections.Specialized.HybridDictionary[]>, System.Windows.FrameworkElement) at System.Windows.FrameworkElement.ApplyTemplate() at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size) at System.Windows.UIElement.Measure(System.Windows.Size) at MS.Internal.Helper.MeasureElementWithSingleChild(System.Windows.UIElement, System.Windows.Size) at System.Windows.Controls.ContentPresenter.MeasureOverride(System.Windows.Size) at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size) at System.Windows.UIElement.Measure(System.Windows.Size) at System.Windows.Controls.Control.MeasureOverride(System.Windows.Size) at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size) at System.Windows.UIElement.Measure(System.Windows.Size) at MS.Internal.Helper.MeasureElementWithSingleChild(System.Windows.UIElement, System.Windows.Size) at System.Windows.Controls.ContentPresenter.MeasureOverride(System.Windows.Size) at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size) at System.Windows.UIElement.Measure(System.Windows.Size) at System.Windows.Controls.Border.MeasureOverride(System.Windows.Size) at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size) at System.Windows.UIElement.Measure(System.Windows.Size) at System.Windows.Controls.DockPanel.MeasureOverride(System.Windows.Size) at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size) at System.Windows.UIElement.Measure(System.Windows.Size) at System.Windows.Controls.Grid.MeasureCell(Int32, Boolean) at System.Windows.Controls.Grid.MeasureCellsGroup(Int32, System.Windows.Size, Boolean, Boolean, Boolean ByRef) at System.Windows.Controls.Grid.MeasureOverride(System.Windows.Size) at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size) at System.Windows.UIElement.Measure(System.Windows.Size) at System.Windows.Window.MeasureOverrideHelper(System.Windows.Size) at System.Windows.Window.MeasureOverride(System.Windows.Size) at System.Windows.FrameworkElement.MeasureCore(System.Windows.Size) at System.Windows.UIElement.Measure(System.Windows.Size) at System.Windows.Interop.HwndSource.SetLayoutSize() at System.Windows.Interop.HwndSource.set_RootVisualInternal(System.Windows.Media.Visual) at System.Windows.Window.SetRootVisual() at System.Windows.Window.SetRootVisualAndUpdateSTC() at System.Windows.Window.SetupInitialState(Double, Double, Double, Double) at System.Windows.Window.CreateSourceWindow(Boolean) at System.Windows.Window.ShowHelper(System.Object) at Serif.Windows.UI.Studio.FloatingWindowManager.ShowFloat(Serif.Windows.UI.Studio.StudioFloatSite, Boolean) at Serif.Windows.UI.Studio.FloatingWindowManager.AddFloat(Serif.Windows.UI.Studio.StudioFloatSite) at Serif.Windows.UI.Studio.PageManager.OnViewSitesChanged(System.Object, System.Collections.Specialized.NotifyCollectionChangedEventArgs) at System.Collections.ObjectModel.ObservableCollection`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].OnCollectionChanged(System.Collections.Specialized.NotifyCollectionChangedEventArgs) at System.Collections.ObjectModel.ObservableCollection`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].InsertItem(Int32, System.__Canon) at Serif.Windows.UI.Studio.StudioGroup+OwnershipCollection`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].InsertItem(Int32, System.__Canon) at Serif.Windows.UI.Studio.Controls.DockHelper.Undock(Serif.Windows.UI.Studio.StudioObject, Serif.Windows.UI.Studio.WindowProfile, System.Windows.Point, Serif.Windows.UI.Studio.Controls.UndockMode, System.Windows.Rect) at Serif.Windows.UI.Studio.PageManager.OnPageHeaderDragStarted(System.Object, Serif.Windows.UI.Studio.Controls.DragAbsoluteEventArgs) Exception Info: System.Reflection.TargetInvocationException at System.RuntimeMethodHandle.InvokeMethod(System.Object, System.Object[], System.Signature, Boolean) at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(System.Object, System.Object[], System.Object[]) at System.Delegate.DynamicInvokeImpl(System.Object[]) at System.Windows.RoutedEventArgs.InvokeEventHandler(System.Delegate, System.Object) at System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, System.Object) at System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs) at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean) at System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs) at Serif.Windows.UI.Studio.Controls.DockingHeaderControl.OnMouseMove(System.Windows.Input.MouseEventArgs) at System.Windows.RoutedEventArgs.InvokeHandler(System.Delegate, System.Object) at System.Windows.RoutedEventHandlerInfo.InvokeHandler(System.Object, System.Windows.RoutedEventArgs) at System.Windows.EventRoute.InvokeHandlersImpl(System.Object, System.Windows.RoutedEventArgs, Boolean) at System.Windows.UIElement.RaiseEventImpl(System.Windows.DependencyObject, System.Windows.RoutedEventArgs) at System.Windows.UIElement.RaiseTrustedEvent(System.Windows.RoutedEventArgs) at System.Windows.Input.InputManager.ProcessStagingArea() at System.Windows.Input.InputProviderSite.ReportInput(System.Windows.Input.InputReport) at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr, System.Windows.Input.InputMode, Int32, System.Windows.Input.RawMouseActions, Int32, Int32, Int32) at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr, MS.Internal.Interop.WindowMessage, IntPtr, IntPtr, Boolean ByRef) at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef) at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame) at System.Windows.Application.RunDispatcher(System.Object) at System.Windows.Application.RunInternal(System.Windows.Window) at Serif.Affinity.Application.RunSingleInstance() at Designer.Application.Main(System.String[])

I’m so excited to finally be playing with the Windows version! Well done, and thank you. Some observations, queries, and suggestions based on my first experiences: I have my Windows taskbar set to auto-hide, and it’s not accessible when I’m in AD. I can press the Windows key to bring it up, but it would be nice to be able to move the cursor down to the bottom of the screen to access it, like I can from most apps. It would be nice to be able to tab between input fields, in dialogues and in palettes in the studio. I like to use keyboard shortcuts as much as possible, but it feels slow and clunky to have to manually click in each field to enter a new CMYK colour, for example, instead of tabbing between them. Esc doesn’t work across dialogues as I would expect it to. For example, if I bring up the preferences, I have to click “Close” to make it go away. Likewise for layer effects. Again this interrupts my keyboard shortcut flow. Also with layer effects, it would also be nice to have a single Cancel option. Sometimes I like to fiddle and play with effects to see how they look, but then decide to cancel. As far as I can tell, I need to remove each effect I’ve added. Perhaps this is just a different approach that I will grow to like once I’m used to it. Are there ways to create presets for new documents, PDF export, etc? That would be very useful for me. What about viewing colour separations? It’s essential for my work. I’ve found working with text to be extremely buggy. AD has crashed more than ten times on me just doing basic text operations like changing fonts, font size, leading, escaping the text frame, etc. I will create another thread as soon as I can pin it down and be a bit more specific about the steps that lead to crashes, but for now it seems like there are a lot of issues with text, and many things have triggered the crashes. Also, relating to text: Ctrl + Shift + > makes the text bigger, as I am used to in InDesign and Illustrator, but only one step for each press. It would be nice to be able to press and hold it to scale a large amount quickly. Or is there another way to do this? No warning for overset text? Is it possible to flow text between frames? Filler text isn’t selectable, except as a whole block. It would be useful to be able to edit it directly, as if I had typed it. A few times certain characters wouldn’t appear when I typed them, but others would. An invisible space would appear, so I could continue typing afterwards, and clear the missing character, but still not type it. This seemed inconsistent and irregular, but was consistent for certain characters within a frame in a session. It was usually followed by a crash. If “Check Spelling While Typing” is checked, everything I type is marked with the red squiggly line. When I restart AD after a crash it usually (but not always) says that it has been restarted after a serious error, and asks if I would like to send the error report. I always choose Yes, but then don’t see anything else about it. Does it send in the background, or should it be obvious that it is sending? Any other suggested best practices for error reporting, or tracking steps that cause crashes? Obviously it’s helpful if we can list steps to recreate a crash, but anything else? Any way to automatically track and save a history? Aside from the above problems I’m excited. It seems fast and has lots of useful features that I look forward to exploring more thoroughly. I look forward to a time when it’s stable and I can really start relying on it in my day-to-day workflow. Thanks for all your hard work, and the chance to give it a spin for free!

Hello, my name is Chris (15 yrs ) I'm a web designer. I spend all of my day and most of my nights in a design tool. One day I hope I'll have the honors of being Drafted on Dribbble so I can (seriously) share my works with the design community and get better projects. The design I'll being presenting to you is my portfolio site, I originally started in Photoshop with this but I ended up deleting most of what I did because I wasn't pleased with it and I ended up redoing it in AD. If you'd like the full size version Click Here

Hey Affinity Designer developers, a few bugs I found so far: The User Interface bugs when I hit the full screen button and doesn't show the Layer bar and menu anymore. Workaround: After minimizing the window everything looks fine. I clicked on a Group with Text curves inside that have FX. When I hit the fx Button, there is none of the FX possibilities marked, but with the Text curve activated hitting the fx bar the Gaussian blur is activated. The bug doesn't occur when i activate one Text curve and hit the fx button of another Text curve. Thank you very much for making this project bigger and bigger, even for Windows users. :) Kind regards, MonsieurMey

Note: I've recreated this bug a couple of times to confirm that it is visually broken Description: Preferences>User Interface> The UI color editing sliders work normally except the first two (Background grey level and Artboard Background grey level) only after the IU Gamma slider is used. Functionally they still change the background of the intended ui elements, however, the slider tip stops moving. Recreate it: Use the UI Gamma slider and then try changing the values of the upper two. Hope this helps.

Hi, I’d like to use Affinity Designer for designing user interfaces, but, you know, it’s so tricky to design interfaces without this feature. Can someone help me? All the best, Vladislav

Hi there, firstly, affinity Designer is simply amazing!! I do apologise for this question if it has already been answered, I did have a look through the pages and never saw it. I want to know if Affinity designer would ever have pre built in design templates for UI and Icon Design? I create a lot of iOS and Android icons and design user interfaces for mobile apps also, it would be super cool if Affinity had a preset iOS, Mac OS and Android icon template as well as standardised UI frameworks built in to speed up my design process. If this is not a feature to be considered, is it possible for me to create these frameworks myself and have them stored ready to use when I need them? Thanks

Hey guys, More UI work. Let me know what you think. https://www.behance.net/gallery/37180653/Android-Weather-App Cheers, Vlad

Hi, maybe it has been asked bevor but it worries me much often. Some values (e.g. color sliders) can be changed by arrow keys, some (e.g. font size) don't. Why doesn't this work everywhere in the app

Please make Distribute options easier to find in Affinity Photo. They aren't on the ribbon, they apparently aren't in the Arrange or Alignment menus--why not?--and it takes some clicking around to finally find them hidden in the pop-up you get when you click on the Arrange icon. It blows my mind that the Arrange icon offers functionality not available (or at least, I can't find it) in the menu system! How about adding a Distribute icon to appear along side the Arrange icons in the ribbon?

Some of the UI elements which are not visible either require a lengthy mouse press-and-hold to be revealed, like secondary tools, or use UI devices which use lengthy animations to reveal the element (eg, snapping options). These while cute quickly become annoying when working under pressure on time critical projects. It would be great if there was a way to toggle UI animations off or enable fast UI mode. In particular, right click on tools with secondary options should reveal the menu (or whatever UI device needs to be displayed) instantly.

Update Dropdown What I did was think about components and what parts belong to what. And for this model to be clear from the UI / UX perspective, it means that the other colour options should be separated into their own panels due to their unique attributes. In my experience, I would recommend removing the colour wheel--it adds no functionality that the sliders can't provide and adds a level of complexity to maintain in the long run. I can't keep working for free, so, this is it from me. ----- Previous -----

Maybe a side effect of what I was used to before AD (let's call it Anno Designer -AD- :P), but I greatly appreciate the automatic selection of "Export Selection" mode (as opposed to "Export whole document") in packages such as Pixelmator or OmniGraffle when you choose Export with something highlighted, and I miss it in AD. Is there a way I can achieve that in AD? At the moment, everything is driven from the document size but if you're experimenting you just set up a large canvas and try out ideas, and to then have to hammer everything back into a specific document size is quite an enterprise - ironically losing the whole benefit of vectorisation to pixel related issues. So far, the only way way I have found to exercise some control is by using an Export Persona Slice, but here too, you must start with first mapping the elements you want to export into one group, as the slice creation tool will otherwise create a slice for each component. Maybe a modifier to the "Create Slice" button would help. If you could alt-click or shift-click to create one SINGLE slice of all the selected layers instead of a herd of individual slices of each selected layer it would already be a big step forward. Anything I missed?

I was excited to learn about the new program Affinity Photo. But then I saw some screenshots. Just to let you know (whom it concerns) - I will never buy another program with a black UI. I bought pixelmator, but I can't use it. It's too hard on my eyes.

Hi, I often have problems to read the histogram with overlapping curves. Its hard to see which channel is responsible for the white curves. I think Apple Photos is doing it better as it always shows the curve outlines in the channel color.