Hey there. This is probably gonna be a long message.
So, I've been developing my game Space Ships. I usually use the bitmap editor for simple things, if I wanna do pixel art I use piskelapp.com.
But, I needed to use some vector graphics, for the player sprite. It looks easy to make,
but really, I took maybe 20 minutes for making a good looking green triangle.
So: Here is my Vector Sprite Editor Complains LIST.
1. The bucket tool. This just confused me, I just don't know why it doesn't works like normal
bucket tools. Why do you need to fill in by hand, and still have the bucket tool?
The bucket tool is made to fill in empty spaces.
2. “Eraser” tool. For example, when you do a mistake in your hard work and you really
wanna erase it. But, the only “eraser” option is clearing the whole sprite.
This one is just actually, why.
3. This is probably just how vector works, (I'm best on bitmap and pixel art)
but I wanna know why the vector line and pencil option, behaves like this:
When you connect a line, it is just becoming extremely spiky.
I have no idea why it acts like that, and I really hope that this is just a scratch issue and not
vector behavior.
4. The shade on text. Even if this kinda looks good and isn't really visible, it kinda bugs me.
I think you should keep it, but give a option if you wanna use the shade option or not.
So I hope someone gets to see this and give me feedback. Maybe I'm just ranting about
obvious things that vector is made to do, but please, give me some feedback.
Thanks!

1. You clearly don't understand how vector works if you think it's “supposed” to fill in. Vector is drawn in shapes/lines/strokes, and using the bucket fills in those shapes/lines/strokes, not the space. However, I have seen Inkscape do what you want by making a new shape that is the “fill”. Support for that(and keeping what we already have).
2. Um, you still don't understand how vector works. This is actually something that would be REALLY complicated for Scratch to do, because again, everything is stored in shapes, not pixels that can just be erased at any moment.
3. I don't understand.
4. I guess support. It doesn't really need to be there.

FancyFoxy wrote:

1. You clearly don't understand how vector works if you think it's “supposed” to fill in. Vector is drawn in shapes/lines/strokes, and using the bucket fills in those shapes/lines/strokes, not the space. However, I have seen Inkscape do what you want by making a new shape that is the “fill”. Support for that(and keeping what we already have).
2. Um, you still don't understand how vector works. This is actually something that would be REALLY complicated for Scratch to do, because again, everything is stored in shapes, not pixels that can just be erased at any moment.
3. I don't understand.
4. I guess support. It doesn't really need to be there.

I don't really get vector, so I don't really have a excuse. I'm very sorry that I probably just said obvious things, I think I will stick to bitmap and pixels

Anino3 wrote:

FancyFoxy wrote:

1. You clearly don't understand how vector works if you think it's “supposed” to fill in. Vector is drawn in shapes/lines/strokes, and using the bucket fills in those shapes/lines/strokes, not the space. However, I have seen Inkscape do what you want by making a new shape that is the “fill”. Support for that(and keeping what we already have).
2. Um, you still don't understand how vector works. This is actually something that would be REALLY complicated for Scratch to do, because again, everything is stored in shapes, not pixels that can just be erased at any moment.
3. I don't understand.
4. I guess support. It doesn't really need to be there.

I don't really get vector, so I don't really have a excuse. I'm very sorry that I probably just said obvious things, I think I will stick to bitmap and pixels

It's okay.