While I was working on a new pixel game, I noticed few little issues that makes the bitmap editor less comfortable.
First, I saw that the minimum size of paint brush is 2x2 pixels instead of 1x1 pixels so I had to edit the sprite on Paint software and then upload it back to the project. Second, moving a selection box by arrow keys makes the box move less than one pixel every time. And third, when I created a new shape (ellipse, rectangle or line) it was displayed as a vector shape, then after I released the mouse button it converted to bitmap and got jagged and not symmetrical like Scratch 1.4 paint editor was.

Hope I helped and you can slove those issues on next updates!

bump

Yep, noticed all these too. Also, the vector size is way too large now compared to what it used to be. But for me bitmap is 1x1 pixels…

I think you need to zoom out first to get the 1x1 pixel.

mathfreak231 wrote:

I think you need to zoom out first to get the 1x1 pixel.

If it's true then it need to be fixed.

relrel wrote:

While I was working on a new pixel game, I noticed few little issues that makes the bitmap editor less comfortable.
First, I saw that the minimum size of paint brush is 2x2 pixels instead of 1x1 pixels so I had to edit the sprite on Paint software and then upload it back to the project. Second, moving a selection box by arrow keys makes the box move less than one pixel every time. And third, when I created a new shape (ellipse, rectangle or line) it was displayed as a vector shape, then after I released the mouse button it converted to bitmap and got jagged and not symmetrical like Scratch 1.4 paint editor was.

Hope I helped and you can slove those issues on next updates!

