Ignition V1.7 now up!
Monkey Forums/Monkey Programming/Ignition V1.7 now up!
| ||
| Hi, I have decided to upload the first version of the tiled loader so people can get to experiment with it. Note that it's far from finished. The demo can be download from our member area at http://monkey.playniax.com/ Read the source code comments for more information! For tiled support you also need v1.7 Changes: - Moved the iGuiJoystick class to the plugins folder. - Separated the content manager from the engine and is now a 'standalone' module. New: - Virtual joypad - Background object for the system gui - iLanguage class to support multiple languages * strings.monkey * Added: - iAsc - iChr - iLen - iStringArrayToFloat - iStringArrayToInt - iStringToArray - iStringToIntArray - iStringToFloatArray Virtual joypad demo: http://www.playniax.com/share/demos/vpad/MonkeyGame.html |
| ||
| And for people who don't own Ignition yet, I have started to work on online docs (WIP) http://www.docs.playniax.com/ |
| ||
| Many thnx, vpad is greate stuff. |
| ||
| Nice work and new features :) In the meantime Tony is there a built in solution in Ignition to solve the problem with lines appearing between map tiles when scaling up from the virtual resolution? I know some people overlap tiles, and some expand the borders around individual tiles in the tilesheet. What is the best way to handle this in Ignition? Theres an interesting page over at the gamesmakers site which explains a little better the problem http://www.yoyogames.com/tech_blog/8 |
| ||
| The tile editor has an 'export to monkey' option and when enabling padding the editor adds 1 extra pixel around the tiles solving this problem. I have never liked these solutions but it seems there are no other ways, not that I know of anyway. |
| ||
| Hi! This is my first post on this forum :) 1st of all thanks for your work with Ignition. I'm really enjoying both Monkey and your framework! Just a couple of things: - I'm not able to find iObject and iLayer classes in the Ignition docs (tried with the 2 latest versions), could you please check if I'm wrong? Also a suggestion for the docs: it would be really great if class/methods/ name would be clickable, instead of the type itself... including super classes as well! - I've just published a DAME map editor exporter for Monkey. There's an example where Ignition uses the exporter output classes to draw the tilemap with animated tiles. Maybe you find useful the snippet! |
| ||
| Thanks Tony for the info on the padding. I've update my tile map editor and it works like a dream. |
| ||
| Cool. Thanks guys! You are right, iLayer and iObject do not show up in the docs. I think something went wrong while building the docs. I will fix it. I will check out your DAME map editor exporter for Monkey. it would be really great if class/methods/ name would be clickable You mean like the monkey docs? |
| ||
| Cool! I leak Ignition docs, what it meant, eg: Method GetTiles:iTile [] (_x:Int, _y:Int, _width:Int, _height:Int) - Instead of 'Method', what is linkable is 'GetTiles' - Also, if iTile would link to iTile class docs, it'll be even more nice |
   |