Raptosauru5

Maybe it can be non-editable Read-only (perhaps with a small "Copy to clipboard button") in certain cases, why not.
But I think we can all agree that it would be nice to have more available info on color windows.

Now, many color pickers do show the #hex value when selecting colors:

 
However, not all of them, for example Swatches. Even though there is definitely space for a little box, above or under the Opacity dropdown.

Since I have most of my colors determined as Swatches, this is the color picker window I am using most of the times. 
Why would I want to see HEX values when I already know my colors? For example to compare parts of a UI, to see if color used is EXACTLY the same one. Or when I want to copy-paste my swatch onto a color comparison website, to compare contrast or generate color palette.
Can you please add the  box to all color windows?
Even showing a hex value next to each individual swatch color would not hurt, really

When you type “-16” into either the X or Y fields (or many other fields), that sets the value to -16 rather than subtracting 16 from the existing value.
If you want to subtract 16 from the value you can type “-=16” instead (e.g. value = value - 16, rather than value = -16).
The same sort of thing happens for W and H but “-16” for W or H (and some other fields) doesn’t make sense (a negative width or height is impossible), so those inputs are ignored.

For minus, perhaps you have to use the form shown in the Help, -=16 ?

You might find this section of the Help useful: https://affinity.help/photo2/en-US.lproj/pages/Workspace/expressions.html

I know, but for this I have to put my left hand across the whole keyboard, slowing down my flow.
 
THANKS!!! I was not aware of this! I think the feature I am asking for is not needed then.
This solves everything 👍😊

Or, for the specific example of 206px+8 you could just let it select the complete text, and just type +8 to replace it. You don't need the 206px part of it.

Doth not 99% of those within these virtual halls agree that services and wares doth require coin? The lone percent receiveth ceaseless heed, as threads are oft refreshed by the ninety-nine who yet cannot sway that stubborn minority. The solitary percent, in turn, might well ponder, 'Is the labour, the leasing of business grounds, the electric glow, the water's flow, and materials within Nottingham, UK, of aught cost?' If yea, then their grievance holds merit. If nay, then...

This is happening SO OFTEN!

When moving one object apart/to the other up/down using arrow keys in my case, the top rotation handle happens to often (with the zoom level I am often using) block the digit of distance the studio is trying to show you (currently in Designer).
Can you please ideally render this number IN FRONT of the handle instead of behind it? Or nudge it to the side or allow user to make the numbers larger. Or even removing the handle? (Users can rotate objects using corners anyway).
Thanks for consideration!

This is happening SO OFTEN!

When moving one object apart/to the other up/down using arrow keys in my case, the top rotation handle happens to often (with the zoom level I am often using) block the digit of distance the studio is trying to show you (currently in Designer).
Can you please ideally render this number IN FRONT of the handle instead of behind it? Or nudge it to the side or allow user to make the numbers larger. Or even removing the handle? (Users can rotate objects using corners anyway).
Thanks for consideration!

This is happening SO OFTEN!

When moving one object apart/to the other up/down using arrow keys in my case, the top rotation handle happens to often (with the zoom level I am often using) block the digit of distance the studio is trying to show you (currently in Designer).
Can you please ideally render this number IN FRONT of the handle instead of behind it? Or nudge it to the side or allow user to make the numbers larger. Or even removing the handle? (Users can rotate objects using corners anyway).
Thanks for consideration!

This is happening SO OFTEN!

When moving one object apart/to the other up/down using arrow keys in my case, the top rotation handle happens to often (with the zoom level I am often using) block the digit of distance the studio is trying to show you (currently in Designer).
Can you please ideally render this number IN FRONT of the handle instead of behind it? Or nudge it to the side or allow user to make the numbers larger. Or even removing the handle? (Users can rotate objects using corners anyway).
Thanks for consideration!

I would like to say that I am ok with paying this amount for a major update. V1 to V2 was a great jump and there are many updates and fixes coming for free all the time. The company has to earn somehow. If everybody just bought the first version, there would soon be no income to pay developers to work on any updates!

I would like to say that I am ok with paying this amount for a major update. V1 to V2 was a great jump and there are many updates and fixes coming for free all the time. The company has to earn somehow. If everybody just bought the first version, there would soon be no income to pay developers to work on any updates!

Hi folks,
I thought I'd give you a quick progress update and let you see some of things we've been working on at Serif Labs.  We now have a scripting core that we're reasonably happy with and have put together a little test area where we can run Javascript code, so I thought I'd show you some of that. Things to note:
This is all VERY early, like pre-pre-pre-alpha. The JS API is extremely fluid and is constantly changing. This is not how the Affinity suite will run scripts and plugins; it is just a sandbox window for internal testing. There is still a huge amount of work to be done. I can't provide any timescales for when scripting will be publicly released, for Beta or Retail. Constructive feedback is welcomed, but I won't be able to answer all questions - see previous points. I'm not claiming any of these examples are particularly useful on their own; they're just to demonstrate some basic scripting functionality. Re Javascript async - yes, we support it, I've just not recorded anything yet. The sleep calls are there for screen-recording purposes only. Here are some demos as low-res gifs. If you want to take a closer look, movs are attached.
Create a Mandelbrot image

