I've edited the message while you wrote your answer.Originally Posted by pstudio
Yes, the problem was that I forgot the "Pen" property. Thanks.
I've edited the message while you wrote your answer.
Yes, the problem was that I forgot the "Pen" property. Thanks.
No signature provided yet.
Last weekend I did fixed some bugs, added some brushes and added save and load map files in internal default format (not customizable yet). When I finished the user manual I decided that I don't like the way I planned to manage map layers and that the way that TileStudio manages map layers is much better, so I didn't released it yet because the internal file format is obsolete before to be released.
So, next milestone is to re-define that internal file format. Once I implement it I'll release version 0.1, just to allow you to test it and tell me what do you think about it.
No signature provided yet.
Just to say that the new internal file format isn't working, that's why I didn't released yet. I don't know whay I'm doing wrong. I still working on it.
No signature provided yet.
I've fixed the file format issue (I forgot to write the "end" of the tileset name, so it didn't find it when loading). I did also some "invisible" stuff.
I was planned to release it as "version 0.1" but I think I will not until I add all stuff I planned (multilayer and "file format description language") or until somebody ask for it.
No signature provided yet.
I'm glad to see this tool is still begin worked on. (even if slowly) Would the tool Tiled be of any inspiration?
I've been using it myself for my Game Maker Studio projects and it's pretty decent. There could be a few more features of course. I like how they included isometric as well as the normal 1:1 tile grid.
Something I'd love to see is a hex tile grid. Maybe animated tiles and of course the ever popular auto-tiles.
Would you consider making Tile Studio export to various formats? XML, match other popular tools (like Tiled), JSON and others?
Jason McMillen
Pascal Game Development
Co-Founder
At the moment only normal 1:1 tile grid will be supported. But since the map drawer/editor is a TFrame with all functionality inside it should be easy to add isometric and hex tile grids too.
Not sure what "auto-tiles" is. Animated ones might be in the future too.
Actually this will be the strong point. The application will allow to define the output format by using a simple description language, simpler than the original TileStudio.
No signature provided yet.
Interesting to read a thread like this...
@Ñuño Martínez, sorry for not replying, I don't remember ever seeing your mail.
Anyway, I've tried get Tile Studio to compile in Lazarus many times over the years and always failed, until this time.
Now I got the tile editor working (almost) completely. The map editor however doesn't do much. There are some really strange things going on with the Canvas.Draw function with transparent bitmaps.
It took me quite a while to figure out that the behavior of TabControl.TabIndex and Form.Resize are different from Delphi in whether events are fired or not. I don't know if such things are bugs or maybe intentional choices.
Anyway, the newest source code is available on github: https://github.com/Wiering/Tile-Studio/tree/lazarus, maybe some of you lazarus experts immediately see what the issues are, any help would be appreciated!
Don't worry. You're here now!
I know, I had the same problems. No idea why it doesn't work correctly.
I recommend to use TPageControl instead. The advantage is you don't need to "draw" the stuff by yourself tracking the tab changes. The bad thing is that it may need more memory but I think it is not your case.
Ok, I've look at the GitHub project and I have to say something:
Use subdirectories! Please. "src" for sources and "bin" for the final binary. And "docs" for documentation. Really, it will help a lot.
The main problem I had when I worked with your code is that most of it is in the main form. That mean thousand controls and it's hard to keep track of they all. You should split the stuff, using TFrame for different control groups (i.e. I did a TFrame for the "brush" selector, another one for the tiles selector, etc). This will also group your code and increase the order.
Also separate "logic" and "GUI" should help too. For example, split the "tile selector" in two units, one for the logic (i.e. add, remove, replace, load, save...) and the other will be the GUI that just renders the tiles and allows the user to select one of them.
No signature provided yet.
Posting Permissions
Reply With Quote
Bookmarks