davmiller2 Posted October 16, 2001 Share Posted October 16, 2001 This may sound to simplified a suggestion for a very complex problem concerning the speed issue but.... Is there a possibility to in a sense turn the data base function "off". The labels would then only become in theory, just letters. The user would then have the abilty to turn the database function "on" when they needed to make changes that would effect database information. Like I said, it's probably too simplified an answer to a complex problem. Quote Link to comment
kmoore1 Posted October 16, 2001 Share Posted October 16, 2001 quote: Originally posted by davmiller2: This may sound to simplified a suggestion for a very complex problem concerning the speed issue but.... Is there a possibility to in a sense turn the data base function "off". ...<SNIP>.. Like I said, it's probably too simplified an answer to a complex problem. The idea is a good one, but unfortunately this level of event messaging doesn't exist for custom objects in VectorScript. Currently anything you do to the instrument (move, rotate, change a field value, etc) causes the instrument to Re-generate. The lighting device object in SpotLight is just code that is run each time you do something. Basically this object is just a recipe for creating an instrument rather than being an actual instrument. Sort of like the Joy of Cooking has a recipe for a pineapple upside down cake but isn't actually the pineapple upside down cake. To continue the meataphor; If the cake is too heavy you can't just add more flower and fix it. You have to bake a whole new cake with the correct amount of flower and then after 25 minutes at 350 degrees you get to see the results. (I'm sure that many users would agree that this aspect of the metaphor is particularly poignant. ) Similarly with the lighting instrument anytime you change anything, it has to go through the whole "recipe" again to create an instrument. Changing over to a new way of handling user events would take a huge amount of work both in the VectorWorks core and in SpotLight. VectorWorks would have to be re-written to tell the instrument what just happened to it (i.e "Your channel field just changed") and the instrument would have to be re-written to handle these events (i.e. "If my channel field changed then re-draw just my channel label") HTH ------------------ -- Kevin Moore --------------------- Product Manager VectorWorks SpotLight --------------------- Quote Link to comment
.png.682a1dde7889dd17fdb4e18ba0421cf6.png)
Recommended Posts
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.