junihh

I can get it with either Designer Beta (1.10.2.1178) or Designer Retail (1.10.1)on Windows, under the following conditions:
The Artboard or Canvas must be positioned in the workspace such that its left edge is outside the visible workspace, somewhere behind (to the left of) the left ruler. At that point, dragging the guide off the Artboard or canvas onto the ruler does not delete it. If I zoom out or reposition the view such that the left edge of the Artboard or canvas is visible, the guide is still there. To delete the Guide by dragging in that situation, I must drag it beyond the ruler, into the left studio panels, such that when I drop it it is beyond the left edge of the Artboard or Canvas.

<AFFINITY DESIGNER>
But... they are not global?
After defining my colors as global to easily adjust all objects accurately at once, selecting them in an gradient, they are no longer global for this gradientobject? wth? 
And why is there not an palette for this? I searched every bit od UI and help for the gradient-tool or palette...

As I am new to AP, I'm still working my way through its functions and capabilities. When I saw that it (AP) does not have the ability to export to WebP, I performed a Google search looking for the reason. After reading a couple of threads on this forum I see a lot of passion for adding the capability, but that passion is being met with a lot of indifference and misinformation in some of the responses.
For example, from the Affinity Photo Lead: and I'm waiting to see if anyone ends up caring about WEBP..
I must say that statement does not exemplify an understanding of web page design and construction.  Allow me to put this subject in perspective for you. 
1. WebP offers approximately 25-34% smaller file sizes in comparison to JPEG. (https://developers.google.com/speed/webp/docs/webp_study)
2. Given that images account for 51% of the content (in total page size) on a typical web page (https://www.keycdn.com/blog/image-cdn), a reduction of that magnitude is a significant factor both on a micro and macro scale.
3. It is a fact that ~90% of all searches are performed through Google (https://www.statista.com/statistics/216573/worldwide-market-share-of-search-engines/). Therefore, the necessity of appearing on the front page of an organic Google search is critical to the huge majority of websites.
4. Page speed scores are a vital component of SEO. The better the SEO score, the higher a website appears in SER. It then follows that a page with a smaller footprint will otherwise load more quickly and the faster a page will load the higher it will rank. (https://gtmetrix.com/)  (https://developers.google.com/speed/pagespeed/insights/)
5. Google decrees the SEO rules and guidelines. I don't necessarily agree with or even like how they've dictated policy, but they have the market share and we have to live with it. So, if they write the rules and build the hoops, one either jumps through those hoops or is left in a detrimental position.
6. The argument that Apple Safari doesn't support WebP, therefore it (WebP) must not be very popular or some fringe property is weak at best. Chrome currently has 60+% market share and Safari ~15%. Although the other browsers have small numbers, they support WebP which results in only a ~15% share of browser traffic that doesn't. A good designer/developer will include both formats as options when constructing a page, but it would be nice if Apple stopped their snobbery and went with the most efficient solution. (https://gs.statcounter.com/browser-market-share)
7. Why the reluctance to change? Old formats, codecs, standards have come and gone. Some hang around because nothing better has been developed (TIFF, maybe). Others are not let go simply because it's what we're comfortable using. There are undoubtedly various other reasons for why adoption is sometimes slow; however, from a technical point of view, there is substantial evidence that WebP is superior to both JPEG and PNG (just do a Google search) for both the web and printing. In my opinion, it's time to move on.

I'll upvote this for Affinity Photo and Designer. Especially since Photoshop and Illustrator don't support it natively and the extension for it is very flacky. This is a chance to out shine them!

Title says it all. Google PageSpeed is recommending the use of these formats, but AP doesn't support any of them. Please, if possible, do.

You was right Pšenda. Thanks. :-)

No, it is directly in Persona Toolbar.
https://affinity.help/designer/English.lproj/pages/Workspace/personaToolbar.html

I've been working with affinity and sketch for some time and it would be great if i could import / open a .sketch file directly in affinity designer. 
 
Thanks for the great work. 
Love the product :)

No, you misunderstood what I meant. That setting is for that layer only. I mean a transparent fill and stroke that would affect all layers underneath as well. As a partially opaque colored fill or stroke would affect the layers underneath it, so the transparent fill or stroke would effectively clip anything underneath. See the thread I mentioned for an explanation for what I'm trying to achieve in the simplest way possible.
 
Erich 

It is there already, I did this with one button press in the Export Persona.

When some designers talk about pages they are referring to the pages for page layout  in a publishing application. Page layout for a book.

When former fireworks (and freehand) users ask for pages we are not talking about pages for laying out a book. 

We are talking about a productivity feature. 

In the old days to make 12 astrology signs Id have 12 photoshop files or 12 illustrator files. Or I might have 12 artboards but it was not the kind of productivity we came to rely on with fireworks and the former macromedia freehand.  Fireworks offered layers and stacked pages accessed via a menu panel.

I could have the 12 characters one on each page all in one file. With a click I could click through each astro sign checking for exact placement.

I could have 12 colors on multiple layers. I could share all of those layers with all 12 pages or I could choose to share just one. I would turn them off and on and compare colors against all the signs in each page. I could have a two logos on two layers. I could share these to all the pages. turn off one. save out all the pages. turn off the other turn on the second one save out all the pages and offer up 24 options to the client. Everything remaining editable in ONE file.

IF the client loved one thing but not another I could go back into the ONE file and turn off the thing the client doid not want. try another iteration and save all those pages out all over again. ONE button click. Far more productive than opening 12 files and adjusting every single one.

pages. we want pages. And layers that can be shared at will with all or some pages. Not side by side pages as found in a publishing program used for page layout for books. Pages in a vector art program where multiple iterations of a single design or a style of button or more is required.

Share how you use pages in fireworks. It will help the developers to understand what we need. We dont need fireworks proprietary anything. What we need is for you to reinvent a method of productivity. And I for one will not care if it cant import old fireworks projects. That would be a plus but Ill settle for the productivity with new projects. Its the method and the increased productivity that counts. 

Make it so each page with its layers could be saved out to a PSD. Not that I care about photoshop anymore but a lot of people still using it. 

All 1.x version updates are free. When they release a 2.0 version (which probably will not be anytime soon) that version will need to be bought if you want to upgrade to it.

Hi junihh,
Welcome to Affinity Forums
Click the gradient colour well in the context toolbar right above the work area, select the colour stop you want to edit, click the Swatches tab on top of the pop-up you just opened and select the palette you want to use if necessary, then click/select the colour you want to apply to that node. You can also pick an existing gradient to apply to the (whole) gradient you are editing.