Ini++ only saving 100 values?

Welcome to our brand new Clickteam Community Hub! We hope you will enjoy using the new features, which we will be further expanding in the coming months.

A few features including Passport are unavailable initially whilst we monitor stability of the new platform, we hope to bring these online very soon. Small issues will crop up following the import from our old system, including some message formatting, translation accuracy and other things.

Thank you for your patience whilst we've worked on this and we look forward to more exciting community developments soon!

Clickteam.
  • Hi everyone! I'm trying to use the ini++ object to save the values in an active object, the active object has over 150 alterable values, but it seems when I save using ini++, it only saves values from 0-99, so I'm wondering is there any way around this limitation, and if not, what are the quickest easiest ways to save an object that holds hundreds of values? Thanks in advance for any help!

  • Thanks for the suggestion, but the thing is, with the Ini++ object you can choose to save all the values in an active at once, so I'm not picking and choosing what values are saved, it just saves values from 0-99 and anything greater than that will not save. Anyway, it's okay, I found a way around it just by saving half the values into another object, and then transferring them back to the original object when needed, kinda messy but it works. :)

  • The reason for INI++ only saving up to 99 values is related to an issue that popped up when the 2.5+ DLC came out. INI++ was created back when objects in Fusion only had 26 values available in them. The extension was programmed to only save 26 values with the action to save everything at once. When 2.5+ came out, this causes INI++ to crash when saving objects that contained the new amount of values and strings.

    Yves released an updated version of INI++ to prevent the crashing. It's a quick fix that increases the maximum number of values the extension can save at once to 99. The code refers to the saved values in a way that apparently explicitly expects the maximum possible number to be double digit. Changing it to be triple digit would require a more detailed examination of the source code. Hopefully someday the extension can be updated to accept the full amount of 2.5+ values.

    Here's a link to what Yves said about it in the original thread. Please login to see this link.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!