persistent values in Modules

eddymouse

Hi, How can I memory persistent variables in Modules? I need to write in a file? How the files system work? Where can I find more information about?
Thank you
Alex

Onkelz

Hi

Sadly, persistent variables do not work in Modules!

ericmedley

eddymouse wrote: »

Hi, How can I memory persistent variables in Modules? I need to write in a file? How the files system work? Where can I find more information about?
Thank you
Alex

You could write them to an XML file on the disk.

mpullin

ericmedley wrote: »

You could write them to an XML file on the disk.

I think the original poster knows this and is asking for details on how to perform file-writing skills within Netlinx. Since I've never done this I can't help any, sorry.

eddymouse

mpullin wrote: »

I think the original poster knows this and is asking for details on how to perform file-writing skills within Netlinx. Since I've never done this I can't help any, sorry.

Exactly! Now I'm trying to follow the manual. But It's not so clear....
Thank you!

Sensiva

While waiting....

Do as I am doing... while waiting for someone to provide detailed info, read NetLinx Keywords help ROUGHLY and THROUGHLY.

click Help, NetLinx Keywords Help, in Index tab type file, and you will find FILE_COPY, FILE_CLOSE, FILE_OPEN, ....etc.

I think after few hours of tryouts you will find out what's the deal with files operations in Netlinx, and then start your own "HOWTO: Files in Netlinx" thread, and I guess it will be a great contribution from you...

AMXJeff

eddymouse wrote: »

Hi, How can I memory persistent variables in Modules? I need to write in a file? How the files system work? Where can I find more information about?
Thank you
Alex

You can actually pass in a persistent variable to a module. The variable needs to be declared outside the module.

DEFINE_VARIABLE
PERSISTENT CHAR cWhatEver[100];

DEFINE_START

DEFINE_MODULE 'Whatever blah blah' modBlah(vdvStuff, dvStuff, cWhatEver);

DHawthorne

I'll usually do what AMXJeff suggests and declare it outside the module, then pass it as a parameter. If it's something more complex, like a structure, or an internal database, I'll write it to a file.