fde101

To put some context around this, one of the highest-performing Android tablets out there right now is the Galaxy Tab S6, which has a roughly $650 price tag (Wi-Fi 128 GB model) and an OpenCL score of 2299. The 6th gen iPad (Wi-Fi 128 GB model) - not even the iPad pro - has a Metal score of 2793 (its equivalent to the OpenCL score for Android) and a price tag of $429. Granted that the multicore (CPU) score on the Tab is 2468 compared to 1405 for the iPad, but from what I gather the Affinity apps on the iPad depend much more heavily on the Metal performance (which would translate to OpenCL on the Android tablets) than on the CPU performance - and an iPad pro (granted a fair bit pricier) has a multicore CPU score of 4604 with a Metal score of 9149, neatly trouncing both of them on all counts. When you look at the more "affordable" Android tablets (since your concern seems to be with the price of the iPad), the numbers look much worse for Android: the $330 Asus Zenpad 3S 10 has a multicore score of 762 and no OpenCL support at all apparently (as the score is marked "N/A"), while the $450 Galaxy Tab S4 shows a multicore score of 1489 and an OpenCL score of 1743. In short, by the time you have something comparable to the performance of the iPad in the form of an Android tablet, you are actually paying more for the Android tablet than for the iPad. If you are hoping for an Affinity version for Android in an attempt to save money compared to the iPad, you either won't be happy with the performance or will need to invest in a tablet that will wind up costing more than the iPad would have anyway.

Yes, in Designer there is actually an option to switch between the two modes (pixelating the preview or scaling it to show it sharply) but Photo is locked on the pixelated view, very likely for the reason suggested here. This has come up numerous times on the forum.

I wonder if something like this could be connected to the history panel somehow... Hmm...

Considering that Serif's offices are closed right now for the holiday season, it won't be at least until they re-open... probably longer.

You can also set that on existing threads after the fact using the "Follow" button along the right side, toward the top of the page.

In this situation that user has something to add to the discussion, so the added post should be more detailed than simply "+1". I have much less of a problem with that than with simple "+1" posts that add nothing else. I agree that there have been times when I wished I could "like" a subset of a post, and looked for creative ways to work around that by providing some context to my response when I replied. If someone agrees with the revised information from such a post, obviously they can "like" that instead.

The best way to handle this is likely to "like" the post requesting the feature. That provides a numeric tally of interest without cluttering the forum with useless "+1" posts that waste everyone's time.

This has already been requested in numerous other threads.

In some ways this will depend on the nature of how your styles are structured and the complexity of the document's design, however. Since you can inherit from non-group styles as well, you could just as easily (in your example) placed all of the information in the "Normal" paragraph style then based the "First" and "Last" styles on that. They could have inherited those properties from the Normal style and just changed the indent / decorations as needed so that you could have made your adjustments in the Normal style and the others would have followed suit. I do think that your use of the group style makes the breakdown a bit more clear however, and particularly if this structure is being used in combination with other styles in a more complex set is likely worthwhile.

I believe that has been requested for the Color panel, while my comment was targeting the Swatches panel. I suspect tint is more important to add to the swatches panel, while noise makes more sense to increase the visibility of on the Color panel.

I agree, this could definitely be handled better.

In that same place, make sure "Show Lines in points" is turned off and the stroke widths will be displayed in the units selected for the document rather than in points. Note that you can enter them in any supported unit regardless and the program will convert as needed (if that option is on, you could enter "0.001 mm" and that will be converted to points for display). Note also that you can be more precise than what is being displayed: if only one decimal point is showing, entering "0.001mm" as the line width will still work, even though it is rounded to "0 mm" for display purposes. You can then verify this by increasing the number of decimal places (using the option pointed out by @Pšenda) to 3 or more and you will see the full value when the object is selected.

