![]() Which features are the most important? If people could tell me (on the Clickteam Forums) their top 5 or so features in order I would find it very useful. Encryption is memory was an idea too, but it is questionable how useful that is. Unicode support everywhere would be good, too. Some extra features I was going to add were: Filtering of the object (so that it would changes what the object lists and so forth without actually changing the object), proper subgroups, saving to formats other than Ini files (in particular, making the whole thing work the same but write to the registry or via a server) and full preservation of white space, etc. ![]() Ability to allow/disallow empty groups, etc.Saving objects and global values directly.Lots of actions had custom dialog boxes in MMF.Functions to get the ‘part’ of a string directly.Interaction with the chart object, array object.Alphanum sorting that puts, say, “Hello 12” before “Hello 3”.‘Perform calculation’ expressions that allows summary information to be easily extracted.(Is the latter even possible in other runtimes?) Global data, including across sub-apps.The ordering of the file is preserved (but comments, etc.Case sensitive/insensitive options (including the ability to change it at runtime).Debugging tools, including a dialog that can be opened at runtime.Built in features to save the file in specific directories.Some of the features that Ini++ support are: But I wanted to ask people what features are important to them. This is obviously a fairly big project for me to undertake, and I’m not sure yet that I want to do this. Therefore I propose a cut-down version of Ini++ be created and ported to every platform. There is a demand for a data storage object on other platforms though, and it seems the format of Ini++ is one that appeals to people. Therefore it would be a lot of effort to port to any other platform. One only has to look at the file size and options to realise this. Ini++ is a monster of an object with many, many features. ![]() Many people have asked for Ini++ to be ported to other platforms. In addition, I wanted to float a new idea. It has since been updated again, see here. Thank you to HitmanN and XStar for sending me examples of these problems. Hopefully I’ll be able to fix this in future, but I do not have the tools available to do so quickly. I have been able to reproduce a crash with the encryption. If you previously choose 128 it will stay selected, so you ought to be aware of this. Now the properties panel will not allow any values greater than 127. ![]() This would actually register as infinite. In addition, a minor bug is fixed where the undo and redo stack size could be set to 128 layers. For this reason it is important that every user update to the latest version. The memory leak applied even if the undo stack was disabled. It fixes a couple of memory leaks do with the undo stack. TLDR: Spent too much time in different engines fighting to see what has a working grab top object function > went to Fusion 2.I have issued an update to Ini++ v1.5. But maybe it should be? There's more to do on the game project but I want to get further knowledge and feed back first. This means you can separate two objects or grab them together. The difference is that the collider for fusion 2.5 is the actual shape of the object on screen with fine collision enabled. I tried in unity and still had the same problem and even this engine has the same issue. I've tried godot for a while and couldn't resolve this issue in any simple way. The jank comes in when you try to grab two items on top of each other. In short the coding was easier in this engine despite it being a slight bit jankier. So in short I made this version of the game to start moving away from unity but as it turns out it's easy to do but annoying to determine what engine to move to.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |