fde101

I just wish global was possible on the iPad version. I have to do some work on desktop and then swap to iPad which means I have to think about where and when I can set work up. I guess it will get there eventually!

I've seen a couple "flash" sales on it since C1 - 20 came out.   I really hope they get on the loyalty discount train, as the upgrade prices are usually ridiculously close to that to add minimal features.  
$180 is indeed one of the better deals I've seen on it.   It is also in line with there is likley a new version ready to drop in about 3 months...just far enough out that one would still have to pay the $120-150 upgrade cost ($120 if they do another pre-order type of deal - where you don't even know what you will be getting)
 
If Darktable could speed up the processing speed, and simplify the toolset and layout, it woudl be a much easier "sell" but as it is, feels more like for advanced users that also don't need a speedy workflow.  It can produce great results, but feels like it takes a lot more time and effort to get there.

The only use case I personally can think of for this is to simplify the process of importing the image into another application which relies on the DPI information to control the initial placed size of the image within a document that contains other elements.

Hi @Rupert Cook, welcome to the forums!
If I am correctly understanding what you are asking for, you can achieve something similar in Affinity Designer by taking advantage of the Export persona.  You would create a single page large enough for the entire design and create the design as if meant for a single large page, then in the Export persona would create slices the sizes of the individual pages and configure them to export in the desired format (PDF for example). After that you can export them all at once using the "Export Slices" button; a separate PDF will be exported for each slice.

All, there is really no point to all of these "me2" posts and the like - check the "Recommended" post at the top of the page: they are already working on implementing this.
Step back and give them time to do it right.  It's coming.

As was just pointed out, this has come up numerous times in the past, so hijacking this largely unrelated thread to once more beg for Page Plus import support is inappropriate.
That said, Serif had at first indicated that a Page Plus importer would *NEVER* happen, then later softened that to say that *IF* it was going to happen, it would not happen until Publisher was fairly close to offering the feature set that Page Plus had, so that the import could work effectively.  From what should be obvious to those who have been around forum for a while, we are still far from having reached that point.

My take on it is that catalogs are preferable for personal photos (for their ability to let you look back through the history of what was previously taken) and for people taking photos for a single company or client over a long period of time (someone on staff at a company, taking lots of photos just for them - for similar reasons).
Sessions are preferable for people doing individual jobs in isolation from each other.
 
This one I disagree with.  I don't currently have any of those camera brands (though I would like to get a Sony at some point for its low-light capabilities, and I am curious about some of Fuji's more unusual sensor designs), and I do work with photos from an assortment of camera brands (Olympus, Panasonic, Sigma, Canon...), but I still consider the cost of that program to easily be worthwhile.

Just "wake up" the original thread by adding a new post. There is no need to create a new thread with exactly the same topic (which, by the way, is against the rules of the forum).

Most of the time when people are asking for the "hex color input" they are looking for something they can copy/paste into HTML/CSS code for use on the web, and that would need to be RGB.
To make sure we are clearly interpreting what you are asking for, are you looking for the actual HSL values to be encoded as HSL in hexadecimal format (which would be compatible with nothing), or are you asking for the RGB values to be encoded as hexadecimal and displayed on the tab along with the HSL color wheel (to be able to transfer values back and forth with HTML/CSS)?

This thread is yet another duplicate of several others, most notably:
 

Wouldn't fading the font make reading the text and therefore selecting another tab more difficult though?
How about leaving the colours as they are but highlight the active tabs top edge with an accent line the same colour as the text? (white or black depending on the selected UI style)

This way which tab has focus is clear and doesn't distract from any colour perceptions on the image
Regards

All, there is really no point to all of these "me2" posts and the like - check the "Recommended" post at the top of the page: they are already working on implementing this.
Step back and give them time to do it right.  It's coming.

Another way to handle this is to take the text from one of the photos and add it to your Assets panel; then you can simply drag that onto the next photo and edit the text, formatting intact.

@kingfisher, welcome to the forums!
 
1. Already available - in the Swatches panel's hamburger menu select "Show as List"
2. You can manually rename the color swatches, global or otherwise.  I recommend naming global color swatches things like "sidebar", "body text", "separators", etc., for the function they have rather than the color they are presented as.  That is a helpful way to maintain better consistency in the document, plus you can change the colors and the naming still applies.
3. If you are referring to bitmap images as fill patterns, this is done using the Fill tool.  Select the item you want to fill with a bitmap, choose the fill tool on the toolbar, and on the context menu, set the "Context" to either "Fill" or "Stroke" (whichever one you are trying to apply the image to) and set the "Type" to "Bitmap" - you should be prompted to select an image file to use for the fill.

