Dieter @ DWorks

The drawing label should be part of the viewport with a control point to set it's placement, not an annotation like it is now. And let the drawing label be set through the oip of the viewport, like Vincent is saying. And for people who doesn't want the drawing label, have the option to show it or not.

Create a VW file as a library. Then you can reference these symbols in the files you use for your buildings. If you change the symbols, you can update the reference and those symbols will reflect the changes. You can reference a symbol by having the file of the building as the active drawing, going to your resoursce palette of the library file and right click the symbol you want to reference and choose the correct option. Try to use a relative reference and keep the files together in the same structure. This makes it easy later on when you move the project or making changes to your folder structure, so that you don't have to rereference all the stuff. Actually, never use absolute referencing for this.

Edit the hatch, then check the option to rotate in wall.

This is the reason why you need to decide some sort of folder structure at the beginning and where you will put your .vso .vsm and .vst files, because these will determine the start of where VS will look for the includes. Personally, I did put the plugin files into the main plugin folder and having all .px files in some sort of folder structure. Then all includes can be the same as long as the folder structure stays the same. Your library files can be easily done. Recently, due to the fact of too many plugin files, I now have one folder for each plugin into the main plugin folder. The plugin files are each in their folder, just one folder down from the main plugin folder. The rest stays the same. I only need to add .. before the include path everywhere if I need to include a file that's not part of the actual plugin, like library files. This is also very easy. long story short: decide your structure and then stick with it to easily create the include paths. I really won't recommend using full paths from your hard drive, because when you move your main plugin folder due to restructuring some data folders, or because you copy your library for a new VW version, you'll have to edit all include paths, which can be a lot of work.

do you use associate dimensions? Then I would recomend not using them. They can cause such things when copying stuff. And copying a stair is never a good thing to do!

It is the lonely little bim that each office needs to master first. All other bim types depend on it's workflows and tools.... How can you expect that an office will collaborate through exchanging models if they aren't capable of creating one, because they can't get all '2D' info out of it in a fast and easy way?

That's a serious bug if you ask me....

Check the folder permissions if you can't open any file in that folder. You can also try to create a new folder, move all files to that and try again. There may be another process that uses the files like backup etc?

I don't think hyperlinks to other sheet layers work when exported.

You can snap to the contents because it's a vector based drawing in the pdf. That it's shifted may be some sort of bug.

Always happy to help.

Ok, you are missing the point here. You need to add an include statement in the script of the plugin in the plugin editor. Only then will VW be able to lookup the code that it needs to execute. Then you need the included files, but once encrypted, you don't need them anymore because VW will just insert them before encrypting. Be sure to copy the plugin file first before encrypting because you can't decrypt it. One of the good reasons to work with include files is to work in other text editors than the plugin editor.

Create a second symbol for each of the windows/doors. This symbol will contain the wall opening. Place these symbols in the upper wall. This symbol can also contain some 2D objects, but then you need to have 2 loci on top of each other so that the wall isn't cut in plan by the 2D objects. A 3D loci can also help to find and select the symbol. OR you can reshape the wall, which is more time consuming and harder to redo once the windows/doors change. OR you can just place the objects in both walls and adjust their Z height so they overlap, you will have duplicates, so when using worksheets, keep this in mind. OR change your walls so you don't have to do this. Maybe there are other solutions to what you are trying to achieve? Always go for the simple one.

If you see no extensions on your files, then turn them on. For professional use, this is really needed for several reasons. Are you sure that width and height are defined as parameters in the plugin through the plugin editor? commenting out a line can with {} multiline comment can with {**}

Any more info? Make sure you set your include statements in the correct order and that VS can find them, and that they are .px files.

yes. I only meant that to include a file, you have to state the path to it, relative to the plugin.

yes, changing the extension in it's name is all it takes. When your includes are in the .px format, they will be included once you encrypt them, so the encrypted file doesn't need them anymore. If they are normal tekst files, it will need them, that's why it's better to use .px files. Keep in mind that using includes, the path you have to use is the path from where the real plugin is stored. Also don't forget to end each file with an empty line or else you will get errors and finding this culprit is really hard!

Yes, just make sure your include files are .px files to make sure they get included with the encrypting.

This is interesting: do your clients/collaborators actually pay you to use your drawing as a base for theirs? I would love to be able to charge, after all, why should we do all the work, save everyone else money, and get nothing for it? However I have never come across an architect with the chutzpah to demand payment. What is other people's experience? Well, my clients know my rates before I work for them. If they don't need the actual drawing, then they just pay for pdf files. If they need the actual file because they will work further on it or for other reasons, they will pay more for it. They have the choice. They also can start with pdf files, and when they need the drawings, they can pay the difference. I find this a normal way of working, because when you give the actual drawing, they can use all of your library items in the drawing that you spend a lot of work on. As long as they know this beforehand, there can't be a problem afterwards...

Lol, this is a very curious case indeed. I also had this from time to time and it just crashes VW here. I thought it could close the program etc.. like the tree buttons in the top right of the window, on a windows machine, but I'm not sure. I know don't have this because I save with the shortcut keys and there aren't any menu items in the first menu that I use a lot.

You could also use a plug-in that just holds a symbol in it. I know they can also create a symbol out of it, but it's just a little bit harder... But I do agree with the posts above that we need some feature to let our own library resources only be used by those we choose. VW can check on Donglenumber (last 6 digits.)

Like Pat says, you can do some stuff, but they can Always make a new symbol out of it. My clients simply need to pay more for the VW file because of this. If they only want a pdf file, then it's less. Also, remember to purge your drawing from unused symbols so they can only use the ones you used for their design.

your pio is event enabled, so you choose which parameters are on the oip. It doesn't matter if a parameter is on the oip or not, you can always get it with Pparameter and set it with SetRField.

In your reset object part, you never get the click parameter, so that will be 0 and no case will be taken.

You Always set the click to 1 in the retrieve parameters section. So click will be Always 1!