Logic to handle it on backend side, logic to handle it on user side. Multi-z support will require additional effort and rewriting of parser. A lot of good ideas were taken from there.Special thanks to SpaceManiac for his amazing SpacemanDMM parser. Thanks to original FastDMM made by monster860 and later supported by TG. You can find application repository here No dependencies required, all packages are fully self containable.Īt the moment I'm providing distributive for Windows 圆4 only, but in short period of time I'm planning to add distributives for Linux and x32 platforms as well. Open releases page and download distribution package you want. Issues and proposals could be send on GitHub repository. Recent environments/maps option like in FastDMM.įeedback of usage experience is really welcom.Same could be sad about map creation/map expanding and so on. Such paths will be just skipped and removed from map. Divide your z-levels in different files and use Map Synchronization option.Īlso StrongDMM doesn't handle unexisted paths (which were removed from environment, but still exist on map). Multi-z maps are absolutely unmaintainable from the perspective of Open Source contribution. StrongDMM doesn't support multi-z map files. You don't need to manually convert map format after editing. You can open different maps in different files and work with them like if they are in the same file, but on different z levels. Searching and ability to show only instances variables. Now you can view instances variables in selection menu.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |