Andy05

You can create a single label in Publisher and use the page-number feature on that. Change their style to one with leading zeroes. Create as many pages as you need labels. When printing, use the N-up feature in order to print multiple pages onto one page. You might have to adjust the original label's size so it includes the margins needed for getting placed correctly onto pre-cut label printing papers.

It's a font disk (Bauhaus Lt. and Bd., Ultra Bodoni standard and It.) for an AM International Varityper Comp/edit Phototypesetter.

HDR merge might be an option for this task. EDIT: @firstdefence's suggestion about blend options also works, just needs some fiddling and soft masking. Quick'n'dirty test:

Hm. "vector brush" is a strong competitor, isn't it?

Yes, that'll work as long as you don't change the operating system (Windows vs. IOS vs. iPad and vice versa). The licence allows you to install it as often as you want to on as many PCs you own.

Maybe it would be good if you could share (a part of) the document. Because right now, it's just a stab in the dark from me. This problem might occur, if some transparency effect is under- or overlaying parts of the text.

Now I feel old. Anyone else remembering doing layouts without any early WYSIYG at all (whereas the "G" stood for "guess" rather than "get")? Anyone else remembering these things (I still have one lying around over here for sentimental reasons): I used to have some pen&paper next to my keyboard for taking notes about the layout (where is what column starting, where ending etc.) in order to save that expensive paper when developing the exposed parts in the darkroom later on...

I had the same problems. But for me it's working again now, after I deactivated and activated "take me to comments I haven't read" in the forum account settings (Content View Behavior).

That's complete nonsense, sorry. Because you basically stated that Affinity apps are not meant to be used for designing UI or Webdesign? As 1 pixel (or fractions of it) matter in both. Both are huge scopes of applications in design nowadays. An object, oddly placed in Affinity apps might cause some ragged or blurried output or other strange things, but a resized exported image can destroy a layout or—even worse—the issue will go unnoticed and later on, those objects are resized when displayed on a device not meant to rescale objects properly. Latter case might make it even harder to see what's causing the problems. Sometimes one has to see beyond one's own nose, there might be other sectors of design than the ones one is home in. 100% agreed on this at least on Windows systems and surely the same applies to Macs. (I don't have an iPad, so I don't know if their input fields are also big enough for displaying 2 decimal places as per standard.)

Doesn't make it any better at all. If a designer decides over an image's size, the software should not, never, in no way edit that by itself. Image size is one of the most important details when designing.

In his video, some parts appear also as semi-transparent. It seems like they are supposed to interact with other (semi-transparent) brushes in order to build some new objects.

That's what I meant earlier and why I disagreed with @R C-R in this point. I deem this behaviour a bug rather than a feature. As for moving the objects to full pixels, you can type the numbers into the transformation window (where you can see the odd numbers, just enter the correct number in there. And—this additional step makes it even clearer to me that this is a bug—you might also have to make sure, the dimensions of the objects and/or artboards are full pixels as well. So, basically not only playing their origin at full pixel coordinates, but also the dimensions should be full pixel and no fractions. In order to prevent such things, you can enforce alignments to full pixels when creating and placing objects in designer.

More help? You got the answer already, you need to position your object(s) and/or artboard(s) to full pixels instead of fractions of them.

Simple. Really. Because exact size of an image is something which is set on purpose in most cases. Whereas images not fully within those dimensions happen quite often.

Well, if they aren't here for doing their job - why are they here anyways?

Agreed. How often did hiding a post/thread happen in the past? I think, if someone has some really good reason for removing his posts/threats, there's always the option to contact a moderator.

True, but in that case it should rather crop the image than changing its dimensions.

That was an "Adobe"-EPS (Adobe puts proprietary stuff into those files). But here, all AI-files in the pack are also included as PNG. Also, the images don't look like they have massive gradients in them, which usually cause most problems when importing "Adobe-EPS". But it can't harm contacting Pixelbuddha and ask about the PNG's resolution. They should be good for display, but might be too small if the maps should be printed i. e. as a poster or package design. If it's about starting with designing some maps, free images from vecteezy might be an alternative, at no costs.

Well, like @iconoclast said, the PNG and suchlike will work. So all the illustrations (islands, buildings, sea monsters, vessels, etc.) are usable. Also the seamless patterns and grids. Those are actually the "more valuable" objects of the pack. As for the brushes, they are not that complicated to reproduce in Designer. (Even easier, if they have a preview bitmap of the brushes in their pack.) They'll just not be true vector, but that shouldn't matter that much in this usecase. So the pack is quite useful for creating various maps, just the "drawing" of own shapes is restricted unless you recreate the brushes.

Well, Affinity Designer doesn't support vector brushes at all. You can't even create your own. The current "vector" brushes are bitmaps, which follow a path (except for one or two simple, circled brushes IIRC). So before buying, you need to consider whether the other stuff in the pack provides what you searched for.

The only problem might be that the (probably most interesting part of this pack, if one wants to be creative) vector brushes won't work.

That was me replying over there at reddit. Unfortunately, especially when it comes to having gradients in EPS files, the stock pages are way too much focused on Adobe's methods of how to implement them.

I hope it's ok, that I blow my own horn...

This might be even easier to do, if you separate the text line per line: copy layer with text/logo hide all other layers So far, so good. select the copy layer (if not already done, make the text black and no stoke/styles), make a duplicate. Move duplicate by 1px to the right and 1px down. power duplicate (ctrl-J) as often as needed merge visible, now you can delete or disable all copies. create a container (i. e. rectangle), filled with a gradient apply a (non-destructive, so you can edit it whenever you want) noise filter Make sure, the merged pixel layer is above the rectangle, then use the pixel layer -> mask to below. activate the original text layer again. Done. Main benefit is that you can always edit the amount of grain and you can still change the gradient as you wish. And you have only 1 pixel layer) as mask which builds the shape of the shadow and 1 full editable fill layer for the appearance of the shadow inclusive its blend modes or "fancy" stuff like filling it with an image instead of a grainy gradient...

Just a random shot - did you connect the table via an USB hub? Because that might cause trouble (been there, done that), if you don't plug it directly to your PC/Laptop/whatever. Can you see it in your device manager (it should be under input devices, HUION HID). Other than that, I suppose the only issue might be Windows 7, which isn't officially supported any longer. Though the HUION website doesn't mention anything like this, it actually gives even a guide of how-to uninstall the driver correctly on Windows 7. What's with the driver's setup panel? Can you use the pen there (in the testing area to setup pressure tolerance etc.). That'd be the most native location to test the functionality I could think of.