mbuchichio

no no no, thats overkill! and not-done in Indesign. I'm talking about all other colors except standard black. What if you have a color swatch 50% black, sometimes you want to knock it out and sometimes you want it to overprint. Making 2 swatches is way to much work, just select the object you want to overprint and set it to overprint in the attributes panel. That's the way it should go and not set per color swatch…

You do not always want a color to global overprint, sometimes, you just want one element to overprint, nevertheless what color it is in.

This is a huge disappointment. I agree that innovation is a desirable thing. But, as other pointed out, basic features like global layers, used for ages in other DP apps, should be taken seriously into consideration. I really regret investing my money in Publisher. I guess I'm stuck with Indesign after all. Really sad.
And that is not the only gripe I have with Publisher. I won't go into all of them. The layers issue is big enough for me. But the styles sheets and color palettes are also problematic and confusing. Or at least over complicated.
I didn't start with DP yesterday. I work on this before computers were used in art departments, for crying out loud. And have been using DP since the early nineties. So, I kind of know a couple of things about what is expected from a desktop publishing app. I see the logic behind the single document concept that Serif took. But that just don't work for everything.
Best of luck.

Sorry, only someone who has never worked properly with InDesign can claim this. Too bad that I have to defend InDesign here. All I really want is for the Publisher to get basic functionality, without which professional work under time pressure is unfortunately not possible.

@Pixelkobold: The Layers in ID show the objects of the site too. But they are working across the whole document. My englisch is too bad to explain the details. I am working for 18 years with ID. Itˋs Layer Concept is much more better than Publisher´s layers.
 

You remember incorrectly. Layers are at the document level, not per page.

@ Walt.farrell: We do not need global layers for static objects, as commonly used in master pages, but for flexibel variations in design and content. These can not be activated simply by changing the master page. Am I right in assuming that you are not a designer or layouter? I really hope that some people from Affinity also work in the industry, because if Affinity stays with the current concept, the publisher will not succeed and its users will be limited to hobbyists and occasional users.
Your Example is not working in the real world, Walt.
Maybe someone is here with better english skills who can explain the issue?

Pleeeeeaaaase Affinity, give us global layers that work across all sites of a document. Professional layouters can live without site-specific layers (all Adobe-users and Quark-Users do that!), but almost nobody would work seriously without global layers. 
A layout application has different requirements than an illustration app. Avoiding much-needed features just for easy compatibility is the wrong approach.

As a layout artist you see your project as a whole. Not as a collection of single pages. For the latter one better uses a illustration app like AD.
I consider it's a big mistake adopting the level concept of AD and AP for AP.  Most layouters use layers primarily for alternative designs, which can then be faded in and out with a single mouse click. Exactly this is not possible with AP and its current layers concept.
I know, it is difficult to change, because AP should be compatible with AD. But maybe you could bypass the problem by offering the option to mark selected layers as cross-project. This could be a publisher-only function.

I also "just set up an account on this forum specifically to make this request " :)
 
Other users already explained the matter in detail so I won't do that.
Suffice to say that GUI and usability are quite sensitive topics and this it is a really important subject.
Please give the user the option to choose the UI brightness.
 
Thank you all.

I also "just set up an account on this forum specifically to make this request " :)
 
Other users already explained the matter in detail so I won't do that.
Suffice to say that GUI and usability are quite sensitive topics and this it is a really important subject.
Please give the user the option to choose the UI brightness.
 
Thank you all.

I also "just set up an account on this forum specifically to make this request " :)
 
Other users already explained the matter in detail so I won't do that.
Suffice to say that GUI and usability are quite sensitive topics and this it is a really important subject.
Please give the user the option to choose the UI brightness.
 
Thank you all.

I also "just set up an account on this forum specifically to make this request " :)
 
Other users already explained the matter in detail so I won't do that.
Suffice to say that GUI and usability are quite sensitive topics and this it is a really important subject.
Please give the user the option to choose the UI brightness.
 
Thank you all.

