Butler To Cats

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

No more than we currently have.  Some vector formats don't support elliptical, so we do a "fix" to radial.  So, they will be no worse than they currently are.  The linear gradient correction can easily be applied as it is done by fixing the key line.
 
All raster formats will be fine as we do the rasterisation.
 

I have another sneak peak for you.
 
This one might be a little hard to follow, but I'll try explain it best as I can.  Something that has always bothered me is when I put a linear or radial gradient fill on something, and then try scaling or shearing the object.  The gradient fill is unstable in that it doesn't track the object transform.  This is because linear and radials fills are positioned relative to two key points, forming a line through which the gradient is rendered.  Elliptical (and bitmap) fills don't suffer from this because they have three key points, forming a rectangle in two axis.
 
So, I decided we need to fix that. See this video: CorrectedFills.mov
 
The top objects have a legacy linear, radial and elliptical gradient fill.  You'll see that when I shear the first two objects, the fill kind of moves around inside the object and doesn't conform to the shear.
The bottom objects have a corrected fill.  When I shear these objects you'll see that the fills continue to adhere to their placement relative to their object.
 
I then show you some new handles that appear in the Fill tool, which show you the "correction" points of the linear and radial fills, connected with dashed lines.  (You'll notice that the elliptical fills appears the same as they need no correction).  These new handles show you when a fill is being corrected, and give you opportunity to place the extra correction points if you so chose.  You can double click the correction point handles to adjust the fill into a conventional linear or radial fill in document space.
 
Why is this important?
 
If I create an asset or a symbol, I can then place it, and transform it, and maintain the visual appearance without the fills distorting.  This is then especially useful for 2.5D drawing - I can use assets and symbols that were designed in 2D, transform them to grid plane (using the new planar tools coming in 1.7 which make use of shear and scale), and they will maintain their fills.
Of course, it is just generally useful, in that it kind of maintains a more WYSIWYG approach to gradient fill placement.
 
 
 
Just, don't ask about conical fills - they are going to take a bit more figuring out.

Yes it is.  The video shows exactly that.
 
When holding Shift to constrain direction, snapping instead allows you to snap the handle length.  If a single mark appears, you've matched the length of the joining handle (on the same node).  If a double mark appears, you've matched the length of the handle at the other end of the segment (like your A-B example).  Of course, it is also possible to match both, in which case the handle line will show both a single and double mark.

Like I said, you'd snap your direction first, then perform a second mouse drag while holding Shift to fix the handle length - then you'd have a perfectly symmetrical curve segment.
 
Demonstrated: SnapToReflectedPlusLength.mov
 
It has to be done as two separate actions, else you'd have two independent types of snap that would fight against each other. While it is another step, it means you'll have greater control over the curve.  Since we use Alt to cancel snapping outright, you might otherwise end up fighting against snapped lengths while all you really wanted was to fix the direction.

Ok, Here are some videos to demonstrate all the snapping that I've added for handles.  Please note, I'm not talking about snapping to grid, I am talking about snapping to useful construction angles relative to the opposite curve point and handle.
 
So, the following snaps are shown:
 
1) Snapping to smooth a cusped node - SnapToSmooth.mov
2) Snapping to inline, and 90 degrees to inline - SnapToInlineAndNormal.mov
3) Snapping to reflected angle - SnapToReflected.mov
4) Snapping to parallel direction - SnapToParallel.mov
5) Snapping to 90 degrees of parallel - SnapToParallelNormal.mov
6) Snap to logical triangle (useful for square corners?) - SnapToTriangle.mov
 
The useful thing about these snaps is that they will enable you to perform common curve construction, completely independent of grid or set axis.  You can use them in tandem with a second action while holding Shift to snap the handle lengths to match the preceding or following handle (while maintaining the direction you already snapped).

These are some recent snowflake shots I got. Quite happy with them. Focus merged with anywhere between 6-13 images.

FebSnowflke1 by Greg Murray, on Flickr

FabeSnowflake2 by Greg Murray, on Flickr

FebSnowflake3 by Greg Murray, on Flickr

FebSnowflake10 by Greg Murray, on Flickr

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!

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!

We've got a fix for this but I don't have a date for its release or when it will go to beta. Hopefully it won't be long. Sorry 

Right.  I started this thread to showcase features that are coming in 1.7.  This was no way an exhaustive list of everything that will go in, and I have said there is time to add more, so I fail to understand why us showing new (hopefully helpful) stuff has come across as the complete opposite.
 
It is a shame that some people have hijacked this thread for a diatribe about how we aren't doing what they want... and in their imaginary time frame.  1.7 is not coming just yet, and we have given no fixed time frame.
 
So, I am going to delete all posts on this thread that are not discussing the features that I am showcasing (in a helpful manner).  The intention was to show what we are doing and take helpful feedback before we even get to Beta, and so that you know we are already working towards the next updates.

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!

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!

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.

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.

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.

Getting Close to Halloween so...
 
 
 

There's probably an easier way, but here's how I created some rain today:
Add pixel layer. Fill with white. Add noise (about 30%). Layer/Rasterise (to fix noise). Zoom in to see pixels. Levels, black up about 50% (darkening it a bit). Threshold about 70% (rain distribution). Gaussian Blur (to widen spots), Preserve Alpha. Levels again, black up to darken spots. Juggle Blur and Levels for optimal size of raindrops. Motion Blur, Preserve Alpha, angle diagonal, radius right up (can type in big number). Levels to darken rain. Invert layer to make rain white. Pixel layer Blend Mode: Screen. Adjust Opacity to suit.  

Added to the Paint Brushes with a new set of texture painting brushes 
30 brushes from set 1
30 brushes from set 2
 
2 Zip files contains 60 brushes (3 pack x 10) x2
 
PDF sample files added

 
PBT 1 Set 1 01-03.pdf
PBT 1 P01-P03.zip
 
 

 
PBT 1 Set 1 13-15.pdf
PBT 02 P13-P15.zip

Vegetation Raster Brushes (leaves) 
Zip file contains 30 brushes (3 pack x 10
PDF sample file added
Set 2 (30 raster Brushes) available here:
Vegetation brush Set 2
 

 
VB 1 Set 1 01-03.pdf
Vegetation S1 P01 - P03.zip

Hey guys, because the comunity in the Facebook Group helped me a lot i decided to give you some resources i've created.
This pack contains: 
- 3 custom ribbons
- twitter, facebook and youtube title picture templates
- 1 grass brush
- 5 Smoke Brushes
- an awesome color palette for flat ui design
 
You can use it private and commercial, more informations and credits are as a pages and docx file in the pack.
 
Sorry for my bad englisch im just a student from germany
cheers and have a nice day
 
Affinity Designer Pack.zip

For the benefit of future readers, here is the thread that contains the official tutorials list with Vimeo and YouTube links.