Jump to content

orso b. schmid

  • Posts

  • Joined

  • Last visited


32 Great


Personal Information

  • Occupation
  • Homepage
  • Hobbies
  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. You should reduce your default content, that will help. Make 2 or more libraries, load the office libraries only where needed. As I stated elsewhere, our library is around 11 GB. Launching VW is a bit delayed, yes, but actually fast (there is a huge gap between Mac and Win, BTW). It's around 20 seconds. The content of the library is also something we didn't yet touch here. What goes where.
  2. It is simply a command plug-in, nothing special.
  3. Hello Gaspar, a lot changed, but not so that the WG disappears. Perhaps you forgot to convert it from a previous version?
  4. I have "managers" for dealing with the sheer immensity of such libraries. Below an example of my CAD-Manager Symbols. But I have similar things for most relevant resources. It is infinitely faster to write a new command and add it in one of the managers, than do anything by hand.
  5. Hello Christiaan, the office library should be split from default content, please note the 'forbidden' icon. I consider it a glitch of VW that there is no clear distinction. Also, we have office libraries for architecture, for rendering and for exposition projects, they are different. We can't have all in one file (all libraries together are 11.5 GB), but we have a file called Basic Set where we keep a subset of the most used resources. This is also more or less the only file used by those making competitions. They have specific needs which are substantially different than those doing construction drawings. For them, on the other hand, there is a huge architecture of data-related resources with ancillary items from worksheets to data tags.
  6. My routines library which was available as open code haven't been saved, so don't ask, please...
  7. Hello, I am very sorry that Vectorlab went down, Gerard maintained it really a number of years. The List Browser article is saved here as web archive, for those interested: The List Browser Article is now hosted on Dev under my personal page as _c_. https://developer.vectorworks.net/index.php/User:CBM-c- It would be so good if @Vladislav Stanev could give us -finally!- a true documentation. In the mean time, just use that.
  8. The vertical frames in the wall displayed below need to have equal spacing. There is no Vectorscript access to the frames. I searched rather deep. Does anyone know how to access those frames?
  9. I am tired of waiting for a fix that will never come. I asked for this functionality when the tool was issued, in 2014. Asked it again and again. It won't come. I need a way to distribute equally Curtain Wall vertical frames. I'd like to write a Distribute Vertical Frames command to be applied on a whole wall instance. Usually one would select them *one * by * one* then use the contextual menu "Distribute Frames". The selection of the vertical frames is a very cumbersome process that has to be repeated countless times during the planning phase. I cannot have a style for each wall length, so setting up widths in a wall style definition is not helpful. Does anyone have explored this already?
  10. Hello, labels are just as old as MiniCad. You won't see any change there. Raymond Mullin will able to point you to very good literature about PASCAL. If he's not following this thread already, I'll send him a note to come here and help you. If GOTOs don't work as expected, you are making some mistake in their scope. And then they work unpredictably. I seem to understand that you are using GOTO globally in your whole script. That will not work. As a principle GOTO statements are only good within a singular routine. No more. You won't be able to solve this problem until you switch to a different script structure. More subroutines, IF and CASE conditions.
  11. No, sorry Arshan, that can't go well. What happens when you display in Viewport with another layer scale? Nothing. Wrong display since the object won't regen. And anyway you would need an event enabled plug-in with regen on layer scale change also for a correct display on design layer. Otherwise there will be no conversion. kObjXPropHasLayerScaleDeps = 2; { Object wants to be reset with when its layer scale changes. // Boolean Property } Did you actually try to use the symbol flag on your Pio? It might work. /SDKLib/Include/Kernel/MiniCadCallBacks.h const short ovSymDefPageBased = 130; // Boolean - whether the symbol will have a constant page size, meaning it will have the same size
  12. Please read well what I wrote: I said that ValidNumStr supports units. Not Str2Num. The two are different. Going back to the sub, you'll want to use a sub that returns the number right away instead of a boolean and that's why you define that sub.
  13. If you have a parameter of type dimension, that takes care of the units and you need no conversion. Whenever you use values that are subject to units, you should really take exclusively parameters of type dimension. You don't need to use Str2Num, ValidNumStr -also in its standard version- supports units and it's a more modern call. Making it a sub has the advantage of having it return a number instead of a boolean value. It is an old standard subroutine from my collection here: http://www.vectorlab.info/index.php?title=Util-Valid_num_or_zero You don't have to redefine the standard routine, you can define your one as you please and call it something else. I think it is better. You can look also at this one, for example: http://www.vectorlab.info/index.php?title=Util-Valid_num_enhanced I don't write the documentation, I just document VectorScript quirks on dev. Before that I did it on Vectorlab. Lucky you that you find easy to follow GOTOs, I don't! Anyway, as it is stated in the current documentation, LABELS are unpredictable if used outside their scope. Keep that in mind and all is well. Ciao, Orso
  14. Hello Sean, I have no idea why on Dev there is written to actually override Str2Num. You don't have to. I don't know who wrote that. You CAN override it, but don't have to. I will add now a warning note on dev. Please don't override stuff if you don't feel comfortable with scripting. BTW, GOTO are more difficult to handle than, say, CASE or IF conditions. This sounds quite surreal to me. I open now the guide which I found here. It states: GOTO statements have several cautions which must be observed whenever using them: GOTO statements can only transfer execution within the same procedure, function, or main body of a script. They cannot be used to jump between procedures or between scripts. The destination of a GOTO statement must always be the beginning of a statement. Jumping to statements that are contained within the structure of other statements can have undefined effects; the VectorScript compiler will not recognize this action as an error. I used them myself only a handful of times. I think you'll do yourself a favour dropping them and eventually coming back to it when you feel more comfortable with VS. Ciao, Orso
  15. Laurum, do you know our Developer wiki? It's great: http://developer.vectorworks.net/index.php/VS:SaveActiveDocument
  • Create New...