Andreas1974

The far too littered and cumbersome undo history it's one of the most annoying things with Affinity Publisher, that makes me not want to use it, as long as I have access to other software.
Is this any change to this in version 2?

Neither of which is a photo editing app, neither of which as far as I am aware has a desktop presence. I am not sure of the point you're trying to make. I don't know the target markets or tooling either vendors (or Serif) have which might make it more of a sensible business decision for one or the other and how much legacy code they've had to port.
All of this is my point. It might look easy to do cross platform software development (in my experience not, and my very limited and ancient experience with mobile devices even less so), and yes there are more and more toolsets to help it get done but without knowing the ins and outs of it then the assumption that seems to be being made that (a) it's easy & therefore (b) Serif must have some ulterior motive not to do it just doesn't hold water for me.
I think that if it were low hanging fruit they'd have plucked it by now.
As I've repeatedly pointed out I'd LOVE an Android tablet version of Affinity Photo.

The far too littered and cumbersome undo history it's one of the most annoying things with Affinity Publisher, that makes me not want to use it, as long as I have access to other software.
Is this any change to this in version 2?

Tell me about it! It drives me nuts! And no, it works the same way in version 2. At least they could give us an option in the settings to disable this stupid thing. Not sure why the developers are so hardheaded!?

According to the Boost documentation, [[:lower:]]/[[:upper:]] are case classes that are "class names [that] are always supported by Boost.Regex."
The case sensitive flags are used for "literal strings" to allow, or disallow, case sensitivity.
Pretty much as simple as that, Walt. Now we could go on arguing what those statements mean and how they apply to APub...but that's mostly meaningless without one of the developers stepping into this discussion and explaining the rationale of their implementation of this/these features.
We seem to simply disagree on how case classes are implemented and APub's requirement to also add the case flag sticky setting to do what a case class is intended to do without it.
It's not a big deal in the larger scheme of things--unless one is coming from other applications that interpret/implement the Boost library differently. In the case of APub, there are X number of people coming from InDesign (and others) where such a flag (Match Case) isn't even present as the person doing/constructing the regex is expected to follow Perl/Boost regular expression syntax.
So when such a person is expecting Perl/Boost compliance comes to APub, threads such as this will be written wherein you (or others) can feel free to write the explanations of how to do it in APub. This will/may be more an issue if/when scripting ever comes to Affinity applications.
OK. Now I'm really done flogging this dead horse.

