April 2015 update of “Ini++ v1.5”

The Multimedia Fusion v2.5 extension manager now contains the April 2015 version of Ini++ v1.5. This is a small update that fixes a problem with one of the expressions.

This version is only available from the extension manager. My website no longer contains the latest version.

The description text for the latest version ends with the words “April 2015 build”, as shown below:

Extention manager


New version of Ini++ fixes crash

I have updated the Multimedia Fusion 2 extension Ini++. The update fixes a crash. This crash only occurred when both encryption and disk access were enabled, as far as I know. This build hopefully fixes the problem. It is referred to as the October 2013 build (sorry for it taking until mid-November to release it!)

Thank you to Logan Apple for his extremely useful help in reproducing this problem.

Update: It was reported that Build 258.2 and higher of Multimedia Fusion breaks this extension. I could not reproduce this and it appears to work fine in Fusion 2.5.

Download Link

Update to Ini++ v1.5 and thoughts about a new extension

I have issued an update to Ini++ v1.5. It fixes a couple of memory leaks do with the undo stack. The memory leak applied even if the undo stack was disabled. For this reason it is important that every user update to the latest version.

In addition, a minor bug is fixed where the undo and redo stack size could be set to 128 layers. This would actually register as infinite. Now the properties panel will not allow any values greater than 127. If you previously choose 128 it will stay selected, so you ought to be aware of this.

There are still known bugs. I have been able to reproduce a crash with the encryption. Hopefully I’ll  be able to fix this in future, but I do not have the tools available to do so quickly. I apologise for the instability. Thank you to HitmanN and XStar for sending me examples of these problems.

The new version can be downloaded here.    It has since been updated again, see here.

In addition, I wanted to float a new idea. Many people have asked for Ini++ to be ported to other platforms. This will not happen. Ini++ is a monster of an object with many, many features. One only has to look at the file size and options to realise this. Therefore it would be a lot of effort to port to any other 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 I propose a cut-down version of Ini++ be created and ported to every platform. This is obviously a fairly big project for me to undertake, and I’m not sure yet that I want to do this. But I wanted to ask people what features are important to them.

Some of the features that Ini++ support are:

  • Compression
  • Encryption
  • Built in features to save the file in specific directories
  • Setting initial data
  • Debugging tools, including a dialog that can be opened at runtime
  • Case sensitive/insensitive options (including the ability to change it at runtime)
  • Repeated groups and items via renaming
  • The ordering of the file is preserved (but comments, etc. are not)
  • Options to auto-save or not
  • Searching features
  • Sorting and reordering features
  • Merging functions
  • Half-baked ‘subgroups’
  • Global data, including across sub-apps. (Is the latter even possible in other runtimes?)
  • Hashed values
  • Get/Set as text, CVS
  • Listing groups and items
  • ‘Perform calculation’ expressions that allows summary information to be easily extracted. Has anybody ever used that?
  • Undo and redo stacks
  • Escape characters
  • Alphanum sorting that puts, say, “Hello 12” before “Hello 3”
  • Interaction with the chart object, array object
  • Functions to get the ‘part’ of a string directly
  • Lots of actions had custom dialog boxes in MMF
  • Saving objects and global values directly
  • Ability to allow/disallow empty groups, etc.
  • ‘Current group’ set of features

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. Unicode support everywhere would be good, too. Encryption is memory was an idea too, but it is questionable how useful that is.

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. Remember, it would take too long to add every feature to every platform, so be conservative.

Work on Multimedia Fusion extensions

A few of my extensions have known problems with it. I don’t particularly enjoy working on these projects; actually, I pretty much hate it. I have much better things I could be doing. However,  I will try to make the changes when I can.

The known problems are:

Chart Object
  • No support for HWA, which means it doesn’t work in the latest version of MMF
  • No support for Unicode titles, etc.
  • Crash to do with encryption
String Replacer
  • Suspected crash turned out to be due to a different object
Spell check Object
  • Lack of support for additional characters (such as accented characters)
String Replacer
  • Lack of support for additional characters (such as accented characters)

None of these will be much fun at all to work on, or particularly rewarding, so don’t expect progress to be quick. However, hopefully it will happen someday.

Why so many versions of Ini++?

It is often asked why there are so many versions of the Ini++ object. I’ve explained the answer a few times on the Clickteam forums, but I thought it would be worth while explaining it here too.

The answer is: There aren’t.

The situation is that there are two versions of the Ini++ object. The original, and Ini++ v1.5. The latter was made when the Ini++ object behaviour changed. In particular, it no longer enforced items and groups to be in sorted order. Therefore I could not release this as an update to the original, as it could break peoples code. To make things worse, this was not something which could be an option either (without some rewriting of code in the original). It was called Ini++ v1.5 as a nod to Multimedia Fusion v1.5, which was Multimedia Fusion v1.0 plus many new features.

Naturally, there have been different releases of the ‘Ini++ Object’ and the ‘Ini++ v1.5’ objects, but both kept calling themselves that name. There is no ‘Ini++ v1.6’ object. There is no  ‘Ini++ v1.1’. Just the two mentioned. They have the file names ‘Ini++.mfx’ and ‘Ini++15.mfx’ respectively.

