_c_

You are missing nothing. Orso

Yes. Absolutely right. I have some 300 hundreds wood profiles divided into DIN. But since each DIN costs a fortune I am quite unprecise as to the whole of it. I only have bits and pieces of the required DINs, only stuff that I could find online. Alone getting hold of the DINs for doing this would cost about 1500$ if not more (I actually already began this ages ago, then gave up). Metal profiles are a horror as to the ruling. It all depends on the thermical insulation. The rules for it are dependent on the National Energy Law, which changes like crazy. No it is not possible. But at least a simple PIO loading a sym for the frame section, that could be done. And then load the sections publiced online or buy the sections from somewhere else. Orso

Lets go for the "Bakin' tin PIO". Resizable to any Baking Tin DIN dimension (the DIN for baking tins, god, how was that?....) LOL!

It is not that we want to keep the costs up. We must do it. If the client cannot pay, that's only too bad for us. We must do it for free. The risk of having to pay for some error is much more expensive than our own time. Even if we only would do permits drawings, we are responsible for what is built. Even if it is built by someone else. The whole detailing goes according to the DIN rules. The DIN rules are a huge beast. They cover everything and are a hell to master in depth. The german client is very different by the american client. He is expecting the architect to know everything. At any point he can claim that we didn't explain something properly or did something wrong and can refuse to pay us. And has a right to. A pio Door or Win taking frames from the (boundless) DIN library would be a very useful thing indeed. I solve this with symbols, but it is too time consuming to manage this on many files. Please mind that an average project here in Berlin is to renovate some house with 3000 sq m/9800 sq feets. As an average this house would have some 50 flats. If some mistakes pops up, there are rules for decreasing the rent that is paid for flat. We can be made responsible for this loss of income. And it happens all the time. We currently have a process going on involving lawyers, consultants and whatever, about a baking tin, one of these things which are inside a stove, already when you buy it. The tenant claims that it wasn't there when he moved in. We claim it was, when we let 43 ovens be installed in the whole house. But we didn't put this in the protocol listing everything in that newly renovated flat. We are probably losing the process! LOL! Next time I'll draw the backing tin! That would have made us win the process. We have another process going on about a tenant who claims that his hot water consume is very high. The firm who made the piping died in the German recession, so we are now responsible for the piping, because we planned it. We are requested to pay for his hot water consume in the last 8 years. The whole consume! We are now trying to lower down the price to the eventual extra consume due to our "mistake" (we couldn't change a part of the piping because another tenant refused to, so it remained 50 years old). Is it also like that in USA or Finland? I doubt it. Orso

Save this as a command (for example as "Toggle background") and load it into your document contest menu. You'll have it always available: SetPref(16, NOT GetPref(16)); Orso

Thank you, nice to know! Orso

I never scripted textures myself, but it looks like you have to loop down all textures in a doc and compare the longint returned. I'd use BuildResourceList with folderIndex 0 to get this done. Orso P.S. we really crossed mail: how did you get that done?

Just for the records: on Win you cannot add more than a certain amount of choices to PIOs popup parameters. They get lost. Tomorrow, under Windows, I'll try to figure if it is a 256 chars issue. This doesn't occur under Mac. Mac PIOs whose parameter list is opened ONCE (through the plug-in editor) under Win lose forever the extra choices. Mac PIOs untouched, do keep the many choices also under Win, seeming to be unlimited. It would be nice if someone with access to Mac and PC at the same time could check this. Orso

Can you explain again? orso

No! I had to google that! I stopped doing videogames by Lara Croft (how was that called?). I realized I had to choose between a life and that. (the question is: if scripting or being an architect, and, worst, both together, is a life). Please forgive me, I've been truly rude. Orso

someonenamed... you are a lucky person. Raymond gave you a really sweet bit to chew upon! Raymond, you allow me to wikify? Cancel or allow? I would only put the dialog items' IDs on a CONST block at the beginning. I think it is a good habit to start upon. This way it is easier to maintain them later, when your dialog grows (it will, it always does) Someonenamed a link (how did you come up with such a name? is worst than all my identities together), I think the time is ripe for "Spiteful PIO". Some of us would call it "Tamagotschi" plugin, but I am afraid I won't be allowed to name it so on vcor, name traded, or I should ban myself there. Which I think would be a pity. Raymond, come on, let's do it on the weekend. It is the perfect object for demonstration purposes! Or do you have some other plan than laugh your head off for two days on a row? Orso

Basta, Petri. ....and off I go to your personal spam list Sorry, suddenly I realize "basta" in English could be misinterpreted: it means stop, enough, in Italian.

Petri, it is horrible.

Yes, I'm very interested in this too. The problem by this routine development is that you must vectorize a M in order to get its width (supposing you search for a clean em). If you find a trick to avoid this, I'd be very glad to know. I don't think VS allows you to do it. The SDK should be the way. Orso

Thank you Petri, nice to know. Orso

