Butler To Cats

I believe Serif is a small company (80 people, I don't think they have 24-hour forum support) running on UK time. Might be worth waiting until they get into work.

I think it was in the Sherlock Holmes stories that this is mentioned as a mark of genius: clear ideas, obvious to hindsight but not to foresight. Thank you for sharing!

Ah, now I understand. Canvas/image area only, no controls, panels, or tools. Nope, don't think you can currently do that, but might be worth submitting it in the Feature Request part of the forum. I suspect it will need new app-specific code rather than existing iOS or Affinity Photo features.

See this thread:

HDMI monitor, cable, and Lightning Digital AV adapter? https://www.apple.com/shop/product/MD826AM/A/lightning-digital-av-adapter See the reply on https://discussions.apple.com/thread/8202375 for a little bit more background on how it works.

Try turning your iPad completely off and on again (especially if you have recently installed the iOS 11.2.6 update). According to a DM from another forum member, doing that made the Affinity update available to them. (Feel free to jump in and claim credit, you know who you are, as I'm hesitant to name a private communication.)

Probably not telling either of you anything but, for the benefit of other readers, using the site option in a Google search can be helpful. e.g. In Google search for "vector brushes" site:affinity.help (the quotes find a specific multi-word phrase rather than also searching for the separate words) or even "vector brushes" site:affinity.help/designer Leave out the quotation marks if you have only a single search word or don't know the exact phrase e.g. boolean site:affinity.help/photo

Ouch! So much for that hypothesis. (Unless ISP caching, device availability variations, server load balancing, or other factors also come into play, as well as simple timezone factors?) Tough luck @kwarn - I hope it becomes available soon for you and all the other users.

Just ran across this. You can add Dropbox to the default locations list in Files and hide iCloud - assumes you have already installed the Dropbox app on your iPad. https://www.igeeksblog.com/how-to-add-dropbox-to-files-app-in-ios-11-on-iphone-ipad/

I wonder if update/release availability in the App store follows the international timezone? The update was available in the App store from eastern Australia this morning (about 4 hours ago at the time of writing), and we're fairly early in the queue time-wise (not far behind our neighbours in New Zealand who are right at the beginning). A quick Google search finds a few pages suggesting this might be the case.

I suspect Affinity Photo passes the location selection to the iOS 11 Files app, so I am not sure that can be changed. The good news is that you can already add Dropbox to the list of default locations in Files. See https://www.igeeksblog.com/how-to-add-dropbox-to-files-app-in-ios-11-on-iphone-ipad/ (you can even turn off iCloud from appearing).

I think you have full control, you should be able to choose where to download them at the time when you click the Download buttons/links - on your iPad storage, or on an online storage account (although I think iCloud is the default for an iPad, you might have to go through Other Locations or something if you have Dropbox installed on your iPad - sorry, don't have my iPad with me at the moment). (You can have an iCloud account as well as Dropbox - might be worth considering for ease of transfer to/from your iPad - iCloud accessible from your computer at https://www.icloud.com/or you can download an iCloud app for Windows) You can even purchase/download through your computer (directly to a Dropbox-mapped folder, perhaps, although I would recommend saving the downloads to an unmapped folder first and copying them to Dropbox afterwards). Once you buy the (temporarily $0) purchase, you also get download links in your Affinity Store account (the Downloads & Product Keys section) for later access/downlaod. Not sure you will need an unzipper app, I think the downloads are already in unzipped .afbrushes and .afmacros format (and PDFs for instructions and licensing files).

See https://affinity.serif.com/en-us/ipad-update/ for the temporarily free content released to match the timing of the iPad 1.6.7 release, although (as per Patrick's post) I'm fairly sure this content will also work in the desktop apps, rather than being iPad-specific (with the disclaimer about the usefulness of the macros, so maybe only the brushes). Link to download just under the Buy Affinity Photo now button. If you reach What's Included, you've gone too far, you are into the description area past the download. Buy the (temporarily $0) extras, download and save on your desktop/laptop machine, and I assume you will be able to copy the content over to your iPad (probably via an online storage service, seems to be the easiest route) when/if you get an iPad. Other raster brushes for the desktop apps should also work on the iPad version of Affinity Photo (but not vector brushes until the iPad version of Affinity Designer is released). Even without a Twitter account, you can monitor announcements at https://twitter.com/affinitybyserif

When video card/chip manufacturers such as NVidia are dropping 32-bit driver support, this seems to support the Steam statistics that 32-bit Windows is almost dead for games and graphics users. Mac OS is also giving 32-bit apps an end-of-life warning.

Looks like Swiss customs issues might have played a role, with a new agreement in place where Swiss Post will do the clearance work for Amazon stuff. https://ecommercenews.eu/amazon-launches-switzerland/

The 2nd line I would read as "by G Horne & G Laylor" (that's Hor ne, not Home - very similar in the typed font on my screen)

See https://alternativeto.net/software/screentogif/?platform=mac for several suggested Mac alternatives (with various features) for ScreenToGIF.

Agreed. There's no (room for) ambiguity there. Admittedly it's an isolated edge case, a very small room (the smallest room in the house, perhaps? ), but maybe there is enough room to fit in a tiny amount of pleasing ambiguity. If the train to Nottingham has not yet arrived, but is visibly approaching along the track, and I'm sitting on the platform typing a reply to the Affinity forum, and a well-meaning bystander says "You should probably finish that up now", I think I can reply "Nah, no hurry, I am getting the next train to Nottingham", which might be ... the one after the "next" one. So much meaning comes from context, neh? My guess is that it's more about how a reader spread is displayed and labeled. I can see page numbers 1 (single right-hand page), 2, 6[maybe], 8[probably], 10, 12, 14, and 4 (not sure what's happening there), indicating that most of the odd-numbered pages are present but not labeled. So I'm guessing that rather than "Page 10 and 11", for example, both the label and the display show "Page 10" (with an implied "and yes, of course, page 11 but I'm not displaying that because you've set the view to show spreads, not individual pages. Change the view back to pages if you want to see each page separately). Of course, I'm guessing wildly from very little evidence ("'T is clear enough the Elephant Is very like a tree!")

First line in the description:

Maybe Patrick was the next Serif contributor. (Incidentally, @carl123, if the doors have just opened and the queue has just newly formed, is the first person in the queue still the "next in the queue"?) If the exact interface is not yet set in stone, a clearer recording may not be helpful. Besides, you don't want give your competitors too much of a heads-up before your product hits the market. Already I can see plenty in that sneak preview, along with the usual great Affinity interface design.

I blame the Normans for most of the spelling mess, those interfering French vikings. "Aluminum" is one of those odd mutations added to the US dialect by Webster, under the guise of simplification (although I can sympathise with his resentment of the mess the Normans added). I think xkcd, as usual, aptly comments on the result of Webster's work. In the US English dialect, Webster's change means that the weirdly USAmerican "aluminum" is now inconsistent with all those other metals that include an "ee", such as sodium, uranium, magnesium, titanium, plutonium, gallium, thallium, chromium, iridium, osmium, palladium, rhodium, selenium, vanadium, zirconium, hafnium, ruthenium, indium, cadmium, ... (I could continue for some time). Meanwhile, the rest of the world follows a more consistent path. On the other hand "aluminum" follows the pattern of ... well, there's platinum (apparently thanks to Spanish), and molybdenum (thanks to a Swede), tantalum (another Swede), and lanthanum (believe it or not, yet another Swede), and I think that's all. So, much rejoicing? (Mynd you, møøse bites Kan be pretti nasti) Regarding the probable beta release timing: For Australian English, "next Thursday" is usually Thursday of the following week, even if it is only Tuesday of this week. Older Australians might use "Thursday next" for clarity. However, when it is still winter then "next summer" is ambiguous. I like the look of the text flow, the drop caps, the multiple columns. Looking forward to the beta!

Welcome to the forums! You are too early, I suspect, as this thread reveals the earliest glimpse seen outside the in-house development team. In the first post TonyB states "expect the beta next summer" (Windows and Mac, by my understanding, if there's an iPad equivalent it will come considerably later), and Serif states on Twitter "It will be an open beta". The Twitter post also adds the hashtag #patience Regarding an iPad version, "We are not currently developing Affinity Publisher for IOS." It's not impossible "but we'd be looking at 2019 at the earliest." "All the info that we currently have is what you can see in video. We do not have any other publicly available information available. As soon as we have any news, we'll be sure to let everyone through our Newsletter, Blog, and social media channels." [RSS for the blog]. Regarding signing up for the beta, "There will be a link on our website nearer to the time." There is an RSS feed icon at the bottom right corner of this News and Information sub-forum, but it is not Publisher-specific, it will probably include any Publisher information amongst other news and information. Likewise, similar Publisher news will probably be included in the Serif Affinity Twitter feed, but it is not Publisher-specific. No Affinity Publisher specific feed (that I know of), and possibly no reason to have a public feed until a public beta is released (assuming there will be a public beta). When there is a public beta, I would expect a Beta sub-forum similar to what exists for the other public or customer beta versions, each with their own RSS feed. (Incorrectly added links, unclear phrasing, and misinterpretations, are all mine). Note: in the meantime, if you are a Windows user with an urgent project, I believe Serif's older PagePlus can create ebooks in both ePub and ePub 3 fixed-layout formats.

@thomas.artist Without any experience in the Silhouette software, but some knowledge of SVG and raster/vector issues and the information in @Busenitz's example (excellent selection of sample steps!), it looks like it might be possible in AD with a little more preparation work to simplify the situation - in effect, to create vector silhouettes for Silhouette Studio. The disappearing shape looks like a layer order problem in that example - SVG does not specify depth, so it might be easy to have shapes present but out of order, depending on the SVG file and the interpreting program. Depending on surrounding transforms, groups, and other SVG tags, a program that does not support the full SVG specification might also have trouble recognising that a shape exists inside a tag it does not recognise. 1. Make another copy of the AD file if you might re-use it in the future and want to make changes to shapes and textures. 2. Rasterise anything not needed as a cutting line e.g. the Happy Birthday text and inner black ring in your (Busenitz) other thread example, and also the white circle on the right-hand shape. 3. Probably not necessary, but I'm paranoid: If more than one rasterised layer for any single cutting shape, merge them. So the upper right circle shape, potentially merge the white circle down onto the outer texture layer. 4. The only real extra work: Create a vector cutting shape for any PNG or bitmap layer with transparency - do not reply on the PNG or bitmap transparency to create it. In your example, create a rectangle vector shape for the outline of the bottom right image, and a vector "ribbon" shape for the outline of your lower left image. Your upper left white circle should still be a vector shape, as should the outer circle on the upper right. 5. Another probably not necessary step: convert all vector shapes to curves. 6. Drag all rasterised/texture layers "inside" their appropriate vector cutting shape layer in the layer panel (so the vector shape also acts as an AD clipping shape). So, in your example, you have two circular vector cutting shapes, one rectangular vector cutting shape, one "ribbon"-shaped vector cutting shape, and absolutely everything else is a bitmap layer "inside" each corresponding vector shape. Your layers should now be a simple structure of: -cutting shape (vector curve layer) (silhouette) |__texture (bitmap layer) -cutting shape (vector curve layer) (silhouette) |__texture (bitmap layer) -cutting shape (vector curve layer) (silhouette) |__texture (bitmap layer) -cutting shape (vector curve layer) (silhouette) |__texture (bitmap layer) 7. Export as SVG. If you want to post an example .afdesign file, I'll modify it appropriately and re-post it with matching steps. If not, I'll fake up an example later tonight when I get home and get access to AD. Let me know if I've missed anything significant in the process.

In the same gardening theme, gourd help you if you are a Deaf or hard-of-hearing person trying to learn using the auto-generated captions on some YouTube videos (fortunately James's clear voice seems to transcribe quite well for Affinity videos)

While 0,0,0 for black is correct for RGB (screen, additive) work, this would be incorrect for using CMYK, which is a printing (subtractive) standard. RGB and CMYK have completely different uses and should not be compared. If you are not intending your output to go to print, do not use CMYK. Printing a dark ("rich") black commercially usually requires a mix of the coloured (CMY) inks in addition to the K (black) ink in order to produce a darker black colour on paper than you can get using only black (K) ink, which will usually only show on paper as a dark grey (true black printed inks are very difficult to achieve in practice with wet ink, ignoring powder/laser ink which has different issues). This why the printing industry uses the term rich black rather than true black (although you might see CMYK 0,0,0,100 as "plain black" - something commercial print customers might not be satisfied with on paper). With some papers (especially coated paper), producing a rich black on paper (without wetness problems) will require noticeably less than 100% K ink and a mix of the other C,M,Y inks. This does not translate exactly to RGB on screen, but in practice the CMYK you are seeing as RGB 32, 32, 32 on screen will produce a darker ("rich") black on paper than CMYK 0,0,0,100 (because of the practical lack of real-world true-black wet inks). Exact mixes of CMYK for "rich black" on paper will vary according to printer, ink, and especially type of paper used (which is why CMYK swatches in software usually specify the paper type) - consult your commercial print expert. As a subtractive (printing) process, the theoretically darkest mix with real-world ink would be CMYK 100,100,100,100 rather than CMYK 0,0,0,100 - however, in practice with real-world paper, this would be far too wet for the paper (with wet ink) and produces other issues with powder/laser ink. CMYK 100,100,100,100 is used for thin-line registration marks (the small marks and thin lines avoid the wetness problems) and is known as "registration black" - it will also show up any problems with CMYK alignment. Software that uses CMYK 0, 0, 0, 100 for printing "rich black" on paper (rather than "plain black") is telling lies about real-world printing conditions and real-world inks, and should stick to on-screen RGB where it is telling the truth.