Read array from .ini file

[F._Schubert]

I actually had to go coding to test the exact behavior. Yes, changing the default value of the type def, doesn't propagate to the instances of the type-def (neither FP nor BD). Same for strict TD's. This is a reasonable behavior, as there is no flag that tells if you did manually set the default value, hence an automatic update could be a bad idea.

However the specific situation where you add a parameter and immediately set a default value (to the TypeDef in the Control Editor), the instances get this value propagated (Controls and BD constants).

Felix

[Jeff.F]

Brad,

     What am I doing wrong?  My code look similar to yours.  I'm using the JKI "Write INI Cluster__ogtk.vi" and  "Read INI Cluster__ogkt.vi" and I can't read back what I wrote.  First I "Set" and then "Get".  When the "Get" state pushes to the "Variant to Data" I get an error 91 (variant doesn't match type input).  Is my cluster too comples?  Noticing that the type variant going in doesn't match the variant data returning from the JKI routing.  It's missing section names.  Can I do any complexity cluster or must it be formatted in a specific manner?

I saved the hierarchy in this zip so you can see the very JKI libs I'm using.

Thanks in advance,

J. Francis

[billko]

---

@Jeff.F wrote:

Brad,

     What am I doing wrong?  My code look similar to yours.  I'm using the JKI "Write INI Cluster__ogtk.vi" and  "Read INI Cluster__ogkt.vi" and I can't read back what I wrote.  First I "Set" and then "Get".  When the "Get" state pushes to the "Variant to Data" I get an error 91 (variant doesn't match type input).  Is my cluster too comples?  Noticing that the type variant going in doesn't match the variant data returning from the JKI routing.  It's missing section names.  Can I do any complexity cluster or must it be formatted in a specific manner?

I saved the hierarchy in this zip so you can see the very JKI libs I'm using.

Thanks in advance,

J. Francis

---

FYI, hardly anyone looks at new posts on a thread that has been marked as "solved" and is about two years old.  It's best to start a brand-new topic.