It’s great, but it’ll probably never see HWA, java, etc. Perhaps if it is an actual problems I will convert it to use off-screen buffers, but I’d prefer not to.ĭownload the version of Chart Object without the HWA checksĮdit: A quote I found from my notes from Fimbul which – probably fairly – describes the situation: I’d be interested to know if there are any people who are strongly bothered by the inability to use it with Direct3D. Well, I thought this would probably do for now. I tried it, and it seemed to ‘just work’ so long as the ‘Display Mode’ setting in the application properties is not ‘Direct3D 8’ or ‘Direct3D 9’ (both of which may cause crashes). The first thing I did was remove the tests which stopped it being added to HWA applications. Today I started work to make the Chart Object HWA compatible (although not actually take advantage of the HWA). It was disallowed as it didn’t appear to work properly with it – nothing would be displayed (except for the pie chart mode, which writes to an internal buffer first). At the time the object was released, this was a separate runtime. The Chart Object I wrote for Multimedia Fusion 2 would not allow itself to be added to hardware accelerated (HWA) applications. Remember, it would take too long to add every feature to every platform, so be conservative. 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.
Clickteam fusion 2.5 platforming glitching full#
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.
Clickteam fusion 2.5 platforming glitching update#
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.
0 kommentar(er)