One of the Serif staff said that the 1.9 beta will have some kind of function to save/restore user interface layouts.

This is extremely unlikely.  As I mentioned above, Serif has already stated in another thread that it is a specific toolkit on the Windoze platform that prevents them from doing this right now.  Porting the Mac version to ARM would not face that same issue, so even if they do release an ARM version for the Mac, that won't make any progress at all toward a Windoze version on ARM.  They already have the iPad version running on ARM so anything the Mac and Windoze versions would have in common to benefit by for ARM is almost certainly already in place for that.

Hi @sujithta, I'm not exactly sure what you are requesting here, and using overly large text in your post doesn't make it any easier to understand.
 
To create a mask from a pixel selection, you can choose Layer -> New Mask Layer, or click the Mask Layer button along the bottom of the Layers panel.  If you have an existing mask layer and select it, you can use the brush tool (for example) to modify that mask, and it will be restricted to make changes within a pixel selection if you have one.
Option (alt) clicking on a layer (on the Mac at least) takes you into isolated editing mode for that layer, hiding the other layers while you are working on it.  Shift clicking a mask layer toggles it on and off.
To invert the mask, select it in the Layers panel and choose Layer -> Invert (menu bar), or use the keyboard shortcut (Command+I on the Mac).

It has been explained on numerous other threads why this is not practical.  I would not expect this to happen, ever.
 
Not practical outside of document palettes.  They are already created as global by default when using the commands that create them as global swatches.  Simple stuff.
 
I agree that these would be very nice...  #12 was already brought up on other threads though.
 
This has already been discussed on numerous other threads.
 
That is because the eyedropper is picking up the color from the display on the screen, not from the document.  It always captures in RGB from what I can tell, and can pick up colors that are from other objects on the screen which are not actually part of the document (from the UI itself for example, or even from outside of the Affinity applications).
 
 
Finally, a few reminders from the guidelines which are not being followed here:
 

The iPad versions are missing a number of major features of the desktop versions.
That said, I would certainly expect the Intel-compiled versions of the Affinity software to be working with the ARM-based Macs fairly quickly under Apple's emulation.
I suspect that Serif probably won't be slow in updating to native ARM builds either but considering how well some of the much more demanding 3D applications appeared to be running in Apple's demos in the WWDC videos, the performance of emulated Intel code should be good enough for most of us when dealing with 2D graphics, particularly since the metal acceleration should still run natively on Apple's GPU, thus not much reason to hold back on getting at least that much going right away.

Yes, and those of us who have been around on the forums (or who actually take the time to read the online help) know that, but someone who randomly stumbles on the program on one of the various app stores (or the Serif web site) might not be expecting to need to do that.  If they create documents which are then made public it has the potential to make their name publicly available in a manner they might not have anticipated, and depending on the nature of the material and its distribution, that can sometimes be a bad thing.

Yes, and those of us who have been around on the forums (or who actually take the time to read the online help) know that, but someone who randomly stumbles on the program on one of the various app stores (or the Serif web site) might not be expecting to need to do that.  If they create documents which are then made public it has the potential to make their name publicly available in a manner they might not have anticipated, and depending on the nature of the material and its distribution, that can sometimes be a bad thing.

I personally think they should default the title and author fields to blank.

Interesting find.
If I set the spacing to anything less than 4 pixels the grid becomes invisible regardless of zoom level.
I suspect this should really be in the bug report forum?

Anything that can be done layer-based can also be done node-based and then some.  There have been indications elsewhere on the forum that have suggested that the engine behind the Affinity products is in fact node-based behind the scenes (the layers you work with in the interface are translated into nodes to be rendered) so I don't think you have a case that being node based automatically makes it slow.
I personally find node-based interfaces to be VERY intuitive to work with.
That said, I also think node-based interfaces are most optimally applied to non-destructive data pipelines, while the Affinity products by nature are organized around destructive editing, particularly of pixel layers, so I am suspect of this request as a general interface mechanism for the Affinity products - though an image processing filter from within the Affinity products that allows a node-based approach to defining a custom filtering algorithm could potentially work quite well.