Thank you for the bugs and suggestions. It is a great help to me, in order to make my level editor better.
Quote:
* To me it doesn't make sense to hide the player start point in the level properties dialog. It's nicer to have it available in one of the menus directly, but what would make even more sense is to just allow it to be draggable like platforms or any other game object.
It
is in the menus, Object -> Set Starting Point. I might make it draggable.
Quote:
* Give objects some default values instead of zeroes so that they can operate "out of the box" so that users arn't left guessing. In addition, please remember which page of objects a user was last on.
Good idea, will do.
Quote:
* If the user accidentally closes the application, there is no warning to save changes before closing, the editor is simple closed and any changes lost. Include a dialog to accomodate this.
Those dialog boxes are annoying, but ok. I'll make it ask you only if the file is altered, though.
Quote:
* There is no way to delete the playtest starting point.
Yeah, if I made starting points draggable and selectable like other objects, I could have the user press delete. I'll do that.
Quote:
* Undo and redo are very buggy. I have seen undo make items appear that never existed in the level and generally create a mess. Using undo and redo a few times easily throws an "Object variable with block not set" error, which means that an object variable is not pointing to any instance of an object when you try to use it. My disposition is that you should remove this feature until the bugs are worked out of it. It's not particularly needed anyway.
I need to start over on those aspects of the program. They are pretty bad.
Quote:
* It would be nice to see an object list editor, such as you might find in a 3D package. An interface that lists all the objects currently loaded into your level and gives you the ability to select, edit, delete or hide them using the list. This is most useful for a crowded level. This approach would also require that objects have uniquely identifying names.
Personally, I would never use this for Stinkoman. But to compromise, I'll make check boxes next to the list of levels to include objects for, so you could enable only objects in a certain level.
Quote:
* Include `Properties` option in the right click context menu for objects.
Check.
Quote:
All in all, a good effort, but what's the Flash.oca file for?
I'm pretty sure my program needs it to playtest levels. It shows up as a reference.
Quote:
Your last two file mirrors also do not work.
Grr, I hate it when they don't let me link to my own file. I'll make a web page with the link on it.
Quote:
Finally, the source code would make an interesting read.
I'm hesitant.