They are base styles which provide something for other styles to build on. You would use them to set up common style information to be used across a family of styles, then create other styles based on them which override specific characteristics of the base style. You can do the same thing with other types of styles, but those would show up in the lists on the context toolbar (for example) in addition to the Text Styles panel. Group styles only show up in the Text Styles panel and cannot be directly applied to text. In short, the only real difference between the types of styles is what they can be applied to: Group styles - can't be applied to anything Paragraph styles - are applied to entire paragraphs Character styles - are applied to text within a paragraph (which may not be the entire paragraph) Additionally, paragraph formatting options are not available when editing a character style (as they would not be applicable). Each style inherits from any style it is "based on" all the way up the hierarchy until the special "[No Style]" of the appropriate type is reached. The selected character style for a range of text overrides what is in the paragraph style applied to the paragraph containing that text. Local formatting (if any) overrides both. Exactly one paragraph style can be applied to a paragraph at any given time, and exactly one character style can be applied to any particular character at any given time, though either one might be the special "[No Style]" (which acts more or less like a style which does not derive from anything else and cannot be edited).

Granted, but the problem is that users are already complaining that they feel there requests are being ignored (they are not). If Serif were to implement a system like this, users would expect the votes to set a priority of some kind. In cases where features depended on other features that had fewer votes, or might not have even been in the catalog, if Serif starts rolling out features that are prerequisites for the high-priority features users will start to question why the priorities set by the votes are seemingly being ignored. If high-priority tasks (as per the votes) are ones that take a long time to implement, and other lower-priority ones keep coming up, users again might start to believe their votes are being ignored. In the end, because of the fact that Serif is trying to steer the products in a particular direction and not simply catering to popularity with a user base, a system like this is more likely to lead to additional frustration and complaints and I would expect it to backfire.

Unlikely, as many of those customers have likely purchased through the Mac App store for example (or the iPad app store), and Apple does not share that information with the publisher of the software.

Hi @Charris, welcome to the forums! Studio Link is only available to allow access to the main persona from each of Photo or Designer from within Publisher at this time, assuming they are owned. It requires all involved apps to be at the same major version (currently 1.7 for the released versions), and does not work between betas and released versions.

No, mostly just curious at this point - but definitely something I may check out later on. Thank you!

I hadn't come across Noiseware Professional before. Another big noise reducer for photos is Neat Image, which does not appear to have this feature either, and the pro version is the same price as Noiseware Professional. Does Noiseware Professional generally work well within Affinity Photo (as a plugin)? Neat Image at least has a standalone version so that if the plugin support breaks in some version of Affinity Photo it could still be used separately; it doesn't look like Noiseware Professional offers that.

This appears to be a possible duplicate of this existing (and very long) thread:

If you go back and review the purpose of his request, it was to reduce the "wasted" blank space in the panels by combining them in such a way that reduces the redundant features and crams things closer together so that they do not occupy as much space on the screen. Placing the existing panels side by side only serves to emphasize the "wasted" space so I don't think this is an answer to the perceived problem he was presenting.

You might be able to use expressions like "+=15" in the fields too but I don't have it in front of me to check right now. Many of the numeric fields in the Affinity products accept expressions like that.

If I am working on something using swatches, most of the time I will set up my swatches at the beginning, then just about the only thing I would use the Color panel for would be to adjust the Tint of a selected spot or global color, so for everything else it would be wasting space. If I am working on something using the Color panel significantly, chances are I am not using swatches. If anything I would like to see the Tint option added to the Swatches panel. There is enough room that if the Opacity control were slid up a bit it could fit underneath and work the same way without making the panel any larger. At least for my way of working, I don't think any other changes are needed here, and I think the rest of the division between the two panels is ideal.

To take this a step further, considering making it a symbol and having your "duplicate" layer being a symbol to which the levels adjustment is applied. That way if the original shape is modified the shadow will reflect those changes.

There were destructive modes available in the crop tool in the early 1.7 betas, but in 1.7.0.105 they were removed, with the comment "for now - will revisit":

Only when the target color falls precisely on a channel boundary.