dcarvalho84

@Patrick Connor i think i've managed to reproduce something similar to what @Oval is talking about.
I will attach my file created in AD Beta 10.
My curves are not so rounded as the Oval screenshot, but they are not straight lines.
You will have to really zoom in, let's say 20000% to see it perfectly.
 
For me that problem is not bothering at all. i'm just trying to help providing the file and maybe end with this unfriendly conversation from both sides.
 
In the screenshot is what i'm getting from AD App Store Version and AD Beta 10. The result is the same.
line.afdesign

@Patrick Connor As i've said i'm just trying to help and end with this confusion. Yes that line is 1.1mm zoomed to 20000%. I didn't even use the line mode with the pen tool on my everyday work.
I'm using AD since the end of November 2016 and i don't have words to thank all the team for such an amazing piece of software I can't live without you Affinity

@Patrick Connor i think i've managed to reproduce something similar to what @Oval is talking about.
I will attach my file created in AD Beta 10.
My curves are not so rounded as the Oval screenshot, but they are not straight lines.
You will have to really zoom in, let's say 20000% to see it perfectly.
 
For me that problem is not bothering at all. i'm just trying to help providing the file and maybe end with this unfriendly conversation from both sides.
 
In the screenshot is what i'm getting from AD App Store Version and AD Beta 10. The result is the same.
line.afdesign

.

For windows that is ALT plus left and right mouse button, 

Creating the Numbers text style with the tab stops built into it is a nice touch, but it is too bad there is no way (that I know of) to create a style with tab stops set relative to the frame width (like at 10%,  20%, & so on) that change their linear position (in mm, inches, or whatever) when the frame width changes. Of course, one can always use the extra handle below & to the right of the frame to scale the text along with the frame, & the tabs will scale along with the rest of the text, but the style would be more "portable" if relative tab stops were supported.

Note: This is not intended as a practical solution, only as a design exercise that someone might find interesting.
 
Before there were personal computers, there were crude "perpetual calendars" that consisted of a sliding plate with day numbers printed on it in a frame with a cutout sized to reveal seven of the plate's number columns. To change months, the plate was moved left or right to adjust the starting day of the month. There were no provisions for months shorter than 31 days; you had to remember which months had 30, 29, or 28 days.
 
To simulate that kind of device, I used a rectangle for the cutout in the frame, a text frame layer clipped to it for the sliding plate, & the lock children option so the frame text would slide properly. I also made four versions for 31, 30, 29, & 28 day months, & added a rectangle to lighten Sunday days:

This works OK as long as the day frame text uses a monospaced font like Courier, Monaco, or Menlo; otherwise the character spacing must be adjusted for each day number for the columns to line up. Tabs might work for that but I did not try that.
 
I think this could be simplified further to one artboard with all four frame text layers as children of the frame rectangle, or with guide lines so the text frame could be snapped to align columns more easily, but the attached calendar.afdesign file is as far as I got.

Good spot! I've reproduced this and will get it reported

Hello @Jose A
Have you tried one soft proof adjustment layer?
Also on the Document menu you have the ability to assign or convert ICC profile option.
Don't know if that helps but it might worth looking.

Hmm, many questions come to mind. If I understand you, you are interested in a separate file for each month, not a 12-month file, and your goal is to find an easy way to turn Janeiro 2017 into Janeiro 2018. Etc for February, etc for March, etc. And you want to have a separate color for Sunday dates. And I don't know whether you want to use AD or AP or the future APub.
 
My approach would be to create each month using a macro that can access the universal DATE function. This would get you past the Leap Year problem. And with this method you don't need to modify a month for next year - your macro just builds each new month for you.
 
I don't know how to get a date function with Affinity so I would use a spreadsheet then paste the results into AD or AP or the future APub. The spreadsheet columns could be set up with the Sunday colors and, hopefully, it will keep the colors when you paste. You can use Excel or try the free Open Source Libre Office (includes Calc as their spreadsheet) and avoid Microsoft.
https://www.libreoffice.org/
 
Or just find free calendars online using google and paste them into AD or AP or the future APub. This doesn't help with your specific question but it is an alternative. And, hopefully, maybe some AD/AP experts will post with better solutions.

Here is a clean template to make a mandala in a super simple way.
Just open the file, select the layer "Draw the Mandala here", start to draw and have fun !
Mandala template 12.afdesign

@dcarvalho84 I think I've just resolved the embedded document issue you are experiencing - that will be in the next Beta update too

@MattP Maybe i don't have made myself clear... When i'm talking "important" i'm referring the fact that the last object was not recognized as deleted don't know if that point is important for you to search from there, i'm not talking about the bug not being solved  I'm here to help and i know that things take time.If you need any help/test regarding this you're welcome.

No need for another video - I do see this as important, don't think that just because it's not fixed straight away that we aren't interested - some things take longer to solve...

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 text appearing blurry while typing. Fix for artistic text creation jumping between different sizes while you drag out a new object. Also added a tooltip next to the cursor to show the size of the text you are about to create. Fix for boolean operations of overlapping areas failing since Beta 5. Fix for fonts not updating correctly when told to reset. Hopefully reduced 'over-eager to serve' behaviour of hidden left and right studio panels. Reduced complexity of the results from 'Expand Stroke' so that they're hopefully more usable. I have not rewritten what it does, just made the result more usable. I will improve this to provide better results on thin strokes for the next beta... Fix for a few OpenType text style bugs. Fix Beta App icons appearing all kinds of crazy colours on macOS High Sierra! Fix for Metal View grid not matching the legacy view's grid when gutter is involved... Added 'Find in Layers Panel' menu item to the 'Layer' menu so that users can assign a shortcut to it for improved workflow. Miscellaneous other tweaks.

Yes, I'm on Sierra. Will enable it and see how it goes. Thanks for the reply.

@Jens Krebs i'm talking about finding something that nobody seems to identify yet ;)
And like @MattPsaid i'm archaic metodology which i can port to ipad aswell :D
 
Please keep delighting us with your amazing software. And i didn't forget publisher! Waiting for it.

You're Welcome ;) This should be enough for you to put me on the Afffinity Designer for ipad testing team :p
I think you can replicate with any bluetooth mouse too. Apple mouse for instance.