Some dodgy physics

Insert a dragon curve

"Emojification" (translation?) of text

Create a grid of colours
 
Select and hide based on hue

Replay a document's edit history

mandelbrot.mov
balls.mov
dragon.mov
grid.mov
hue.mov
replay.mov
emoji.mov

This is happening SO OFTEN!

When moving one object apart/to the other up/down using arrow keys in my case, the top rotation handle happens to often (with the zoom level I am often using) block the digit of distance the studio is trying to show you (currently in Designer).
Can you please ideally render this number IN FRONT of the handle instead of behind it? Or nudge it to the side or allow user to make the numbers larger. Or even removing the handle? (Users can rotate objects using corners anyway).
Thanks for consideration!

Hi @Raptosauru5,
Okay I've been able to replicate it with your file  
I'm just poking this some more, as you say, it doesn't happen every time and once I've figured out the best way to trigger it, I'll get it logged with the Developers  
 

@MEB have you considered using something like a Product Portal by Productboard? It allows you to signal ideas you're interested in moving forward with, without committing to specific dates. End users can provide votes and additional feedback on individual ideas or submit new ones. It's optimized to help the product team make sense of all the inputs behind the scenes — prioritize the right features, build them in the optimal way. Worth a look!

It also seems that other people are switching to Affinity products from other software.

@MEB Thanks for reply, I am sorry to hear about your personal issues. I hope you are doing better now!
Hopefully the developers will figure out some smart way how to hide the Artboards from Layers. Overall I think the Designer could more include UI/UX designing workflows. For now it seems that UI design field could use more love in Affinity Designer. I know that this is probably not Designer's main target, but the Designer is the best tool out there for Vector graphics UI designers use mostly.
Thanks for confirming the bug. You guys are doing an amazing job, developing an amazing tool!

Very much, yes. It is incredibly annoying to deal with.

Better at least HEX than nothing.
...but if you really want to see CMYK values often, maybe there should be a small button next to this box, that would cycle between HEX/CMYK/HSL and remember that choice for each color window separately.
This way I could let it keep showing HEX and you could make it show CMYK or HSL and it would still take this  little space.

@Bit Arts I absolutely agree with all you just said.
This is the real world situation where you often simply don't have other choice.
It can totally be done elegantly

I need that and a little more.
It's an oversimplification of reality to say that hex values are mostly for web graphics. Like it or not, it has also become a colour exchange format that I encounter just as often as RGB. In addition, there are many palette generators (e.g. create palette from jpg) and other places where you only get hex. So that's what you have.
So I often find myself in the scenario where I get a colour value in a non-optional format, very often HEX and RGB, sometimes CMYK, values I copy from a PDF or the web and need to paste into Designer. And then apply them from there. So there are other scenarios than those where you have to use, for example, exact CMYK colour values.
I have often missed a functionality where you can enter or paste a colour value in hex, rgb or cmyk, which in the worst case must be approximated by Designer - Serif should feel free to notify and warn me that the entered/pasted value is approximated in the selected colour space by Designer and may differ from what is desired. It can be done elegantly.
It's a need I have in ALL colour selectors and swatches too, and regardless of whether I use HSL, wheel or anything else. Now that Serif has parsers for math in input fields and also supports regular expression in search and replace, it's time to support color codes in such functionality as well. But it can be done in several ways.
I also think it should be basic functionality for all of us who work with programs and data from a world much bigger than Affinity. Beyond that, it's just a functionality that is gentlemanly and value-adding.

Swatches are designed to maintain consistency of color throughout a document.  Placing an *editable* hex color field on the Swatches panel runs contrary to its purpose and the very notion should be immediately dismissed as a bad idea.
Also, hex values are only of interest to web designers and do not scale well: they only reflect 8-bit-per-component RGB and do not account for HDR, CMYK, etc.
Swatches may represent spot colors, which by definition are not RGB, or even CMYK; even though they have RGB/CMYK representations for display and printing on devices that do not have true spot color support, displaying RGB values for them could be considered misleading.
Similarly, displaying hex values for swatches representing CMYK colors can be similarly thought of as misleading.
Including them on RGB and RGB-related color space color pickers in the Colors panel makes a lot of sense and should cover the needs of most web designers.
The value of including them on the swatches panel, together with the potential for confusion it may cause, seems questionable.
 
What might make more sense is to include a *label* (read-only display) explaining the selected color.  This could show the hex color of the selected swatch if the swatch is an 8-bit RGB (or related) color swatch, but show the CMYK values of a CMYK swatch, the Pantone number of a Pantone swatch, etc.
This would scale better to support the range of colors that a swatch might represent, without being misleading, and without raising questions like "If I change those values what happens to the swatch?  Am I editing the swatch or am I disassociating the selected object from the swatch and giving it a different color?".