maxen

I used the vector flood fill tool instead of the gradient tool as hangman did. But Sean is absolutely right: In the appearance panel is an additional fill listet - delete it and booom - everythings fine! Thanks for your on point answer - your support is superb as always. I guess I have learn about the appearance panel now...

Well, I really did nothing special. Just added the bitmap fill to an already filled curve... I created the pattern myself in AD and saved them as assets. But the same thing happens when I saved the pattern as .png and reloaded it as asset to use for the bitmap fill.

@GarryP:Yes, it's the beta. @Pyanepsion: The stages are from the bottom to the top layers. Create a curve, fill it solid. Then apply a bitmap fill. If you then remove the bitmap fill by switching the fill mode to "none" , the curve retains it's fill from before the bitmap fill. This fill is then locked and can't be removed. Nevertheless you can change the color.

Here's a file: AD-bitmapFillBug.afdesign

AD 2.4.2301 / Win10 When I used a bitmap fill on an object with solid color fill and then switch back to "fill: none" to get rid of the bitmap fill, the objects fill color can't be set to "none" (transparent) but will switch to the original fill color despite stating it's not filled at all according to the fill icons. However, the color itself can be changed, but as soon as I turn the opacity down, the original color creeps in.

That's crazy - I'm blown away! Never thought about that...

Well, my fault. Didn't switch the context tool.

Don't know if it's only in the current beta (AD 2.3.0.2096) or also in earlier releases the case: Once a bitmap fill is applied to an objects stroke it can't be adjusted anymore (at least I can't figure out a way to do so). Only way at the moment is: apply the fill to the area, adjust it, then apply it to the stroke too and then delete the fill for the area. If you want to djust it - repeat the whole precedure.

I don't remember having not this behaviour. Hardware acceleration is turned on.

I imported a SVG-file of a GPX-Track, and edited the points. Selecting, deleting and modifing nodes is smooth as long as the hole curve is shown in the editor. As soon as I zoom in to select single points, AD becomes extreme unresponsible. I'm talking about multiple minutes, not seconds. I'm not on a slow machine: i9-9900x and RTX4080+RTX2080. I attached a file, zoom in until you see the single nodes and try to select fife or six via rectangle selection and delete them. My 4080 goes up to nearly 30% to usage, GPU about 5% while AD freezes. course_E.svg

I still hope they improve this fearure. Another bug is, when zooming in on a curve with a lot of points (as in my example above), AD becomes absolute inresponsive. You literally can't do anything because AD seems to recalculate all the time, even, if you don't do anything.

Sorry, yes - wrong section. Should have been postet in Beta section. If the change it's intentionally, just delete the posts. Thanks.

zoom using numpad +/- doesn't work Win 10 | RTX 4080 | AD/AP 2.2.0.1903

Note how the behaviour changes, after setting it to "single radius", changing the corner type and setting it to 0, then turning off "single radius" again.

Here your go: 2023-06-29 15-16-08.mp4