AdamStanislav
-
Posts
537 -
Joined
-
Last visited
Posts posted by AdamStanislav
-
-
I actually tried that (ungrouping and regrouping) and I don’t even have Show snapping candidates turned on (it doesn’t seem to do anything when I do turn it on, so I keep it off), and I still had the problem.
The only thing that helps me is hiding all the Mandala-Guides, but that defeats the purpose of having them there in the first place since the idea behind the whole thing is to Ctl-J the “Box” (which is a symbol) several times and rotate the copies around the circle, so when I select the original “Box” and draw something, AD automatically creates the necessary duplicates and produces a nice mandala (based on this tutorial), while the guides are meant to help me to snap somewhere on an intersection of the circles (and octagons) with the other guides (the ones that look kind of like rays).
-
Thanks, KoBu and Lilpri.
-
Rather than trying to explain, please open this file Slow!.afdesign, enable Show Rotation Center, and try to drag the rotation center to the center of the image. At least on my computer, this becomes impossible and Windows just says AD has become non-responsive.
It was so bad, I was wondering if the problem was with Beta *.14, which occasionally crashes on me. So I uninstalled it (btw, the uninstall did not remove the desktop shortcut!) and reinstalled Beta *.12, but had the same problem.
I installed *.14 again, removed a number of gigabytes worth of files from my computer thinking maybe my system was running out of virtual memory, but no go.
Finally, in desperation, I unselected the snapping magnet, and suddenly everything was working, except of course I could not snap anymore.
Admittedly this file has a lot of objects to snap to, but is it really necessary to be snapping to every single object on the way while the mouse keeps dragging and has since moved far beyond whatever object AD is still calculating?
Adam
-
This version crashes a lot for me, almost always when either saving a file or exporting one, though it seems to write those files properly before it tells me it crashes. Whenever that happens it offers to send a report next time, and of course I tell it to do so. Nothing is in the Crash Reports directory; I’m assuming AD deletes the reports after it sends them to you?
Anyway, when I restart, it can open the file it saved just fine.
-
Oh my god! I'm so dumb! Shame on me!
LOL, we’re all still learning the intricacies of AD 1.5. There’s no shame in that. :D
-
Purple borders are back again :(
It’s to show us the object is currently selected.
-
If it created a crash report, it will give you a reference the next time you start the app. You can find the reports in %APPDATA\Affinity\Designer\1.0 (Beta)\Crash Reports.
Actually, that should be %APPDATA%\Affinity\Designer\1.0 (Beta)\Crash Reports (a percent sign before and after the APPDATA).
-
I created a simple text to test whether, upon SVG export, the text is converted to curves as requested (it does, thanks) and I assigned it a radial color gradient. I chose the SVG for web preset.
The text consisted of just three characters and an exclamation point (see Aha!.afdesign ). It converted it properly to four separate paths. It, however, created four separate SVG radialGradients, one for each of the characters. All four were identical. There should only have been one radialGradient, which should have the been assigned to each path.
Here is the SVG it created: Aha!.svg
-
-
- Fixed SVG export of relative coordinates to use a relative “m” for a move to a subcurve of a polycurve
Thank you!
-
I'm just wondering if they have a timeline for actual release.
Do you understand the whole point of Beta testing? It is for others than the programmers to find all the various problems the programmers aren’t aware of, so they can fix them. And since they’re not aware of those problems, they cannot know when the software will be ready for final release.
As such, I’m sincerely hoping they don’t have a timeline for actual release because that would only force them to release some software that is not ready for release.
- Mark Ingram and Alfred
-
2
-
Were you logged in as an administrator when you were trying to install it?
-
Thanks for the update.
-
That one wasn't reported, so thanks!
I've just logged it for the developers to look into :)
You’re most welcome, Jon.
Adam
-
Thanks, QA.
I have just noticed another problem with imported SVG and will just mention it here instead of starting another thread.
The SVG in question can be had by going here and clicking on the image. The image on that page shows what it should look like. The image here shows how AD is interpreting it:
The problem is that AD is incorrectly interpreting, or just plain ignoring, the spreadMethod="reflect" in the linearGradient declaration.
Adam
P.S. This time I was able to attach the SVG file itself here: thailandflag.svg
-
The Herzegovina.svg file does not declare a clipPath, but the one I posted does. You can see it at https://openclipart.org/detail/257331/the-bosnia-and-herzegovina-rainbow-flag. The image on that page has it clipped properly. If you click on the image, you will see the SVG file whose code I posted above.
Or you can just go directly to https://openclipart.org/download/257331/bosniarainbowflag.svg and see it in your browser. Also Inkscape clips that one (the one I posted) correctly. Serif DrawPlus also clips it, though messes up the background (but I’m not too concerned with DrawPlus because once we have a fully functional AD, we can stop using DP).
-
Well, since I have been unable to upload the SVG file (and I have tried repeatedly), I am going to paste it here:
<?xml version="1.0" encoding="UTF-8" standalone="no"?><svg version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" viewBox="0 0 24 16"><g id="bosniarainbowflag"><title>The Bosnia and Herzegovina Rainbow Flag</title><defs><linearGradient id="Rainbow" x1="0" x2="0" y1="0" y2="1" gradientUnits="objectBoundingBox"><stop offset="0" stop-color="#F00"/><stop offset="0.1667" stop-color="#F00"/><stop offset="0.1667" stop-color="#FF9800"/><stop offset="0.3333" stop-color="#FF9800"/><stop offset="0.3333" stop-color="#FF0"/><stop offset="0.5" stop-color="#FF0"/><stop offset="0.5" stop-color="#009800"/><stop offset="0.6667" stop-color="#009800"/><stop offset="0.6667" stop-color="#00F"/><stop offset="0.8333" stop-color="#00F"/><stop offset="0.8333" stop-color="#980098"/><stop offset="1.00" stop-color="#980098"/></linearGradient></defs><g id="rainbowflag" fill="url(#Rainbow)"><title>The Rainbow Flag</title><rect width="24" height="16"/></g><clipPath id="snip"><rect width="16" height="8"/></clipPath><g id="bosniaflag" clip-path="url(#snip)"><title>The Bosnia and Herzegovina Flag</title><rect width="16" height="8" fill="#002395"/><path d="m4.24,0h8v8z" fill="#fecb00"/><g id="g"><path d="M2.353283,0.5248529 2.8,-0.85 3.246717,0.524853 2.077197,-0.324853H3.522803z" fill="#fff" id="s"/><use xlink:href="#s" x="1" y="1"/><use xlink:href="#s" x="2" y="2"/></g><use xlink:href="#g" x="3" y="3"/><use xlink:href="#g" x="6" y="6"/></g></g></svg> -
When importing an SVG file which contains a clipPath element, AD ignores the clipping path and displays objects that extend outside the clipping path.
This image shows what such a graphic looks like in AD (the bottom star should be cut off at the border with the green stripe but is not):
Here is what it is supposed to look like:
I wish I could show you the SVG original, but the forum refuses to upload it.
Adam
-
-
When exporting to SVG, even if Use relative coordinates is selected, absolute coordinates are still used to move to the next point within the same path element. I’m not talking about the first move within a path, which, unfortunately, has to be absolute because of the way SVG works, but about any subsequent moves within the same path.
For example, take this snippet of SVG code produced by Affinity:
...c0.2,3.201 0.2,6.002 0.2,21.207l0,17.592ZM234.888,7.888c0,-0.8 0.2,-1.2 0.9,-1.4...
It contains a relative curveto, a closepath command, an absolute moveto command, followed by a relative curveto command, etc. Everything is relative as it should be (with Use relative coordinates ticked). Everything, that is, except the moveto, which is absolute.
Adam
-
A polygon drawn with the Polygon Tool shows as '(Polygon)' on the Layers panel.
That has no relevance for this. This thread is about a polygon in an SVG file opened in AD, a file which has a polygon (actually many of them) drawn using the SVG polygon element, which, as its official definition says, “defines a closed shape consisting of a set of connected straight line segments.” When opened in AD, all those polygons show as curves, not as polygons, as clearly illustrated in the enclosed screen cap.
Why is it that every time someone reports some issue with the Beta on this forum, it is like having a tooth pulled? People start jumping at him, quoting all kinds of straw men, trying to prove him wrong. Why? We are volunteering our time and resources to Beta test a product someone else will make a ton of money on, yet we are treated as we were a stupid bunch of nincompoops.
Adam
-
Thanks Adam. So, your original "cannot be removed" problem has not happened again, when uninstalling either 1.5.0.7 or 1.5.0.8 - right?
That’s correct. It did not happen again.
Adam
-
Hello guys,
if your object is of type "Polygon" (i.e.. a procedurally generated polygon shape) - then it will say "Polygon".
Except it doesn’t. It says curve.
-
Hi AdamStanislav,
Please could you try uninstalling 1.5.0.8. Do you get the same problem?
[EDIT] Also, what happens if you install 1.5.0.7 again and then uninstall it?
I wish you hadn’t asked that! Here is what happened:
I uninstalled 1.5.0.8 fine. I noticed it didn’t remove the shortcut from the desktop, so I double-clicked it. Windows said there was a problem and asked me if I wanted to wait, close, debug. I picked close, then right-clicked on the shortcut and asked to go to the directory. Everything was still there, the exe, the dlls, etc. I double-clicked the exe, same result as before. Presumably the uninstall just restored the directory to whatever was in it before I installed 1.5.0.8 (since I was unable to uninstall 1.5.0.7, only deleted the registry entry, the files were still there).
Next, I installed 1.5.0.7. I double-clicked on the shortcut and nothing. So I tried again, and this message popped up:
I uninstalled it. It performed a clean uninstall, including removing the files. I don’t know what possessed me, but I decided to install 1.5.0.7 for a second time. This time double-clicking showed the message that a new Beta was available. I clicked OK since I didn’t need to download it again. It showed the standard Affinity window, the black background and a message popped up that Affinity had recovered from a crash and would I like to send a report. I said yes, the popup disappeared, and then I was just staring at the black window for a long time. Eventually, I clicked on the icon to make the window smaller (the restore icon) and got a message from Windows that Affinity was not responding. So I told it to close.
I tried to run it again, but I always ended up in the black window with nothing happening. And now my entire system was down to a crawl. That is when I wished you hadn’t asked me to try installing 1.5.0.7 again, because it had always brought my system to a crawl.
I decided to see if I could install 1.5.0.8 over it, but since my system was now non-responsive, I decided I had enough. I cancelled the 1.5.0.8 install, uninstalled 1.5.0.7, and suddenly my system was running smoothly again. I then installed 1.5.0.8 from scratch, and the only thing that went wrong was that now Windows didn’t know what to open the *.afdesign files with and asked me if they belonged to the Opera browser. :o
I was able to run 1.5.0.8 just fine, but I could not find any option for it to make itself the default software to open the afdesign files. So I right-clicked on one of those files, chose Open With, and had to actually go to the Affinity directory and click the executable to tell Windows to use it as the software to open the afdesign files with.
Adam
Non-Responsive
in [ARCHIVE] Designer beta on Windows threads
Posted
Well, I tried to simplify the guides, resulting in this file Mandala-Guide-8.afdesign. I managed to move the rotation point to the center by enabling Show Grid and hiding the Mandala-Guides layer. Then I was able to create the full guide, as in the tutorial mentioned above. I saved the file (and that is what is enclosed).
After that, I enabled the Mandala-Guides layer, hoping the simplified guides (I got rid of all the octagons) would let me snap as needed. I selected the Guide-Box (Curve), and picked the pen tool. I successfully moved the cursor to the center point and clicked on to start drawing. Then I managed to move the cursor up a bit but then everything froze:
I waited a few minutes, finally clicked on the system icon (the little x in the upper right corner) to close, and this is what I got:
Adam