Signguy

I have heard of people finding the circumfrance of the circle and then making a line the same length of the circle circumference.  Then you could space your 45 shapes (or what ever the odd number is) evenly across the line using the space horizontally tool.  Then you could create a new brush using those shapes.   Create a new circle using the brush and I guess this might work.  Especially if you have different kinds of shapes that need to be spaced evenly.  I know it's possible but it sounds like a pain to me.  Plus, if she is using a vinyl cutter, the brush would no longer be a vector shape that could be cut out.  
 
It would just be a lot easier to make an even number of circles and rebuild it.  I doubt that anyone is going to actually count the number circles other then you. 
 
On a side note, how are you exporting your AD files into your cutter software? What format? 

This has been covered a couple of different times on this forum.
 
The easiest way is as follows:
 
1. Draw a circle using the circle shape and hold the shift key to constrain its proportions.  
2. Drag the circle to the top of your design in the 12 o'clock position.
3. Select the circle and duplicate it using either Copy/Past or Command J key combinations.
4. Drag the second circle to the 6 o'clock position while holding the shift key to keep it in perfect alignment.
5. Decide how many dots that you want your overall circle to contain.  Make sure it is an even number and divide it into 360.  (ex. 360 dots divided by 46 = 7.8260869565º of seperation)
7. Click on the center rotation spot in the transform window.
8. Select both upper and lower circle and hit CMD-J to duplicate them.
9. In the rotation box (transform window) enter the degree of separation that you came up with.
10. Continue to hit CMD-J until your circle fills up with the required number of duplicate shapes that you wanted.
 
 

Hi Signguy,
Yes, there will be improvements here. Embedded documents will export as vectors if they contain vector objects/layers.

Which is still an absolute BARGAN!

Having an offset path will be nice.  I've been using stroke, expand stroke and then doing a geometry divide to get my results.  It works but it's not as easy as having native offset path.   Printing registration marks would be nice as well!  Or having the ability to create registration marks from a rectangle shape.

This is something that Affinity Photo can do already.

Hi Signguy,
You can export at a higher setting than 400 dpi. Click on the input box and write the value you need.

Shouldn't this be 1.4.2 beta 3 since we already have a 1.4.1 version?   Just wondering.

Shouldn't this be 1.4.2 beta 3 since we already have a 1.4.1 version?   Just wondering.

That light purple outline that you see is a snapping candidate. Turn them off an you will no longer see them.
 
Additional instructions can be found here: https://forum.affinity.serif.com/index.php?/topic/16406-designer-whats-with-these-purple-lines/?hl=snapping+candidate&p=74340

If you look under your styles panel, you will see there is already a rainbow style that should work well for you too.  Pretty strait forward IMO.
Remember you can always make your own styles as well and save them for future use.

If you look under your styles panel, you will see there is already a rainbow style that should work well for you too.  Pretty strait forward IMO.
Remember you can always make your own styles as well and save them for future use.

You may want to explore using "compound shapes" for what you want to do.
 
I didn't have access to my laptop when I sent this reply(mobile), but here is an quick example of the sun if you haven't figured it out yet.  You don't have to worry about how long you make your horizontal lines if you do it this way.  The only other thing that you could do would to be use the subtract boolean but this way is non-destructive.
 
 
Sun.afdesign

I am able to import SVG files that have hidden layers so it only seemed logical to be able to export them as well.  It's not a problem to select all layers and make them visible before I export, it just doesn't look very nice when layers overlap or when a layer is representative of an artboard or another page.  
SVG is an open standard whereas .afdesign is not so this does make it difficult for certain people to exchange files easily. 
 
My issue was that I was sent a licensed SVG file that had hidden layers.  I made some changes and sent them back to the original licensor of the file and he was not able to see the hidden svg layers that I made changes to.  It just seemed awkward to have to select all layers when the SVG standard allows hidden layers.
 
On the other hand, I'm sure that there are instances where someone might want to export to SVG and not have hidden layers contained within the file either.  I know that in AI hidden layers are exported whether you want them or not so I guess there is an argument on both sides of the fence.  
 
I just want you to know that I couldn't be happier with Affinity Designer/Photo and you guys have given me more options then I could have hoped for.  I am more than happy to work around some of these little incompatibilities and don't find them to be a major problem at all.  If someone really needs something that AD doesn't offer then they can use some other program that provides that compatibility.  It really bugs me when someone complains and threatens to switch to something else.  There is nothing better than Affinity for the price!
 
