gabriel_komorov

Yes I get it, but the line is drawn in questionable place. No one expects painting tools in Designer, but if we already have shape tools in Photo, so why not give full control on effects they produce, like stroke? It's just common sense. Spliting features just for sake of difference isn't best idea IMO. It works in layers panel, you can delete by dragging on recycle bin icon

Genereally idea of appearance is interesting, but in current state flawed by some issues: - When Designer file is imported to Photo, there's no way to change fill or stroke of shape with few appearances set. Why? Because there's no Appearance panel in Photo. BTW disparity between obvious features are baffling to me in Affinity. Why Photo misses Stroke Panel? Or why Designer doesn't have proper document preview implementation as Publisher? Etc. It's all doable in all apps anyway, only is long and unconvinient. - When Appearance item is clicked, then pressing DELETE key deletes... object. Seriously? - Appearance item can be dragged on recycle bin icon, but dropping it there doesn't delete it.

When Include printer marks > Include page information is checked instead of just filename and page number, spread / artboard name should be added also.

That's it! Thank you! This will be helpful too. Windows 10. Given above answers I'm curious what this option is supposed to do

Doesn't work for me too

View rotation is neat feature when working with some foldable designs, but it's implementation needs few tweaks. First - rotation is reseted to default when switching back from another document. Second - rotated view shouldn't change objects behavior. What I mean - rotate view by 180° and try to add text - it also defaults to rotated! Same goes for all dimensions in transorfm panel, arrange and align etc. It's very confusing. Just rotate view and leave rest as it works at 0°

Some files I work with contains groups of 100s of objects, what would be convenient - while clicking object on artwork layers list should jump to it. Because finding selected object on loooong list takes to much time!

As title says - when object is selected, then it's boundaries are highlighted with blue outline. But sometimes, especially when working with small objects or fine outlines it's impossible to see what's going on. Is there a way to disable it, so selected object is indicated only by handles? If not can you make it a feature request?

Nawet nieźle ;)

It's easier to operate on small values, also there will be no need to do math (yay) So let say I want to rotate object clockwise by 67 degrees. That's easy - just enter 67. But when rotating counterclockwise things starts to look more complicated. I must calculate 360-67 to know it's 297... damn 293. See? What about just entering -67, and moving on? (maybe I mixed directions, but general idea still holds up)

In patch / stamp and other similiar tools where source can be set, there's option to rotate it, but what would be also useful is flipping (mirroring). That's all folks. Thank you for attention.

Yeah, but this is exactly what such post will be for: - "X has currently lower priority, beacuse we've discovered critcal bug in Y" - "Still working on Z, we want to make Za and Zb ready before final release" I'm sure you have someone who can write exciting words about forgotten boolean or unnecessary if I know from experince that users can turn dev life in to nightmare, but also know that dev can change user's mind with interaction in right place

Things I mentioned as far simplier, really are... simple. I've written few lines of code in my life, and things like persisiting prefernces/settings are basics of basics, it's literally next thing you learn after "Hello World". Well, maybe he was upset after disocovering such extraordinary feature... Anyway, we can only hope that now, when Publisher is finished, they can focus on delivering what's missing I guess you can call it an attempt at sarcasm, but hey - at least we're talking now Thank you for your post, this is what we (users) miss - more transparent communication. It's far better to keep us updated, than telling that bug is acknowledged, and then go silent. Such assuring is what can turn frustration to patience. @MEB Maybe it's good idea to create pinned post, where once per month we can read about stuff you currently work on? Not any detailed descriptions, but something like @MattP posted. "This month we started to work on feature X. Y is coming nice, we' currently testing it. Dev was assigned to look at Z and he already wrote some code" You know - such heads up, so we know that you really listen and care

I would say this is critical bug, however is it also more complex? I don't know, but you acknowledged it many, many months ago, and at this point I have theory that it's your petty revenge on users for their critique/demands. Above is also true for a lot of other, far simplier requests - workspace manager, sticky preferences, more intuitive settings screen etc. Petty revenge I say. How reporting a bug is ridiculous or clownish?

I can only imagine horrors of registration you've been through