AdamStanislav
-
Posts
537 -
Joined
-
Last visited
Posts posted by AdamStanislav
-
-
Hi AdamStanislav,
The reason why they are exported as images/raster is because the brushes are based on a raster image which is stretched or repeated (depending on the settings) along a vector path.
I know, but that is not what I was talking about. The problem is that they are rasterized incorrectly. In my OP I have included a .jpg of what it looks like when exported to a JPEG, which is correct; then a .png of what the SVG looks like, which is incorrect.
I only mentioned the rasters inside the SVG to point out I did export it correctly and despite it creating rasters, those rasters are wrong, or at least appear to be in every single SVG host (and I have quite a few) I have viewed the SVG in. I have even enclosed the SVG so you can see for yourself what it looks like.
FWIW, I used the for the web preset (72 dpi) when exporting.
-
A straight line is a special kind of curve
Well, English isn’t my native tongue. But in my own language I was always taught there were straight lines and there were curved lines. So, a curve is a special kind of line, but a line, let alone a straight line, is not a special kind of curve.
Anyway, as I said, this is not a major issue to me, so I have no interest in getting into a debate here.
-
Thank you, Arun. I did use it. The exported SVG file even contains a number of embedded PNG images. So, it looks like a bug to me.
For the record, it was the vector brushes from this forum post that I used.
Adam
-
I was browsing the forum outside the Beta section and noticed someone offering free AD brushes. So, I downloaded them, just to see if they would install and install they did. Then I just did some scribbles to see how they work. I saved the result, then exported it it to JPG, which worked as expected:
Then I exported to SVG, but that only showed the strokes without the brushes:
-
Polygons are still represented as curves.
Why? Dictionary.com says a curve is “a continuously bending line, without angles.” Polygons consist of straight lines with angles. As NFG suggested, calling them paths would make more sense. Though I would just call them polygons. B)
-
Yes, of course! I have the Pro version and it does operate on 32 and 64 bit programs. Sorry for the misinformation but I'm glad you were able to resolve your problem.
You actually did help. It was when I was watching the uninstaller loading the information about the installed 32-bit software from the registry that the idea of searching the registry myself occurred to me.
Anyway, I don’t know if it can help Affinity programmers figure out why I was getting those messages (and why perhaps someone else may in the future), but I changed the extension of the .reg file I exported from my registry before deleting the problem key to .reg.txt and am attaching it here.
Adam
-
It's not correct, IMO.
I agree.
-
I have noticed that when I open/import an SVG image, in the layers list, where it lists all the objects, it says (Curve) to the right of polygon objects. This, while not a major issue, is inexact. A polygon is not a curve. A polygon is a geometric figure completely defined by a set of points connected by straight lines.
Adam
-
Well, I ended up running regedit, searching for Affinity, and deleting [HKEY_CLASSES_ROOT\Installer\Products\A3F452FAC88CD5E4D93D5F57A1F7944F] and all of its subkeys (though I exported it to a .reg file first, just in case that wouldn’t help). And, bingo, 1.5.0.8 now installed without a glitch!
-
The usual advice in such circumstances is to download and install the (free) http://download.cnet.com/Revo-Uninstaller/3000-2096_4-10687648.html, run it and tell it you wish to specifically uninstall AD.
Alas, it only works with 32-bit software, so it did not even find any of my Serif programs.
-
So, I then went to Windows Programs and Features and tried to uninstall 1.5.0.7, and got this popup. What now?
-
I cannot install this version. It goes through the setup, then says the older version (1.5.0.7) could not be removed and to contact technical support.
-
Not sure if bugs go here or in a new thread
New thread, I’d say. Otherwise, all we’ll have is one thread that would be impossible to navigate.
-
it is part of the svg spec that a blur can only be 10% larger than the objects size, so even a shadow would only be able to go up to 10% of the objects size without getting clipped.
Sorry, looks like a misreading of the SVG spec, which simply states that by default filter effect regions are 10% larger than the object they are filtering, or, more precisely, extend 10% up, 10% left, 10% down and 10% right from the bounding box of the object. However, that default is only used if the filter does not explicitly define the effect region of the filter, which can be of any size. See https://www.w3.org/TR/SVG/filters.html#FilterEffectsRegion.
-
LOL yeah, AV is showing some news at the wrong time.
Oh, yes, they (AVs) can be a pest.
-
What was that, Vadim? Did I see Affinity ask you if you have children in that video at 0:35? :o
-
-
You’re quite welcome.
-
Version 1.5.0.6, I was exporting some pretty text to SVG, checked the thing telling it to export the text as curves, but no, it exported it as text. I had to go back, turn the text into curves inside the editing window and then export it to SVG.
-
First of all, I installed 1.5.0.6 this morning. It was a painful process because after it installed the .net and went to the Affinity setup, it locked up the entire computer, so I had to power it down. When I turned it back on, it went through saying it was updating my computer. Yes, my computer, not my Windows! It did it while the computer manufacturer’s logo was showing up, so it looked like it was doing that during the BIOS bootup, and that was scary!
Anyway, I then installed 1.5.0.6 without a hitch. But when I first started it and it was showing its fancy startup graphic with its transparent background, out of curiosity I just clicked on the startup graphic and it suddenly had a black background. I clicked on it again and the background turned white and I got an Unhandled Exception message from Windows. When I clicked OK on that, the startup graphic disappeared and Affinity stopped loading.
So I tried to load it again, this time without clicking on the startup graphic and it loaded successfully.
I can’t say whether this is something new in 1.5.0.6 because this was the first time I ever clicked on the startup graphic.
Adam
-
Thanks, Mark.
-
When I open an SVG file (this has been going on in all the Betas so far) and try to export it as a PNG bitmap, the save dialog claims it is going to create an *.png file but it keeps the .svg extension in the file name it offers, so if you just accept it without explicitly deleting the .svg extension and changing it to .png, it will save the PNG bitmap under the name of the original SVG.
OK, that was a mouthful. So, here is an example:
Open example.svg, export to PNG. After the export dialog, the save-file dialog pops up. It suggests to save the PNG as example.svg. Since any other Windows program would automatically offer example.png, you just press the enter key, and now you have lost your original SVG file and you cannot find your bitmap because example.svg in now a PNG bitmap with the wrong extension.
Additionally, Affinity Designer now thinks that example.svg has changed (even though all I did was export it), and so when I want to quite the program, it wants me to save it.
-
The installer language should be populated. We should support English, French, German, Italian, Spanish, Japanese and Chinese.
I will get the guys to look at the installer tomorrow.
Thanks.
-
As long as it is something you’re working on, I’m happy. :)
Exporting to SVG
in [ARCHIVE] Designer beta on Windows threads
Posted
Thanks, MEB.