So why the confusion?

The problem stems from the fact that although the behaviour of Ini++ v1.5 changed from that of the original, it was still compatible with the original Ini++ object. That is, if you took ‘Ini++15.mfx’ and renamed it to ‘Ini++.mfx’, then any MMF application using the old version would suddenly be ‘upgraded’ to the new version. If you knew your program wasn’t going to stop working because of the changes, this was a great way to make use of the new features without copying over all the events to the new object. Quite a lot of people did this.

It was entirely deliberate that you could do this. In fact, Ini++ v1.5 has a few actions which have no menu items exactly for this purpose. For if they were removed from the code, then this renaming method might not work.

You would expect that if you did this you would see two identical looking objects in the ‘Create new object’ dialog. The same icon, the same text: ‘Ini++ v1.5 Object’. In fact, this is not what you see. Multimedia Fusion will rename the second object to ensure it doesn’t have the same name, so you actually end up with ‘Ini++ v1.5 Object’ and ‘Ini++ v1.5 Object 2’.

The first one (selected in the picture) actually has the file name ‘Ini++.mfx’ and the second has the file name ‘Ini++15.mfx’.

An earlier version of the Ini++ v1.5 Object called itself simply the ‘Ini++ v1.5’ object. Therefore if both ‘Ini++.mfx’ and ‘Ini++15.mfx’ were that version, you would in fact get ‘Ini++ v1.5’ and ‘Ini++ v1.6’ in the dialog, as it intelligently renames. Therefore any object calling itself ‘Ini++ v1.6’ is just an illusion. (Indeed, the title of the object was renamed after it was noticed this happened to avoid this confusion)

But perhaps you are seeing this anyway, despite not being one of the people who renamed ‘Ini++15.mfx’ to ‘Ini++.mfx’? Unfortunately, this is common. The first installer for the first release of Ini++ v1.5 actually installed the file as ‘Ini++.mfx’, which was obviously complicated the situation. (I didn’t make this installer. Later installers install it correctly.) I believe that the one of the extension updaters for MMF will also distribute Ini++ v1.5 with the filename ‘Ini++.mfx’. Combined, this means that nearly everybody will have this problem.

Perhaps I will solve this in future by having the next installer install the original version of Ini++ as well. Or perhaps by making sure it is uninstalled (as you shouldn’t really be using it anymore anyway – it exists only for compatibility reasons now).

So which version is the latest version? Well, it is quite possible they are both the same version. Make sure you are using the version with the file name ‘Ini++15.mfx’ (you can tell this by selecting the object and clicking the ‘About’ tab in the properties viewer). Ensure this is up to date by installing the latest release. If you don’t use ‘Ini++.mfx’, perhaps you should delete it.

Chart Object Released

So, at last, I’ve released the Chart Object, along with the latest version of Ini++ v1.5. I have written many posts about the progress of the Chart Object, so it is great to finally get it released. I’m sure there will be an initial set of bugs, but hopefully there won’t be anything too major.

The Ini++ v1.5 object has a large number of bug fixes from the original release, and works much better. It is worth noting that the compression algorithm is different that before, so if you use compression it cannot open old Ini files.

The latest bug fix in Ini++ v1.5 is to do with the loading of subgroups, which didn’t work very well previously. Essentially, this is a feature which changes the loading and saving routines to take tabs into account. Groups which are indenting are considered ‘subgroups’. So for instance,

a = 1
	a = 2

has the group ‘Group’ and which has the subgroup ‘Subgroup’. The object does not support subgroups in memory, so it is faked by renaming groups to their path. It is hence loading in memory as:

a = 1
a = 2

This feature was always present, but it was previously fairly buggy.

Ini++ bug fixes

I haven’t forgotten about Ini++ and the Chart Object. In fact, some bugs in the former were delaying the release of the latter. I want them to be released at the same time in order to stop the ‘version hell’ that is the current state of Ini++ (i.e. too many versions floating around, some with bugs). It’s a shame really, because I want the Chart object out of the door.

So mid-September I was told about some bugs. By January I had time to work on them (as I was working on the Chart object before hand, getting ready for what I thought was the release) and had managed to reproduce the bugs, with Pixelthief’s invaluable help. Unfortunately, with only bits of weekends to work on them, as well as problems to do with which computers I have debuggers on, it took ages. I program at work a lot, so I rarely feel like going home and programming as it is. Debugging, definitely not. Still, I carried on and last night I think I finally cracked it!

I fixed quite a lot of bugs on the way. Most of them are small and probably had no effect, but certainly some of them did as it seems to work now. I am so glad to get it out of the way! If, indeed, I have.

Hopefully I can release it through Clickteam fairly soon. It’s late enough already!

One thing: The latest version’s compression is incompatible with the old versions compression. It will not open any compressed files saved in the new version. I hope this is OK with everybody. I switched to zlib for the compression, whilst before I used a library which appears to have had some bugs in it (and was generally unsafe on corrupt files). The penalty for this is a much bigger file size. (About 60kB bigger for the Runtime version.) It’s still all tiny by today’s standards though.

Stay tuned!

%d bloggers like this: