0 Members and 1 Guest are viewing this topic.
That's a lot of features O_oI can only think of a couple things that are missing:Ability to scroll (So we can edit, say, a 32*32 sprite at 4x zoom)Cut/Copy/Paste (Box selection, unless you really want to add the ability to deal with user-drawn shapes )Can't wait to see if you implement this!
Does it work with frames/animations already? if it doesn't, I'd like to see that too
Export function, thats what I've missed in your last version xD
Also would this be an APP? The issue with the other tilemapper was having to archive/unarchive everything back and forth during development. I know I can use Doors or CalcUtil, but when I develop, I prefer that no other ASM stuff is being used on my calc. In other words, only Axe and my work will run. It's quite easy to mess something up in Axe and if it happens to conflict with CalcUtil or Doors it has higher chances to mess things up.
Quote from: Ikkerens on November 29, 2010, 04:06:35 pmExport function, thats what I've missed in your last version xDIt's already in the list, bundled in with an import function.Quote from: DJ Omnimaga on November 29, 2010, 04:09:58 pmAlso would this be an APP? The issue with the other tilemapper was having to archive/unarchive everything back and forth during development. I know I can use Doors or CalcUtil, but when I develop, I prefer that no other ASM stuff is being used on my calc. In other words, only Axe and my work will run. It's quite easy to mess something up in Axe and if it happens to conflict with CalcUtil or Doors it has higher chances to mess things up.There are multiple reasons that this will definitely be an application:Running the program as an assembly executable would take up a large portion of user RAM just to hold the executable. This will leave little free space for anything else, like the data appvar.The finished program will undoubtedly be larger than the assembly executable code limit. (I hope I can even fit it into an app!)This will leave more user RAM free, allowing all data to exist in RAM. This (hopefully) means no constant unarchiving and archiving will be necessary.Leaving more user RAM free will also allow for the free space to be used as an extensive undo/redo history.It seems more suitable for large utilities like this to be an application, anyways.