Jump to content

New ODM preference settings

Recommended Posts

I was playing around with the settings for the new On Demand Menu and wanted to see how it worked.


I'm assuming that PrefReal(6902) returns time in very very small units?


What really has me puzzled is Section ODM Parameters, 6906.  There must be a misprint in the appendix.  Preference Data Type 4 is listed after two different preferences and has no function values.


But what really confuses me is that GetPrefInt(6906) returns a different integer value every time the script is run.  Even if the preferences haven't been changed.


Anybody see what's going on here?


Procedure GetODM;

		CR = CHR(13);


				'Use ODM:                           ',GetPref(6900),CR,
				'Show ODM After Mouse Idle:         ',GetPref(6901),CR,
				'ODM Mouse Idle Timer:              ',GetPrefReal(6902),CR,
				'Show ODM with Spacebar:            ',GetPref(6903),CR,
				'Show ODM with Middle Mouse Button: ',GetPref(6940),CR,
				'Initialize ODM Layout:             ',GetPrefInt(6905),CR,
				'Section ODM Parameters:            ',GetPrefInt(6906),CR,
				'Show ODM Search Filters:           ',GetPref(7000),CR,
				'Show ODM Command Context:          ',GetPref(7001)





Share this post

Link to post

No Idea what is going on with 6906 but it definitely seems like a bug.


6902 should be GetPrefInt instead of GetPrefReal and return the value in Seconds before the ODM automatically displays.

Share this post

Link to post

You're right.  6902 must be a misprint in the appendix.  GetPrefInt works.


At first I assumed that 6906 it was like text styles.  But there's no pattern.  Then I tried to see if the mouse position was involved.  But if you run the create text twice in the same script it still returns nonsense values.



Share this post

Link to post

The 69XX prefs have not been added to the Appendix on the Developer site yet, so it is hard to tell what the formatting for the 6906 result was supposed to be.


No matter what, I don't think it should change. 


File a bug.

Share this post

Link to post

Be careful with these. I tried GetPrefString(6906) and it froze VW.


The description does not make sense to only be a single pref. 


If there are four quadrants and each quadrant can have a different setting then you need at least 4 prefs. I actually think you probably need 8 or 12 to define everything that needs to be defined.



Share this post

Link to post

I didn't even think of trying a string.  I tried GetPrefReal and it just returned a (nonsense?) real number.


I think you're right.  Either the documentation is wrong or it's a bug.  Could be both 🙂 



Share this post

Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114


© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

  • Create New...