23 replies to this topic

[crelf]

Regardless of which method you choose to store the data in the app (class, globals, cluster), persisting the data is fairly easy:

My version of the preferences dialog uses the OpenG panel to disk VIs, and they work great. I'll try to post an example tomorrow, if someone reminds me with a PM...

[Aristos Queue]

Is this a good Idea - or are there reasons not to do this?

Making it a symbolic path would encourage you users to link against it. If you thought we were cavalier about changing VIs in vi.lib that aren't in the palettes, that's nothing compared to what we feel free to do to the Resources directory. ;-)

[jgcode]

Making it a symbolic path would encourage you users to link against it. If you thought we were cavalier about changing VIs in vi.lib that aren't in the palettes, that's nothing compared to what we feel free to do to the Resources directory. ;-)

lol

[Christian_L]

I posted a new version of the code on NI Community including a VI package.

Changes in the code:

• Reverted version number from 1.0 to 0.2
• Added VI package distribution
• Moved all dialog subVIs from LV resource folder into package
• Added support to show/hide Help button and specify dialog help file
• Moved API and framework into LV project library
• VIs install to ..\user.lib\ODF
• Added subpalette to User Libraries in Function Palette

http://decibel.ni.co.../docs/DOC-13146