Seems like we're going around in circles.
Yes, my text editor also has a match case switch. But it is unneeded (i.e., it doesn't need set to on) if I use a Perl case flag such as APub requires. My text editor also doesn't need the case sensitive flag when using an explicit case construction such as [[:lower:]] or [[:upper:]].
I don't believe any other option--especially a half-hidden option that is sticky--should be needed in APub. You seem to shrug your shoulders over APub's inability to comply with the Boost library. So we differ on our opinion in this regard. So I'll leave it at that.

If you click on the placed PDF you can select a page in the context menu on top.

Another +1 for this with the addition that the layers panels should show whether the image is linked or not, as this is something I would like to be able to see in conjunction with this feature.

Another +1 for right click reveal in Explorer/Finder, and "following".

Look through your document to find the image you want to replace, then click on it with the Move Tool to select it. You should see a "Replace Image" button on the Context Toolbar.

It took me a while to figure out how to show details about my linked files since there is no Links palette in Publisher like there is in Adobe apps.  It seems that Linked file access in Affinity Publisher is restricted to Document > Resource Manager.  Fine and well, but how do I perform a Reveal in Finder command like we can easily do in Adobe apps?  (In Adobe apps you can right-click on the graphic to get the Reveal in Finder command, or do the same through the Links palette.)
Thanks.

Hi Kobold,
It's already possible to choose the number of decimal places you want to display with the latest Beta. You can get it from here (usually pinned at the top).
You can find the settings in Affinity Designer Beta ▸ Preferences, User Interface section, Decimal Places for Unit Types.

That's part of the problem but it still exists with a docked studio panel. However, I've confirmed the floating part of your bug.
If Find and Replace is floating and closed, Text>Find or Cmd+F sets focus to the Find field If Find and Replace is floating and open, Text>Find or Cmd+F does nothing If Find and Replace is docked, Text>Find or Cmd+F usually sets focus to the Find field but not always With regard to the docked version of this bug, few bugs are truly intermittent so there is a certain sequence of steps that must be followed to trigger it. The obvious candidates are whether the studio panel is visible or not, which field in the panel last had focus, whether a different studio last had focus, which tool is selected, etc., but I've tried all of those and haven't been able to duplicate it on demand. I'll keep an eye out for the next time it happens and see if I can then come up with repeatable steps. Once we've figured this out we can move this to the Report a Bug forum.

I second this. I accidently edited the text instead of searching without noticing.

The screen shot of the History pane was just for illustration purposes.
This is my feature request and it's is primarily about being able to use the Ctrl-Z shortcut in an efficient way, just as in most other programs. My word processing software does for example not include every cursor position or text selection in it's undo history – it's not relevant, since there is no change.
You think it's a good idea to let the user decide what should be selected.... I can't tell what would be selected when I look at the history panel. It easier just to select the object again, than to find the correct selection in the history pane. I see no point in using the history panel for returning to previous selections. 
There would be no "guessing" from the application involved. Why would it? My suggestion is that Affinity Publisher was to back to (and including) the last change. The selection changes in between (in the history panel) do not even have to be seen by the user, unless there is something I don't grasp at all. There probably is, since you like the selection changes to be part of the undo history.
Even if I were to use the history panel, what's the sense in looking through five irrelevant entries of "set selection"? They take up a lot of space, making the relevant parts (the actual changes) harder to find.
With my request the user would just get back to the same state as before the last change. Compare with InDesign or Word.

When I am adjusting the layout, there are often times I need to see the layout without the selection boxes... this is fine until I need to make a few comparisons. I use the Undo/Redo actions for a before and after comparison but I can't because for some reason it was thought to be a good idea to include De/Selections into the Undo History. This makes it so if I Undo, and then select something, I've lost all my history I may have wanted to keep.

Can you remove this "feature" from the product. It's not great and makes me want to go back to Adobe pretty quickly out of frustration.

Nope. I guess when the devs closed this bug report as 'by design', they really meant it. Affinity has a pretty 'unique' idea of what constitutes good UX design at times. 😕

Hi all i have a big problem i was a AI and PS user for a long time and now with the 1.9 update  AFFINITY DESIGNER uses ALT + SCROL to rotate the Canvas(Project)
I used AutoHotKey to remap ALT=CTRL but is messy and can't remove curve points when creating a curved shape
I want to ask you guys if there is a way to remap :
CTRL+scroll wheel
 ALT+scroll wheel
SHIFT+scroll wheel
 
 

Looks like it uses a custom scroll amount - I'll report it

Hey there!
Anyone else have a very low scroll speed on the Pages Studio?
I mean, using the  Scrollwheel is a pain, at least if i set the Page Preview to small its working as intended.
(Using Windows 10, no special mouse software installed, 3 Lines per Scroll set in Windows 10)

Hey guys,
oh yes, thank you! I just thought I was the only one who noticed it was annoying to only get
one page forward in the 20 page document with a full pull.

I thought it was my mouse driver, but all other programs adapt or scale the speed accordingly.
Cheers
MrDoodlezz

On Windows, the scrolling is very sluggish and requires more scrolling of the mouse wheel than necessary. Please increase the speed at which all scrollbars move. I would like to see the "Pages" view adopt a scrolling rate of one-spread-per-wheel-click and the main document view to scroll at least 2x faster than it currently goes. 

scroll speed is too slow on pages

When I scroll over pages in the pages menu, the speed seems extremely slow. Anyone else experience this? IMO, it should be quicker.

I agree! I have all the apps on all platforms (Mac, PadOS, Win) - and the page scrolling (and navigation - compared to Mac) in Publisher for Windows is slow. I know that hardware etc. impacts performance - but I am comparing Publisher (on the same laptop - Win) with InDesign (that old dinosaur of an dtp) - and the scrolling in InDesign is actually better in my eyes! But that's about the only thing I prefer in InDesign over Publisher :-)

Thank you Syrehn for reviving this issue, since it's still present! Windows 10 here. You have found a solution that is simple. Just select "Run as administrator" in the Windows Start menu. I hope your discovery will help the Affinity programmers to find a permanent solution that requires no additional actions but to run the program normally.