Construct image editor bugs and PNG transparency suggestion

I still can't reproduce the bug myself.

What Operating System name and version do you have?

I still can't reproduce the bug myself.

What Operating System name and version do you have?

That's strange. I'm using Windows XP Professional SP 2.

Hmm. Cannot reproduce it on \\Araquiel (XP sp2), or \\Cortana (Vista sp1). Your image serves as enough proof though. I'll file this on SourceForge.

There's also another bug I found. The eraser tool only does 2 pixels. It cannot be shrunk to 1 pixel.

I guess I'll file that on SourceForge myself. That's easy to describe compared to this bug.

However, people have been shooting down bug and feature requests recently due to some sort of feeling that Construct won't have x support if Ashley fixes or adds y.

It wasn't "some sort of feeling." I clearly explained my reasons, and they weren't without merit. I wasn't arguing just to argue, you know. So please don't take it personally because it's nothing against you.

You know what they say about arguing on the internet, folks.

Just ignore that post (btw, my comment wasn't even directed towards deadeye, I was just saying people here in general). What about the bugs? I saw that Ashley replied to this post and got excited for nothing. I am not here to argue with anyone. Don't derail this topic. So anyway, Ashley, what do you think? I mean about the bugs I just reported, ignore any comments made on the side. That's probably the least important thing we should be discussing right now.

I've also ended up annoyed trying to paste various alpha graphics in to the picture editor. Importing 32 bit PNGs with alpha channel is pretty bulletproof, but I do consider it a bug if you can't paste in alpha images. So I will try to do something about it.

I've also ended up annoyed trying to paste various alpha graphics in to the picture editor. Importing 32 bit PNGs with alpha channel is pretty bulletproof, but I do consider it a bug if you can't paste in alpha images. So I will try to do something about it.

Have you also tried the paint bucket tool? Why does it act so.. weird? Are you getting the same behavior? By that, I mean how it fills in only some pixels while leaving some spots unchecked. Is that happening to you?

Also, as someone else mentioned in this post. The square select tool just flat out doesn't work. Although I don't really have any use for it as I just import my graphics. I'm not sure how to give an example for you to reproduce but well, just try using it. You'll probably see what I mean.

Another thing I noticed is that the pencil tool doesn't do anything unless you drag it. Clicking with it doesn't create a pixel unless you drag the mouse.

Also, like I mentioned the eraser tool only does 2 pixels (even if the width is set to anything else).

But other than that, I can't think of any other things that really strike me as odd. There is bound to be more stuff wrong with the picture editor but these seem like the most annoying of them all (the whole paint bucket and transparency issue, especially).

Edit: I probably should report the rest of these in the bug tracker right? But compared to the whole transparency bugs and such, these are pretty basic issues. I don't want to clutter the bug tracker with every minute little thing.

Just ignore that post (btw, my comment wasn't even directed towards deadeye, I was just saying people here in general).

Okay then, I'm sorry I assumed. I just don't want there to be any hard feelings. It's not my intention to make enemies here.

> Just ignore that post (btw, my comment wasn't even directed towards deadeye, I was just saying people here in general).

>

Okay then, I'm sorry I assumed. I just don't want there to be any hard feelings. It's not my intention to make enemies here.

Don't feel that way. We're all friends here. A little debate here and there doesn't make us enemies. It just helps serve as meaningful discussion as to what this program will become or what direction will it be taken OR something like that, I don't know. However, I still think that if something can be fixed or if something can be done more efficiently, it should. Workarounds are good but they shouldn't be used for everything. I could just import my image as a 32 Bit PNG, but then what will become of the image editor? The bugs that it has need to be fixed sooner or later. If something can be done more efficiently, it should and that's what I'm trying to help with. I am not trying to impede on any progress that this program is making, just giving some suggestions on how to make Construct much more efficient and productive to use.

But I'm sorry for that other post. I never thought of making a grid that way. I forgot my basic math. But that post has already been put to rest. I look forward to the tilegrid object, whenever it may be released, although your method works too.

Yeah, I shouldn't have put that remark in my earlier post on this topic. But CaptainOblivious' posts struck me as slightly condescending at first (in the sense that it seemed like he didn't read my post), but that was only because I misunderstood what he was trying to say and because I didn't explain everything fully. He actually really helped me out here. I shouldn't have spoken so soon.

Anyway, just don't worry about it. I don't even really care about whatever it is we were talking about anymore. This post is about the bugs in the image editor, that's all I really care about right now. So let's just keep this on topic and stop talking about a thread that's been locked and put to rest already.