> 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.