TheSwamp
Code Red => VB(A) => Topic started by: simor on December 30, 2008, 10:03:08 AM
-
Hi,
I'm trying to figure out if there is an easy way to have variables defined on a "per drawing" level. I thought that ThisDrawing will refer to the active drawing (in standalone project - not embedded) and so I will be able to use ThisDrawing.myvar and myvar defined under ThisDrawing as public but apparently once myvar is set under Drawing1.dwg I can see the same value when I'm working on Drawing2.dwg. (It's per project, not per dwg file).
I know I can use dictionaries but I thought that maybe there's some easier way, some keyword I can put next to the variable definition that will set the "per-file-scope".
uhmm am I clear? :oops:
-
Thisdrawing, like you have said, is merely the active drawing.
Perhaps the easiest way to achieve what you want is to come up with some rules that work for your project, if this drawing path comes from here, do this etc.
-
Thanks Bryco. I was thinking of creating some array/table to store my per-dwg-data (new dwg = new record) but it's hard to believe autodesk/microsoft didn't prepare anything like that ... other than the dictionaries hmm. I'll have a closer look at them, maybe they aren't that scary - the implementation I have is really unclear :P
BTW, do you/anyone happen to know if this kind of variable scope is available when using ARX & .NET (C#)?
-
Perhaps you could use the User setvars available as integer useri1, real userr1 or the string version. These are per drawing and may be all you need.
Net doesn't have anything magical for this that I know of.
-
Why not just write a wrapper for dictionaries that provides an easy / simplified interface? User vars are not the way to go imo.
-
I'm not a fan of the user vars either.. so I went the dictionary/xrecord direction and so far it's looking good. Thanks for the tips :)