What about ldata?

[Devin]

Do the ldata functions work now? I know there was some problems early on.

ie: vlax-ldata-put / vlax-ldata-get

TIA,

Devin

 

[R. Robert Bell]

IMHO, it is a dead-end. The data is not available to VBA, so I am concerned that it won't be available to future supported languages either.

 

[Devin]

Do you think it will be supported in lisp and active x later on? Also is there another way to store and retrieve data?

 

[Luis Esquivel]

Robert,

Have you tested with .NET apps yet?

And what will be your recommendation to save data (safely).

 

[Jason Piercey]

Dictionaries/Xrecords

 

[R. Robert Bell]

Since the LData isn't available via ActiveX, it doesn't matter with .NET (those must use ActiveX at this time).

Vanilla Dictionaries/XRecords are the way to go.

--
R. Robert Bell, MCSE
www.AcadX.com

| Robert,
|
| Have you tested with .NET apps yet?
|
| And what will be your recommendation to save data (safely). | | | | | > IMHO, it is a dead-end. The data is not available to VBA, so I am | concerned | > that it won't be available to future supported languages either. | > | > | > -- | > R. Robert Bell, MCSE | > www.AcadX.com | > | > | > | Do the ldata functions work now? I know there was some problems early | on. | > | | > | ie: vlax-ldata-put / vlax-ldata-get | > | | > | TIA, | > | | > | Devin | > | | > | | > | > | |

 

[Tony Tanzillo]

LDATA is just a way to 'encrypt' your data in a
dictionary, using a custom object. In fact, in
some circumstances (opening a file by double-
clicking in explorer) you can see proxy notices
when you open a file with LDATA.

The only thing LDATA offers is that it preserves
the original list structure, which is something
that is useful only to entry level programmers.

The disadvantages is that it is a way to lock
your data up in a way that can potentially
render it completely inaccessible, which is
what happened when R14 drawings were migrated
to AutoCAD 2000.

You can use Dictionaries and XRecords to store
anything you can store in LDATA and can access
it via any API you might choose to use.

In short, stay as far away from LDATA as you
can possibly get.

 

[Devin]

Thanks for the rundown Tony. I thought ldata and dictionaries were the same thing, I'm still living in the stone age a little

Thanks, I think I'll use dictionaries if I can.

Devin

 

[Devin]

Vanilla Dictionaries/XRecords are the way to go.

Thanks Robert I appreciate your knowledge on the issue. I'm glad I asked, I think I'll try using dictionaries for my settings data storage.

Devin

 

[Jason Piercey]

I use them all the time, work real well for drawing dependent data. It helped me to have a set of standard 'toolbox' functions for handling dictionaries/xrecords. I've since converted all of that stuff over to ActiveX and also started using the registry to store some program specific values.

 

[Devin]

That's pretty smart! I'm going to use activeX and devlope some handling functions too.

Thanks,

Devin

 

[tsigwing]

So the command vlax-ldata-put is storing to a dictionary and not to ldata? I think this is correct, but the "ldata" part of the command is misleading.

Troy

 

[R. Robert Bell]

LData is stored in a dictionary. The LData _itself_ is *not* available outside of LISP.

 

[Tony Tanzillo]

So the command vlax-ldata-put is storing to a dictionary and not to ldata? I think this is correct, but the "ldata" part of the command is misleading.

No. LDATA is stored in a custom object, which itself is stored in a dictionary.