Yes the two flags seem to return the same attribute. Petri, I could think they are points: 1 point = 1/72 in 1 point = 1/1828,8 mm = 1/(25.4*72) mm= 0,000547 mm Since I'm awful in math, and I cannot find at the very moment my own snippet for this, I ask the intervention of real Gandalf for giving you a truly optimized conversion routine. Including UPI. Raymoooondd....... Orso

Why disable aliases? Do you realize that the use of aliases would allow a network sharing of plug-ins? After all they get loaden once and then no more. If one do not reset them continuously. As we do. It could be so: 1 admin (Gandalf) takes care of general setting, developing in the preciousss folder, on a server Clients load an alias to the precioussss folder. Eventual contemporary loading of a Plug-in could be dealt with by a try loop. If the plug-in is busy because is currently readen by another VW launching, wait 5 seconds, then retry. This thread is almost as old as the introduction of plug-ins. How is the future of Network sharing planned? Orso

The thing I'd like the most, would be the possiblitly to use aliases (links in the other world). Last time I tried it didn't work. precioussss... alias to a whatever place of our own choice. Orso

Yes you can. Pref flag real 681 and 682. I didn't try to set them, give it a try and tell me if it works. And how it works. Orso

Give a look to the thread 'Menu command parameter record ', at this very moment is below your one, it answers all your current questions and hopefully every future one. Cut that into pieces and you can work with records. I'd suggest a little experience with 'normal' records first, if you still do not feel comfortable with that. It will help you a lot. Orso

It might just be a matter of time, but it would be great if support to class overrides could be added to the VS routines. And, if I might add it, that it be not 'Architect Only' Thank you Orso

As to overwriting the parm field, probably you pick the wrong obj handle or you make a mistake in the field name. A mistake in the field name induces a silent failing. Lets say you have a PI (PlugIn) of type object called 'aPlugIn' Lets say this PIO (=record attached to a script) has a field whose universal name is "__Bla Bla", whose type is number: And I mean you typed exactly "__Bla Bla" in the Plug-In editor (under the universal name), mind the space between "bla" If you are INSIDE the PIO script first you get a handle to itself (the script) through: IF GetCustomObjectInfo(gObjN, gObjH, gObjRecH, gwallH) THEN BEGIN gObjRecN := GetName(gObjRecH); { now get hold of the universal name } { it is what is displayed first in the Plug-in editor } { supposing it is called '__Bla Bla', because you wish it to be invisible in the OIP:} SetRField(gObjH, gObjRecN, '__Bla Bla', concat(121468797)); { please note that I convert to string the number } END; If the PI would be a command it doesn't matter if you are inside or outside the script attached to the record, but from inside you can use GetPluginInfo, which also returns the name. Otherwise you can use getObject('aPlugIn'); { obviously it is only a record definition} Since commands do not draw a parametrical object you will always have ONLY ONE such record named 'aPlugIn': at the document level (record definition). As every other name it is unique in the name list, then can be securely accessed by the routine above. Call it by name when it is the record definition what you want to access or it is such -like a command- that it can only have a record definition and nothing more. Please compare this two functions: GetCustomObjectInfo(VAR_objectName_STRING, VAR_objectH_HANDLE, VAR_recordH_HANDLE, VAR_wallHand_HANDLE); { for Plug-in Objects } GetPluginInfo(VAR_pluginToolName_STRING, VAR_recordH_HANDLE); { for Plug-in tools, commands } You'll notice that while GetLocalizedPluginName had a parameter ''VAR_objectH_HANDLE'', this is missing in GetPluginInfo. That's logical, a command doesn't have an object-instance, only an document instance (record definition): you'll have only one record, one name. In the name list reigns the usual name unicity rule. If you wanted to reset the DEFAULTS for you PIO (script object) you would then search for the record definition in the name list. myRecN := 'aPlugIn'; myRecH := getObject(myRecN); { call it by name! } SetRField(myRecH, myRecN, '__Bla Bla', concat(121468797)); { overwrites defaults } NOTE: with the same procedure you access also any other "normal" record definition. The record attached to a script has just a little more names, but it is the same. There is a lot to say about records, but I hope this helps you ahead. To my knowledge there is no way to read or rewrite the application level of a record (what you set in the Plug-In editor). Orso P.S. like any record definition, you must launch the command at least once in the open doc in order to add it's record name to the names list, that's logical. If you never runned it and try getObject('name') you just get NIL, if nothing else is called 'name', or you get a whatever object called 'name' should you have one.

SetPref(407, NOT GetPref(407)); This toggles it.

You're welcome. It is a bit naive. But still quite helpful. Mind also that I posted a new Language module, you'll find a link in the thread you started about TextWrangler. BTW, why don't you come back to the vlist? This here is really not quite what you need as a forum, with all respect. Did you ban yourself there? Orso

Hi all, here you find the latest Language Module covering VW 12.5. Language Module 12v5 I'll post to Patrick as well. Enjoy Orso