Thank you for providing us with such a wonderful tool for the price and thank you for your unbelievable support!  I owe you a lot more than I have ever paid for your software.

Hi Singguy,
 
At the moment we only export layers that are visible and haven't been hidden. The ability to export hidden layers is something that has been requested in the past and may be added in the future but in the meantime you will have to make all of your layers visible before you export.
 
C

definitely no!

You may want to explore using "compound shapes" for what you want to do.
 
I didn't have access to my laptop when I sent this reply(mobile), but here is an quick example of the sun if you haven't figured it out yet.  You don't have to worry about how long you make your horizontal lines if you do it this way.  The only other thing that you could do would to be use the subtract boolean but this way is non-destructive.
 
 
Sun.afdesign

Font fallback is great (It would be nice to know that the font is a fallback font by some type of notation).
Recently used fonts section of the font dropdown now also includes all fonts in the current document - GREAT ADDITION Thank you!
PDF export fixes are great.  Most of my issues are now fixed!
 
Thank you Affinity Team and have a Happy Thanksgiving!  Take some time off will you?  You guys deserve it.

Font fallback is great (It would be nice to know that the font is a fallback font by some type of notation).
Recently used fonts section of the font dropdown now also includes all fonts in the current document - GREAT ADDITION Thank you!
PDF export fixes are great.  Most of my issues are now fixed!
 
Thank you Affinity Team and have a Happy Thanksgiving!  Take some time off will you?  You guys deserve it.

Font fallback is great (It would be nice to know that the font is a fallback font by some type of notation).
Recently used fonts section of the font dropdown now also includes all fonts in the current document - GREAT ADDITION Thank you!
PDF export fixes are great.  Most of my issues are now fixed!
 
Thank you Affinity Team and have a Happy Thanksgiving!  Take some time off will you?  You guys deserve it.

It seems to me that there is a separate, and possibly larger issue here. The fact that this is apparently a small company, with a dedicated but limited staff, working very hard to get two high quality products to market. They have had to push the Affinity Publisher beta release. It seems very counter productive to do a survey on the present demand for a product you may not even be able to start planning for maybe 2 years. Not to mention committing now, to a Linux version, and then having to listen to people complain about how long it is taking to release it. Nothing kills a company faster than taking on more they they can handle. It's easy from the outside to say "What about this feature? Why haven't you added the ability to do such and such? It's been a year a still nothing! This shouldn't be that hard!". We don't know the difficulties the developers face. The issues they are trying to resolve and those unforeseen they will have to handle. Nothing is impossible for those who don't have to do it. Not long ago neither of these apps existed and they are being expected to live up to programs that have been enhanced and redefined for 20 years. And now they should also take on Windows and Linux versions because clearly they don't have a well thought out business plan and are just making decisions on the fly. Come on. Cut them some slack.

Thanks for providing alternative directions without having to disable SIP.  Unfortunately, there are still a few issues with El Capitan and Affinity Designer (unable to search for file names in file open dialog) that prevented me from upgrading.  So I'll stick with Peter's approach and continue to use Yosemite until these issues get resolved.  

Because AD does not have the ability to create vectors from embedded graphic files yet, I decided to use Vector Magic Desktop as an alternative.  Unfortunately, I just discovered that Vector Magic Desktop does not work with El Capitan.  So, I am now forced to go back to Yosemite.  Anyone else experience this?

I fixed the crash by replacing the updated dylib with one from Yosemite.
The path is shown in the crash log. Make a backup, then copy it from Yosemite over the El Capitan one.
 
Full instructions, and a download link to the dylib if you can't get one yourself are available here, so that I can keep the instructions updated:
https://georgegarside.com/blog/osx/vector-magic-crash-el-capitan/

Hi Kevin,
It's not a question of honesty. It's also hard to predict when something will be ready for release. There's always bumps during development. Sometimes, some code must be rewritten or approached in a different way or even simply put on hold until something else is completed because it's tied to another feature. There may be some additional research needed or issues that weren't anticipated.
So rather than pointing and force a tentative date which we may or may not meet and that eventually would lead to a subpar implementation just to meet a deadline, it's better to simply made new features available when we feel they are ready for testing/public release.