SaucyWeeTart

Would it not make more sense to offer plugin support earlier rather than later? That way, the community itself will help you proactively build and popularize your products - hopefully leading to a snowball effect. I see it as a potentially very powerful growth mechanism.
 
I'm sure you guys have thought about it but I'm curious what your thoughts are.

Would it not make more sense to offer plugin support earlier rather than later? That way, the community itself will help you proactively build and popularize your products - hopefully leading to a snowball effect. I see it as a potentially very powerful growth mechanism.
 
I'm sure you guys have thought about it but I'm curious what your thoughts are.

Would it not make more sense to offer plugin support earlier rather than later? That way, the community itself will help you proactively build and popularize your products - hopefully leading to a snowball effect. I see it as a potentially very powerful growth mechanism.
 
I'm sure you guys have thought about it but I'm curious what your thoughts are.

Would it not make more sense to offer plugin support earlier rather than later? That way, the community itself will help you proactively build and popularize your products - hopefully leading to a snowball effect. I see it as a potentially very powerful growth mechanism.
 
I'm sure you guys have thought about it but I'm curious what your thoughts are.

Would it not make more sense to offer plugin support earlier rather than later? That way, the community itself will help you proactively build and popularize your products - hopefully leading to a snowball effect. I see it as a potentially very powerful growth mechanism.
 
I'm sure you guys have thought about it but I'm curious what your thoughts are.

Hey guys,
 
Quick question, what's the main difference between the 'Expand Stroke' command and the 'Convert to Curves' one? What example would I use one over the other?
 
Cheers!

Would it not make more sense to offer plugin support earlier rather than later? That way, the community itself will help you proactively build and popularize your products - hopefully leading to a snowball effect. I see it as a potentially very powerful growth mechanism.
 
I'm sure you guys have thought about it but I'm curious what your thoughts are.

Would it not make more sense to offer plugin support earlier rather than later? That way, the community itself will help you proactively build and popularize your products - hopefully leading to a snowball effect. I see it as a potentially very powerful growth mechanism.
 
I'm sure you guys have thought about it but I'm curious what your thoughts are.

Would it not make more sense to offer plugin support earlier rather than later? That way, the community itself will help you proactively build and popularize your products - hopefully leading to a snowball effect. I see it as a potentially very powerful growth mechanism.
 
I'm sure you guys have thought about it but I'm curious what your thoughts are.

I posted the exact same thing a while ago. It would really improve the experience on smaller screen sizes. I dislike many of Adobe choices, but they've nailed this particular thing.

Would it not make more sense to offer plugin support earlier rather than later? That way, the community itself will help you proactively build and popularize your products - hopefully leading to a snowball effect. I see it as a potentially very powerful growth mechanism.
 
I'm sure you guys have thought about it but I'm curious what your thoughts are.

Status: Beta Release
Purpose: New features, fixes
Requirements: Purchased Affinity Designer
Mac App Store: Not Submitted
Download: Here
 
This beta version represents a substantial change to our codebase and as much as we have tried to ensure the quality of the code, it should be considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity that may be adversely affected by the application failing. In addition it is definitely worth noting that files created in Affinity 1.6 may not open in 1.5 so always make a copy of your important documents before opening them in 1.6 to ensure you do not accidentally overwrite them and are unable to open them in your 1.5 version.
 
To use this beta, simply download the file from the link given above and double-click on the file to open the installer. Follow the instructions to install the beta version. The beta sits alongside the Mac App Store version and will not interfere with it.
 
Fixes/Improvements:
Fix for crash when exporting Fixed incorrect colours when using Metal view option in Sierra with AMD GPUs Added support for macOS file system tags when saving Fix for crash changing between Asset categories with an active search term Fix for editing a colour in the system palettes Fix for SVG import of scaled content (found in certain CorelDRAW exported SVGs) Fix for some panels crashing in the Light UI scheme Performance increase for boolean operations performed on many objects at once Fix for 'Always show crosshair cursor' not being honoured for non-round pixel brushes Fix for exporting 'Selection with background' causing artefacts if the same area is included in the selection more than once Miscellaneous other tweaks

I have no idea what you mean, Alfred... it's working fine for me? ;)
 

Thanks for your words SaucyWeeTart. I'm sure the dev team will appreciate them. They really did a great job here (i'm biased i known but still!).

Hey,
 
This is just a quick message to the Serif team.
 