Actually, it is 1*1 pixel. The bitmap editor for Scratch 2.0 is double-resolution (which means it's capable of using subpixels). When a bitmap sprite is exported from Scratch 2.0, the double-resolution factor doesn't sit well with computers and the result is a sprite that is twice the size of what is originally was in Scratch 2.0.

The selection box is supposed to move by one pixel each time, but it's known to snap to a subpixel grid if you try to move something when zoomed in at higher levels (last I checked, problems start at 400%).

The impreciseness of the shape tools is an issue that the ST knows about. That deals more with vector-to-bitmap conversion. I'm not sure when a fix for that is coming, though.

You might be wondering “Why double-resolution?”. Well, some people on the ST thought that by making things double-resolution, projects would look okay when in fullscreen mode (unfortunately, due to the way Flash works, Scratch 2.0's fullscreen mode is not 2x size like it is in Scratch 1.4 presentation mode. This can sometimes result in images possibly looking wonky when in 2.0's fullscreen).

That being said, there are some of us on the ST who are not big fans of the double-resolution, me being one of them. Like you, I find the Scratch 2.0 bitmap editor rather difficult to use because of these issues and find myself switching over to an external editor (or even back to Scratch 1.4) because of these issues. Personally, I think switching to standard resolution would solve most of the confusion issues regarding the actual resolution of sprites, but for developers, there's the concern about a bug trail caused when doing so. So if you or anyone has questions, suggestions, or concerns, feel free to post them.

cheddargirl wrote:

relrel wrote:

While I was working on a new pixel game, I noticed few little issues that makes the bitmap editor less comfortable.
First, I saw that the minimum size of paint brush is 2x2 pixels instead of 1x1 pixels so I had to edit the sprite on Paint software and then upload it back to the project. Second, moving a selection box by arrow keys makes the box move less than one pixel every time. And third, when I created a new shape (ellipse, rectangle or line) it was displayed as a vector shape, then after I released the mouse button it converted to bitmap and got jagged and not symmetrical like Scratch 1.4 paint editor was.

Hope I helped and you can slove those issues on next updates!

Actually, it is 1*1 pixel. The bitmap editor for Scratch 2.0 is double-resolution (which means it's capable of using subpixels). When a bitmap sprite is exported from Scratch 2.0, the double-resolution factor doesn't sit well with computers and the result is a sprite that is twice the size of what is originally was in Scratch 2.0.

The selection box is supposed to move by one pixel each time, but it's known to snap to a subpixel grid if you try to move something when zoomed in at higher levels (last I checked, problems start at 400%).

The impreciseness of the shape tools is an issue that the ST knows about. That deals more with vector-to-bitmap conversion. I'm not sure when a fix for that is coming, though.

You might be wondering “Why double-resolution?”. Well, some people on the ST thought that by making things double-resolution, projects would look okay when in fullscreen mode (unfortunately, due to the way Flash works, Scratch 2.0's fullscreen mode is not 2x size like it is in Scratch 1.4 presentation mode. This can sometimes result in images possibly looking wonky when in 2.0's fullscreen).

That being said, there are some of us on the ST who are not big fans of the double-resolution, me being one of them. Like you, I find the Scratch 2.0 bitmap editor rather difficult to use because of these issues and find myself switching over to an external editor (or even back to Scratch 1.4) because of these issues. Personally, I think switching to standard resolution would solve most of the confusion issues regarding the actual resolution of sprites, but for developers, there's the concern about a bug trail caused when doing so. So if you or anyone has questions, suggestions, or concerns, feel free to post them.

Thank you

cheddargirl wrote:

relrel wrote:

While I was working on a new pixel game, I noticed few little issues that makes the bitmap editor less comfortable.
First, I saw that the minimum size of paint brush is 2x2 pixels instead of 1x1 pixels so I had to edit the sprite on Paint software and then upload it back to the project. Second, moving a selection box by arrow keys makes the box move less than one pixel every time. And third, when I created a new shape (ellipse, rectangle or line) it was displayed as a vector shape, then after I released the mouse button it converted to bitmap and got jagged and not symmetrical like Scratch 1.4 paint editor was.

Hope I helped and you can slove those issues on next updates!

Actually, it is 1*1 pixel. The bitmap editor for Scratch 2.0 is double-resolution (which means it's capable of using subpixels). When a bitmap sprite is exported from Scratch 2.0, the double-resolution factor doesn't sit well with computers and the result is a sprite that is twice the size of what is originally was in Scratch 2.0.

The selection box is supposed to move by one pixel each time, but it's known to snap to a subpixel grid if you try to move something when zoomed in at higher levels (last I checked, problems start at 400%).

The impreciseness of the shape tools is an issue that the ST knows about. That deals more with vector-to-bitmap conversion. I'm not sure when a fix for that is coming, though.

You might be wondering “Why double-resolution?”. Well, some people on the ST thought that by making things double-resolution, projects would look okay when in fullscreen mode (unfortunately, due to the way Flash works, Scratch 2.0's fullscreen mode is not 2x size like it is in Scratch 1.4 presentation mode. This can sometimes result in images possibly looking wonky when in 2.0's fullscreen).

That being said, there are some of us on the ST who are not big fans of the double-resolution, me being one of them. Like you, I find the Scratch 2.0 bitmap editor rather difficult to use because of these issues and find myself switching over to an external editor (or even back to Scratch 1.4) because of these issues. Personally, I think switching to standard resolution would solve most of the confusion issues regarding the actual resolution of sprites, but for developers, there's the concern about a bug trail caused when doing so. So if you or anyone has questions, suggestions, or concerns, feel free to post them.

Have you noticed also how the smallest size of vector is now too large? They changed it; it used to be way smaller, but now it's not small enough.

turkey3 wrote:

cheddargirl wrote:

relrel wrote:

While I was working on a new pixel game, I noticed few little issues that makes the bitmap editor less comfortable.
First, I saw that the minimum size of paint brush is 2x2 pixels instead of 1x1 pixels so I had to edit the sprite on Paint software and then upload it back to the project. Second, moving a selection box by arrow keys makes the box move less than one pixel every time. And third, when I created a new shape (ellipse, rectangle or line) it was displayed as a vector shape, then after I released the mouse button it converted to bitmap and got jagged and not symmetrical like Scratch 1.4 paint editor was.

Hope I helped and you can slove those issues on next updates!

Actually, it is 1*1 pixel. The bitmap editor for Scratch 2.0 is double-resolution (which means it's capable of using subpixels). When a bitmap sprite is exported from Scratch 2.0, the double-resolution factor doesn't sit well with computers and the result is a sprite that is twice the size of what is originally was in Scratch 2.0.

The selection box is supposed to move by one pixel each time, but it's known to snap to a subpixel grid if you try to move something when zoomed in at higher levels (last I checked, problems start at 400%).

The impreciseness of the shape tools is an issue that the ST knows about. That deals more with vector-to-bitmap conversion. I'm not sure when a fix for that is coming, though.

You might be wondering “Why double-resolution?”. Well, some people on the ST thought that by making things double-resolution, projects would look okay when in fullscreen mode (unfortunately, due to the way Flash works, Scratch 2.0's fullscreen mode is not 2x size like it is in Scratch 1.4 presentation mode. This can sometimes result in images possibly looking wonky when in 2.0's fullscreen).

That being said, there are some of us on the ST who are not big fans of the double-resolution, me being one of them. Like you, I find the Scratch 2.0 bitmap editor rather difficult to use because of these issues and find myself switching over to an external editor (or even back to Scratch 1.4) because of these issues. Personally, I think switching to standard resolution would solve most of the confusion issues regarding the actual resolution of sprites, but for developers, there's the concern about a bug trail caused when doing so. So if you or anyone has questions, suggestions, or concerns, feel free to post them.

Have you noticed also how the smallest size of vector is now too large? They changed it; it used to be way smaller, but now it's not small enough.

Hmm, that's kind of odd (I would have expected the smallest size to be relatively pixel sized). I'll ask the ST developers about it.

cheddargirl wrote:

turkey3 wrote:

cheddargirl wrote:

relrel wrote:

While I was working on a new pixel game, I noticed few little issues that makes the bitmap editor less comfortable.
First, I saw that the minimum size of paint brush is 2x2 pixels instead of 1x1 pixels so I had to edit the sprite on Paint software and then upload it back to the project. Second, moving a selection box by arrow keys makes the box move less than one pixel every time. And third, when I created a new shape (ellipse, rectangle or line) it was displayed as a vector shape, then after I released the mouse button it converted to bitmap and got jagged and not symmetrical like Scratch 1.4 paint editor was.

Hope I helped and you can slove those issues on next updates!

Actually, it is 1*1 pixel. The bitmap editor for Scratch 2.0 is double-resolution (which means it's capable of using subpixels). When a bitmap sprite is exported from Scratch 2.0, the double-resolution factor doesn't sit well with computers and the result is a sprite that is twice the size of what is originally was in Scratch 2.0.

The selection box is supposed to move by one pixel each time, but it's known to snap to a subpixel grid if you try to move something when zoomed in at higher levels (last I checked, problems start at 400%).

The impreciseness of the shape tools is an issue that the ST knows about. That deals more with vector-to-bitmap conversion. I'm not sure when a fix for that is coming, though.

You might be wondering “Why double-resolution?”. Well, some people on the ST thought that by making things double-resolution, projects would look okay when in fullscreen mode (unfortunately, due to the way Flash works, Scratch 2.0's fullscreen mode is not 2x size like it is in Scratch 1.4 presentation mode. This can sometimes result in images possibly looking wonky when in 2.0's fullscreen).

That being said, there are some of us on the ST who are not big fans of the double-resolution, me being one of them. Like you, I find the Scratch 2.0 bitmap editor rather difficult to use because of these issues and find myself switching over to an external editor (or even back to Scratch 1.4) because of these issues. Personally, I think switching to standard resolution would solve most of the confusion issues regarding the actual resolution of sprites, but for developers, there's the concern about a bug trail caused when doing so. So if you or anyone has questions, suggestions, or concerns, feel free to post them.

Have you noticed also how the smallest size of vector is now too large? They changed it; it used to be way smaller, but now it's not small enough.

Hmm, that's kind of odd (I would have expected the smallest size to be relatively pixel sized). I'll ask the ST developers about it.

That's weird. The other day the smallest size was about 3px, but yesterday it was 1 pixel, but at times it wouldn't go back down to 1 and only stay at 3. Probably another IE glitch.