Skip to main content ↑ ↓
Topic: QtSphere IDE 0.6.0 (Read 1066475 times) previous topic - next topic
0 Members and 18 Guests are viewing this topic.

Re: QtSphere IDE 0.2.5

Reply #106 –
I'm working on importing spritesets from images. Unlike the original editor, which immediately saved the generated spriteset, QtSphere IDE just imports the image, so you can make changes before saving it, or in case it didn't come out right. Also as you can see, I combined the frame width/height and the transparency i/o dialogs into one for user convenience.

Re: QtSphere IDE 0.2.5

Reply #107 –
That's a good idea, not saving the image right away to facilitate experimentation.  I've always been annoyed when an editor automatically saves something you just created that you might end up having to delete and start over; IDEs in particular are notorious for forcing you to save newly created projects (Sphere Studio also being an offender here).

As a suggestion for a future iteration it could be useful to see an actual preview of the generated spriteset before actually generating it; this would let the user fiddle with the values and see the results in realtime, before clicking OK.

Re: QtSphere IDE 0.2.5

Reply #108 –
Quote from: Fat Cerberus – on
That's a good idea, not saving the image right away to facilitate experimentation.  I've always been annoyed when an editor automatically saves something you just created that you might end up having to delete and start over; IDEs in particular are notorious for forcing you to save newly created projects (Sphere Studio also being an offender here).
Yeah, it just always felt really awkward. The menu even says "Import", which generally implies that something is being included or generated without being saved automatically.

Quote from: Fat Cerberus – on
As a suggestion for a future iteration it could be useful to see an actual preview of the generated spriteset before actually generating it; this would let the user fiddle with the values and see the results in realtime, before clicking OK.
That should be pretty easy with Qt's slots/signals.

Right now I'm having an extremely frustrating issue with the direction objects in the direction list being corrupted/reset after the function that they're created in returns. I'm not sure if it's caused by my pointer handling or Qt's implicit sharing system, but based on my experience with the same thing happening to individual QImage objects, I'm guessing it's the latter.

Re: QtSphere IDE 0.2.5

Reply #109 –
The way the system is described, it seems you’re meant to pass around the shared object itself, rather than a pointer to it.  This ends up being efficient because the object is merely a wrapped pointer so there’s no significant cost in making copies of it.

What I’m guessing is that you’re creating the object on the stack and then returning a pointer to it.  This leaves you with a dangling pointer because the object itself goes out of scope.  A pointer doesn’t count as a live reference, it’s just a dumb memory address.

Code: (c++) [Select]
CSomeClass object(arg1, arg2);
return &object;  // dangling ptr, ticking time bomb

Re: QtSphere IDE 0.2.5

Reply #110 –
Uh...so it turns out  the directions being reset was caused by two really dumb mistakes. The direction.name was being reset because of what you described. Changing it from a char* to a QString fixed the issue.
As for the frames being "reset", I created each frame when looping through num_frames (an integer read from the .rss file), but forgot to actually add them to direction.frames!

Whatever, at least it works now, and importing is mostly finished, as you can see from the images. The spriteset in imported.png is ugly but it isn't meant to be pretty, since I was using it to make sure that the given color is being properly replaced with transparency (or another color if you don't need transparency).

Re: QtSphere IDE 0.2.5

Reply #111 –
Hehe, anti-aliasing and colorkeyed transparency indeed don't get along very well.

Re: QtSphere IDE 0.2.5

Reply #112 –
That was done deliberately in GIMP to see how the 1.x editor handles  similar shades of the given color. It's also why I added a gradient to the last frame.

Also importing works now, and the created file can be read by both QtSphere IDE and the original editor, though I don't know about Radnen's editor. sha256sum reports that the file generated by my editor has a different checksum from one generated by the original editor, but I suspect that's because of random junk in the reserved byte arrays.

Re: QtSphere IDE 0.2.5

Reply #113 –
Per spec (what little “spec” there is for the v1 formats...) I think the reserved bytes are always supposed to be zero’d.  Doing so helps with forward compatibility since the “default” for any new value can safely be assumed to be zero.

That said, it’s unlikely those formats will be extended in any way going forward. :P

Re: QtSphere IDE 0.2.5

Reply #114 –
Alright, I zeroed out the reserved byte arrays and set the default frame delay to 8 (since I had it at 1), and now it creates a spriteset identical to one generated by the 1.x editor if you renamed the empty direction to "north", added "east", "south", and "west" directions, and gave each direction three frames.

Re: QtSphere IDE 0.2.5

Reply #115 –
This thread is in desperate need of an update since QtSphere IDE is still in development even though it isn't my main project. I'm currently working on the map editor, and even though it's still far from completion, it fully loads map files, and this is what the editor itself looks like so far:

It might end up being able to display the first frame of each entity as a preview, rather than a generic icon. I haven't decided yet.