I've been tinkering about with your Photo app for the iPad all night and I must say, it's very impressive. For about a year, my 12.9" iPad Pro has been on the brink of being sold because it hasn't once lived up to it's much touted 'pro' status (mainly due to the apps on offer). Photo has absolutely changed that for me. It still has a good few bugs here and there but to knock out an app of this quality is very impressive.
 
Seriously guys, well bloody done.
 
 
❤️

Hey Matt, any chance we might be seeing...
 
right click or key short equivalents for: 
- lock current selection,
- lock everything but the current selection,
- unlock all,
- hide the current selection,
- hide everything but the current selection,
- unhide all,
 
Sorely missing this stuff.  :( 
 
Is it still in consideration?
 
Cheers. :)  

??
 
A spunky, relatively tiny competitor methodically and carefully building fresh-from-the-ground-up elegant, powerful, and affordable alternatives to a set of decades-entrenched applications "shows no enthusiasm" just because they're not done yet?!
 
JET

Hi guys,
 
Wasn't really sure whether to put this in 'Feature Requests' or not, so here it sits.
 
Before I cancelled most of my Creative Cloud, I used Typekit fairly heavily, and was really impressed with it overall. It got me wondering if a feature like that would work well with the Affinity suite. I'm sure it would but have not got a clue of the logistical/financial issues which may surround it.
 
Any thought been given to it?
 
Thanks,
Stu Wilkie.

Hi guys,
 
Wasn't really sure whether to put this in 'Feature Requests' or not, so here it sits.
 
Before I cancelled most of my Creative Cloud, I used Typekit fairly heavily, and was really impressed with it overall. It got me wondering if a feature like that would work well with the Affinity suite. I'm sure it would but have not got a clue of the logistical/financial issues which may surround it.
 
Any thought been given to it?
 
Thanks,
Stu Wilkie.

Would it not make more sense to offer plugin support earlier rather than later? That way, the community itself will help you proactively build and popularize your products - hopefully leading to a snowball effect. I see it as a potentially very powerful growth mechanism.
 
I'm sure you guys have thought about it but I'm curious what your thoughts are.

+1
I'm going pile on here with a real-life use case for "transform each".  
 
I'm working on improving the clarity of a collection of 28 scatter plots created in R, each of which has 50 data point markers.  I need to resize each of those identical markers to the same final size, and it's critical that I preserve the integrity of the plot by resizing them so that their centers do not move.  I'm not too enthusiastic about the idea of individually resizing 1400 objects.

Hey guys,
 
I posted about this before a while ago but I feel the need to post again because it's very irritating and I really think it should be given some attention from the dev team.
 
The issue is the kind of buggy relationship between the MAS/beta versions of your app. As you guys already know, during a beta cycle one might open loads of .afdesign files with it and therefore move the beta into the 'default app' list in OSX. The problem is that after the beta cycle ends and you update the MAS version, all your .afdesign files are still tied to the beta, which with a double click, sends you on a magical journey like this:
 
> splash screen with an error message
> click 'ok'
> new tab opens in your browser to app store
> app store then opens up on OSX
> close window
> close tab
> another splash screen with 'failed to open file'
> click ok
> beta splash screen then freezes on screen until you right click and manually close it
 
What's the problem with still being able to use the beta even if it's a version behind the MAS? There must be another way to indicate that you've opened your file up in an outdated beta, other than the process above.
 
When I was using the Adobe Muse/Muse beta apps they functioned just fine because it was up to you where you opened your files. If you opened them in an outdated beta, fine.
 
Unless I'm still totally missing the point, I still consider this a problem. And a problem that makes me want to systematically end everyone in the office.
 
Thanks for reading that wall,
Stu W.

Hi Stu,

I'm moving this to the Designer Beta Forum's as this is more applicable to them as it is not a bug with the release software, developers are also more likely to see the thread in there as well.

Hey,
 
I was just wondering when you guys think a Publisher Beta will be released, and how to sign up to it. I'd be very interested in doing just that.
 
I had a quick look through the forums and couldn't see anything related to that.
 
Thanks!

Collapsible palette functionality that reduces the palettes into an icon.
This would allow more screen real estate when working on designs.
Clicking the palette's icon should restore that palette as a fly-out with the others remaining collapsed.
 
Similar implementation to Adobe Photoshop / Illustrator (shown below).

 
Also mentioned here: https://forum.affinity.serif.com/index.php?/topic/16282-cvollapsible-palettes-export-preview-actions-glyphs/?p=73830