rubs

The file was made in a previous 1.7 Beta by a colleague, but he doesn't remember if there was any saving errors. We never tested Publisher, nor opened the file in any other app then Designer. What might have happened (can't be sure at this time) is that this particular file was created by editing a previous AD 1.6 document. Fortunately we keep several previous versions of all our work.  I've just uploaded them for you to check:
v01-v03, apr 4-9, no errors. v04, apr 18, smaller file with error, maybe with the pixel layers were lost here. Perhaps you can find what's missing by comparing versions 3 and 4.
P. S. I wish Serif support was always so quick to respond,  thanks!

hello, just wanted to note something less about the program but rather about the beta test itself apparently with the re-branding of 1.7 there are no beta specific icons anymore and even the title you can see in the taskbar just says "Affinity Designer" which makes it really ugly since there is only one true place where you can see that you are in the beta and that is the splashscreen which is also used in the about panel.
 
I think this can easily lead to confusion for people who use both on the same machine and should be fixed sooner or later.

Sorry, this quote is from the 1.7.1.385 Customer Beta changelog. I didn't understand why Designer would have page navigation, but @Mark Ingram explained it.

If you open an .afpub file, Designer will allow you to navigate through the pages (previously it only ever showed the first page).

Sure, that's what worries me. Another release and most old problems are still there.
Oh, certainly not. To quote a friend, only obsolete software isn't buggy  I refer to those "old time favorites", things that just don't work as expected for years. You know, the ones you've never fixed and are not answered by Serif. Some of them, from the top of my head:
Complex boolean operations Constraints (lots of issues with those) Expand stroke Selecting then moving several artboards Symbols Objects moving inexpectedly when grouped / ungrouped Continuous export Sluggish search in assets 1980's style text tabs UI Performance problems in the Windows version And so many more...

Good to know that, much needed. But please make it case-insensitive again, otherwise we won't be able to find our assets. Thanks for answering.

Hi rubs.  Asset searching was rewritten to improve speed. (It used to re-populate the entire control on each key press but now it uses an index which is much quicker). However, I did indeed make it case-sensitive too. This can easily be changed though.

Sure, that's what worries me. Another release and most old problems are still there.
Oh, certainly not. To quote a friend, only obsolete software isn't buggy  I refer to those "old time favorites", things that just don't work as expected for years. You know, the ones you've never fixed and are not answered by Serif. Some of them, from the top of my head:
Complex boolean operations Constraints (lots of issues with those) Expand stroke Selecting then moving several artboards Symbols Objects moving inexpectedly when grouped / ungrouped Continuous export Sluggish search in assets 1980's style text tabs UI Performance problems in the Windows version And so many more...

Sure, that's what worries me. Another release and most old problems are still there.
Oh, certainly not. To quote a friend, only obsolete software isn't buggy  I refer to those "old time favorites", things that just don't work as expected for years. You know, the ones you've never fixed and are not answered by Serif. Some of them, from the top of my head:
Complex boolean operations Constraints (lots of issues with those) Expand stroke Selecting then moving several artboards Symbols Objects moving inexpectedly when grouped / ungrouped Continuous export Sluggish search in assets 1980's style text tabs UI Performance problems in the Windows version And so many more...

In version 367 RC2 (I'm not sure about previous ones) it seems that Assets search is case-sensitive now. I have an asset called "Balloon", but when I looked for "bal" it didn't return anything. "Bal" worked. I hope this is not intentional!

I don't know when, but based on what Matt has said, he should be taking a look at those two oldies, in the following months: Boolean Operations and Expand Stroke.
Best regards!

@Ben
Do you know when the boolean operations will be fixed or will they be fixed in the coming release? I know, it´s a little bit off topic in this thread.

It's an RC because at some point we need to update the official versions.  It's fine for everyone on the Beta getting new features, but a lot of user only take the store versions.
 
Also - you can argue that we should fix 100% of bugs before doing an RC - if that was what we were aiming for, we'd never release.  Believe it or not 1.7 has addressed a lot of bugs from 1.6 and earlier.

Sure, that's what worries me. Another release and most old problems are still there.
Oh, certainly not. To quote a friend, only obsolete software isn't buggy  I refer to those "old time favorites", things that just don't work as expected for years. You know, the ones you've never fixed and are not answered by Serif. Some of them, from the top of my head:
Complex boolean operations Constraints (lots of issues with those) Expand stroke Selecting then moving several artboards Symbols Objects moving inexpectedly when grouped / ungrouped Continuous export Sluggish search in assets 1980's style text tabs UI Performance problems in the Windows version And so many more...

Symbols losing connections is an issue that has led me to not using symbols at all, for example (because I don't know when or how the connections get lost)

I've learned to live in harmony with bugs. Top two Classic Bugs since Day 1 I Started using Affinity Designer:
1. Symbols will mysteriously lose connection
2. Mouse click Offset (ctrl+ click causes replication)

What bothers me everytime I see those little RC's appended to the version numbers is that all the old bugs and problems from years ago are still being ignored. (Shouldn't we call them "classic" already?)
Oh well...

Hello!
I have a suggestion
Add the ability for artboards to always have integer values for position and size.
At the moment, fractional values in the arbord position are very disturbing. If you do not return the integers, during the export of artboard, the image is exported with the wrong size.
I can't imagine when artboard may need fractional values. This only creates problems in the work.

@Sean P
With reference to my earlier post… 
https://forum.affinity.serif.com/index.php?/topic/36293-by-design-ad-symbol-name-does-not-update-propogate-on-rename
The behaviour regarding symbol names seems to have changed.
1. Create a shape
2. Make it into a symbol
3. Duplicate the symbol a number of times
4. Rename one instance of the symbol
Result: All instances of the symbol adopt the new name.
5. Rename the symbol via the Symbols Panel
Result: none of the symbol instances are renamed.
6. Drag several instances of the symbol from the Symbol Panel to the canvas
7. Rename one of the new instances
Result: all of the new instances are renamed, but not the original set of symbols.
---
Update: Mouse over tool-tip now shows "Name" as something that can be un-synced with symbols, so I guess that this is 'by design'?
However, if that is the case then the behaviour seems inconsistent to me. Renaming the symbol in the Symbols Panel should update the name of all instances where the Name property has not been un-synced.
Also, this is the only property that can be un-synced without first toggling the Sync button in the panel. This is good from ease of use perspective, but is inconsistent with default behaviour.
 

Thanks for listening, and thanks for your answer. AD is my main design tool, I use it on a daily basis. I'm a big advocate of it among fellow designers, and I've already produced hundreds (thousands?) of work files with it. So I'm not going anywhere soon  But I feel it's important to know whether these showstoppers will be addressed or not (and when), but I'm not seeing any answers.
Please look here for more thoughts.
Thanks again.

This is getting old... I secretly hoped they would fix constraints for 1.7.

@gbrampage
Welcome to the Serif Affinity forums
Sorry, this problem was introduced in this latest beta. I think it only happens when the drag starts outside of an artboard. It was an unintended consequence of fixing not being able to drag select multiple artboards, and will be fixed very soon, hopefully in the next beta.

Right! That's probably because Windows is in pt-br and Affinity Designer is set to en-us. (Serif's Portuguese translations are quite bad.)

64° 30′ NB, 165° 24′ WL

If you have enabled Snapping to the Pixel Grid, and disabled Move by whole pixels, then you should be able to use the move tool to move any artboard and it will end up pixel-aligned as required.
However, I agree that either the Artboard locations should be shown in global pixel coordinates, or Serif should fix the issue with exporting items that are not aligned to the pixel grid so that the export works properly as long as the items have integer pixel dimensions.