I also "just set up an account on this forum specifically to make this request " :)
 
Other users already explained the matter in detail so I won't do that.
Suffice to say that GUI and usability are quite sensitive topics and this it is a really important subject.
Please give the user the option to choose the UI brightness.
 
Thank you all.

I also "just set up an account on this forum specifically to make this request " :)
 
Other users already explained the matter in detail so I won't do that.
Suffice to say that GUI and usability are quite sensitive topics and this it is a really important subject.
Please give the user the option to choose the UI brightness.
 
Thank you all.

I was not aware that this was not possible.
This is an absolutely must have basic feature.

I also "just set up an account on this forum specifically to make this request " :)
 
Other users already explained the matter in detail so I won't do that.
Suffice to say that GUI and usability are quite sensitive topics and this it is a really important subject.
Please give the user the option to choose the UI brightness.
 
Thank you all.

While I do agree with you and what you've outlined. I cannot help but think that if AD could use the sets that can be created in FontBook (which I've seen other apps make use of, btw) it would eliminate a number of issues while giving the user a nice consistency between different apps.
 
Different sets in FontBook can reference the same fonts. For example, I have a set called Comic Dialog, which contains all the dialog fonts I use for comics. Then I have other sets, UC-LC dialog, which has only comic dialog fonts that use Upper and Lower case letters <-- and this set contains fonts that the basic Comic Dialog set has. So by using that info (or similar info from apps like, Suitcase fusion for example) when it comes to displaying fonts could be very helpful and save a bit of work on the user end. 
 
For me, any kind of automatic font assignment would, most likely, be customized ... a lot.

Good point. If the metadata is really problematic, the automatic categorization would work for default fonts only. And perhaps for those fonts with no issues during AD's categorization process. For the rest there might be another category, for instance 'uncategorized'. When user opens AD after installing a new font, he is asked if he wants to manually categorize fonts which were not recognized.
 
I believe some order in list of fonts would really help designers be more effective and a bit more conscious when thinking about type.

In the apps that support it and FontBook itself has had the ability to create custom font sets since, I believe, OS X 6 or thereabouts. I have sets set to contain Comic Dialog, Comic Sound FX, Display, Sans serif faves, serif faves, and so on. ComicLife 2 and now 3 calls up the Mac OS font thingamabob (at least that's how I think of it. Because, artist here) and the sets are there. so there has to be a way to incorporate these "sets" in a panel/dialog/whachamacallit for easy utilization by the user. This would be, imho, the best way since these sets would be system-wide and not change (or be dependent on memory to recreate each time) from app to app.
 
so +1 (conditionally on the above) for this.

Everything is written for it apart from the colour chooser on the document preferences dialog :D
 
I'll see if I can get it done..
 
AndyS

Hello,
 
I would like to propose a feature request so that one can easily manage which font collection (NSFontCollection) are available in the list of fonts.
The main purpose would be to hide all unwanted fonts from the font list in Affinity Designer.
 
Thanks.

I know all about whatthefont :-)
I use it l a alot. But that only provides me with the best candidate for the font family used. It will not OCR anything.
Performing an optical OCR seems a lot more complex because the engine does not know in advance what type of characters (serifed, non-serifed, slanted, bold, etc) it will be recognizing.
Having the outlines available, it would be much easier (not easy, but easier).
And the outlines are available, on the installed fonts.
 
But the suggestion by mbuchicio sounds feasible and powerful.

Actually, what could be done is that at the time of the type to path conversion, the text object could be 'stored' as hidden data for the path group in some way as to have it available if you change your mind, so you could always revert to the original text, this obviously should happen behind the scenes, and not activated by the user.
Or even better, maybe have a live 'convert to path' filter to manipulate the path and keep the text attributes 'live' to have both worlds.
That would be great :)

It was suggested a couple of times... it's useful when you don't want all the time to work with relative distances :) but absolute ones.
 
It was suggested too the "smart object distance" (a kind of) to make easier the workflow with AD.