Forum Replies Created
-
Posts
-
A few questions just for my understanding if I may.
1.) So there is no need to DEFINE the fill if you already have the gradient fill as an attribute?
Just SET FILL “Linear Gradient Fill”.After all you are not really defining a pattern for the fill.
Every gradient fill you define is exactly the same as the others, just with a different name (and attribute number).
It is all about using the correct options in the POLY2_B[3] command and setting the required pen colours.2.) Why can we not see the gradient and radial fills when a fill parameter is created in the parameter list?
But we can ‘SET FILL’ using those attributes by name in the script.
It would be nice to be able to choose solid, vectorial, symbolic, image and gradient fills from a parameter.3.)Is there a tricky way to set up graphical hotspots to adjust the settings?
I can create hotspots to move the fill origin.unID=1 !Stretchy x HOTSPOT2 0, OriginY, unID, OriginX, 1+128 : unID=unID+1 !base HOTSPOT2 -1, OriginY, unID, OriginX, 3 : unID=unID+1 !reference HOTSPOT2 OriginX, OriginY, unID, OriginX, 2 : unID=unID+1 !moveable !Stretchy y HOTSPOT2 OriginX, 0, unID, OriginY, 1+128 : unID=unID+1 !base HOTSPOT2 OriginX, -1, unID, OriginY, 3 : unID=unID+1 !reference HOTSPOT2 OriginX, OriginY, unID, OriginY, 2 : unID=unID+1 !moveableAnd I can add a hotspot to rotate the fill.
!angle stretchy hotspot HOTSPOT2 OriginX,OriginY,unID,patternAngle,6 : unID=unID+1 !centre HOTSPOT2 OriginX+(patternSize),OriginY,unID,patternAngle,4+128 : unID=unID+1 !base HOTSPOT2 OriginX+COS(patternAngle-symb_rotangle)*(patternSize),OriginY+SIN(patternAngle-symb_rotangle)*(patternSize),unID,patternAngle,5 : unID=unID+1 !stretchy hotspotBut I can not make that rotational hotspot also stretch the pattern length.
If I comment out the above rotation hotspot and add this, I can stretch the pattern length.ADD2 OriginX, OriginY ROT2 patternAngle !Stretchy gradientlength HOTSPOT2 0, 0, unID, patternSize, 1+128 : unID=unID+1 !base HOTSPOT2 0-1, 0, unID, patternSize, 3 : unID=unID+1 !reference HOTSPOT2 0+patternSize, 0, unID, patternSize, 2 : unID=unID+1 !moveable DEL 1 DEL 1I guess what I am asking here, is there a way to combine the rotation hotspot with the pattern length?
So we can have a stretchy rotation.
Or will they have to be two separate hotspots?Barry.
Versions 6.5 to 22
Dell XPS- i7-6700 @ 3.4Ghz, 16GB ram, GeForce GTX 960 (2GB), Windows 10
Dell Precision M6800 - i7 4700MQ @ 2.40GHz, 16GB RAM, AMD FirePro M6100 (2GB), Windows 7 64bitIs it a case of aligning the material with the COOR command after the REVOLVE?
Barry.
Versions 6.5 to 22
Dell XPS- i7-6700 @ 3.4Ghz, 16GB ram, GeForce GTX 960 (2GB), Windows 10
Dell Precision M6800 - i7 4700MQ @ 2.40GHz, 16GB RAM, AMD FirePro M6100 (2GB), Windows 7 64bitIf you don’t have a separate parameter for the height of the lamp itself, then you won’t be able to schedule it.
Barry.
Versions 6.5 to 22
Dell XPS- i7-6700 @ 3.4Ghz, 16GB ram, GeForce GTX 960 (2GB), Windows 10
Dell Precision M6800 - i7 4700MQ @ 2.40GHz, 16GB RAM, AMD FirePro M6100 (2GB), Windows 7 64bitIt’s all OK.
I have it now.UI_INFIELD{2} length[1], 70,20,65,15
UI_INFIELD{2} length[2], 70,40,65,15{2} and no quotes did the trick.
I am sure I had tried that already but obviously not.
I was sure it could be done.Everyone can relax now – panic over!
Barry.
Versions 6.5 to 22
Dell XPS- i7-6700 @ 3.4Ghz, 16GB ram, GeForce GTX 960 (2GB), Windows 10
Dell Precision M6800 - i7 4700MQ @ 2.40GHz, 16GB RAM, AMD FirePro M6100 (2GB), Windows 7 64bitFor objects you just copy and paste what ever image you want into the ‘Preview Picture’ window when you open and edit the object.
Barry.
Versions 6.5 to 22
Dell XPS- i7-6700 @ 3.4Ghz, 16GB ram, GeForce GTX 960 (2GB), Windows 10
Dell Precision M6800 - i7 4700MQ @ 2.40GHz, 16GB RAM, AMD FirePro M6100 (2GB), Windows 7 64bitIf you are saving elements as GDL objects, you will have no control over how the script is generated.
You just have to try to understand it and edit it.If you want complete control, then you have to create the scripts yourself.
Create the elements (prisms, etc.), move and rotate them, create for/next loops, gosub routines, add hotspots etc.As to how to create a complex model in GDL, that would be almost impossible to say.
You will just have to make a start and ask questions as you get stuck.To script something like that crane, you would want to have a pretty decent knowledge of GDL, especially if you want to make it parametric (stretchy and moveable).
It is not something I would want to attempt.Barry.
Versions 6.5 to 22
Dell XPS- i7-6700 @ 3.4Ghz, 16GB ram, GeForce GTX 960 (2GB), Windows 10
Dell Precision M6800 - i7 4700MQ @ 2.40GHz, 16GB RAM, AMD FirePro M6100 (2GB), Windows 7 64bitIn my experience, SYMB_POS_X & SYMB_POS_Y always measure from the ‘Project’ origin regardless of where the ‘User’ origin is.
Are you sure you are looking at the ‘Project’ origin?Barry.
Versions 6.5 to 22
Dell XPS- i7-6700 @ 3.4Ghz, 16GB ram, GeForce GTX 960 (2GB), Windows 10
Dell Precision M6800 - i7 4700MQ @ 2.40GHz, 16GB RAM, AMD FirePro M6100 (2GB), Windows 7 64bitA single HOTSPOT2 command will place a black hotspot that can be used to select or drag the entire object.
I won’t drag just a portion of the object.To stretch just a portion you must use ‘Graphical’ hotspots.
These are a series of commands that produce a purple (may depend on you Archicad settings) diamond shaped hotspot that can be dragged in plan (also can be used in 3D).
You then use an ‘ADD2 x,y’ command before the part of the script you want to drag and a ‘DEL 1’ after it.
This way you can control just a portion of your object.The hotspots will be something like this.
!Stretchy x HOTSPOT2 0, off_ver, 1, off_hor, 1+128 !base HOTSPOT2 -1, off_ver, 2, off_hor, 3 !reference HOTSPOT2 off_hor, off_ver, 3, off_hor, 2 !moveable !Stretchy y HOTSPOT2 off_hor, 0, 4, off_ver, 1+128 !base HOTSPOT2 off_hor, -1, 5, off_ver, 3 !reference HOTSPOT2 off_hor, off_ver, 6, off_ver, 2 !moveable ADD2 off_hor, off_ver .... object script.... DELL 1This create a single hotspot that drags both the horizontal (x) and vertical (y) position at the same time.
You will find more info on Graphical hotspots in the GDL reference manual.
Barry.
Versions 6.5 to 22
Dell XPS- i7-6700 @ 3.4Ghz, 16GB ram, GeForce GTX 960 (2GB), Windows 10
Dell Precision M6800 - i7 4700MQ @ 2.40GHz, 16GB RAM, AMD FirePro M6100 (2GB), Windows 7 64bitThat is just a simple hotspot.
It is not a graphical (adjustable) hotspot.You need to add the graphical hotspots and then an ADD2 x,y to transform your marker position to match the hotspot values.
Barry.
Versions 6.5 to 22
Dell XPS- i7-6700 @ 3.4Ghz, 16GB ram, GeForce GTX 960 (2GB), Windows 10
Dell Precision M6800 - i7 4700MQ @ 2.40GHz, 16GB RAM, AMD FirePro M6100 (2GB), Windows 7 64bitAccording to the GDL reference guide …
• Attribute definition in library parts. The materials and textures defined this way can be used in the script and its second generation scripts.
I assume by second generation scripts they mean CALLed macros.
I think the problem is that if you are just looking at the macro and you are using the defined material name, then it will make no sense as that material will not exist in the macro itself.
I guess it would only work when looking at the original (CALLing) object, where you can see the CALLed macro being used.
I can’t say I have defined materials in an object – but I have done it in a MASTR_GDL script which makes it available to all objects and macros.I also assume the material would have to be defined in the same script that the CALL is made from (i.e. the 3D script).
Barry.
Versions 6.5 to 22
Dell XPS- i7-6700 @ 3.4Ghz, 16GB ram, GeForce GTX 960 (2GB), Windows 10
Dell Precision M6800 - i7 4700MQ @ 2.40GHz, 16GB RAM, AMD FirePro M6100 (2GB), Windows 7 64bitIn the Interface script, turn off the ‘Hierarchical pages’ button at the top.
You can probably also turn off the ‘Set as Default’ button as well.Also in the parameter script, find and comment the line for “HIDEPARAMETER ALL”
Barry.
Versions 6.5 to 22
Dell XPS- i7-6700 @ 3.4Ghz, 16GB ram, GeForce GTX 960 (2GB), Windows 10
Dell Precision M6800 - i7 4700MQ @ 2.40GHz, 16GB RAM, AMD FirePro M6100 (2GB), Windows 7 64bitYou can’t set parameter values in the 3D script.
This can only be done in the parameter and master scripts.You can change a parameter value in the 3D script, but it will only be available from that point in the 3D script only.
It can not be used in any of the other scripts.Barry.
Versions 6.5 to 22
Dell XPS- i7-6700 @ 3.4Ghz, 16GB ram, GeForce GTX 960 (2GB), Windows 10
Dell Precision M6800 - i7 4700MQ @ 2.40GHz, 16GB RAM, AMD FirePro M6100 (2GB), Windows 7 64bit-6.30182e-17 is effectively zero.
Archicad has always had this error (someone else will have to explain why – floating decimals or something?).-6.30182e-17 = -0.000000000000000630182
I will often just change it to zero in a script just to make it easier to read.
Barry.
Versions 6.5 to 22
Dell XPS- i7-6700 @ 3.4Ghz, 16GB ram, GeForce GTX 960 (2GB), Windows 10
Dell Precision M6800 - i7 4700MQ @ 2.40GHz, 16GB RAM, AMD FirePro M6100 (2GB), Windows 7 64bitThe only ones you can’t edit are the ‘Built-in’ objects.
Barry.
Versions 6.5 to 22
Dell XPS- i7-6700 @ 3.4Ghz, 16GB ram, GeForce GTX 960 (2GB), Windows 10
Dell Precision M6800 - i7 4700MQ @ 2.40GHz, 16GB RAM, AMD FirePro M6100 (2GB), Windows 7 64bitIt seems there are 22 label parameters in the 21 guide.
Only 5 in the 22 guide.
Anything to do with the fact that “LABEL_CUSTOM_ARROW” is considered deprecated since ARCHICAD 22?Barry.
Versions 6.5 to 22
Dell XPS- i7-6700 @ 3.4Ghz, 16GB ram, GeForce GTX 960 (2GB), Windows 10
Dell Precision M6800 - i7 4700MQ @ 2.40GHz, 16GB RAM, AMD FirePro M6100 (2GB), Windows 7 64bit
