Barry Kelly

Forum Replies Created

Viewing 15 posts - 16 through 30 (of 139 total)
  • Author
    Posts
  • in reply to: Forward Migration #4722

    Barry Kelly
    Participant

    Automigration is a special type for migration: it simply does an ID change, without running migration scripts. It is useful to eliminate migrations from new elements, and create step-by-step migration logic through many versions.

    So to clarify, if we just want to migrate objects with no parameter changes, we just add the old object GUID to the list and turn on AutoMigration.
    It will ignore anything in the migration script.

    Here is the link to the actual post Peter has quoted from Greg.
    I had forgotten I was even a part of that conversation. (insert embarrassed face emoji here).

    https://archicad-talk.graphisoft.com/viewtopic.php?f=6&t=58220&p=274105&hilit=automigration#p274105

    Thanks Peter and Greg.

    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

  • in reply to: Forward Migration #4720

    Barry Kelly
    Participant

    It is all a bit of a mystery.
    In the GDL manual STORED_PAR_VALUE and DELETED_PAR_VALUE seem to do exactly the same thing.
    I figured I should use DELETED_PAR_VALUE if the parameter no longer exists in the new object, but I am guessing it doesn’t matter.

    I can find no reference as to what AutoMigration does, either here in the GDL Center or the Help Center.
    Or if it is there it is just hard to find.

    I have always had AutoMigration turned off, so would never noticed it is a problem.

    Also, I find it is easiest to use the ‘Migration’ section to find out the GUID of your new object.
    You need the GUID of any old objects here – just don’t forget to delete the current object GUID once you have found out what it is and pasted to the migration script.
    Otherwise the object will simply not migrate, and there will be no error messages to say why.

    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

  • in reply to: Forward Migration #4718

    Barry Kelly
    Participant

    I use DELETED_PAR_VALUE – that works for me.

    So …

    IF actualGUID = _startID THEN
    	rrr = DELETED_PAR_VALUE ("aSurf", aSurf_val) ! get value from old
    		bSurf = aSurf_val
    		PARAMETERS bSurf = bSurf ! apply to new
    
    	actualGUID = _endID
    ENDIF

    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

  • in reply to: Global for Favorites Mode #4645

    Barry Kelly
    Participant

    That’s what I get for looking at the 21 version of the book.

    I still use the book from version 6.5 – as it was the last physical book printed and I find it much more convenient than opening a PDF.
    Good job most of the basic stuff is still the same.
    I just keep forgetting to look at the new options though.

    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

  • in reply to: Global for Favorites Mode #4636

    Barry Kelly
    Participant

    Yes it is GLOB_PREVIEW_MODE = 3

    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

  • in reply to: Issue with label and surface override #4608

    Barry Kelly
    Participant

    When the override button is pressed it should show the override.
    When the override button is not pressed it should show the BM surface.

    Isn’t that what I said?
    I would like it to show the BM or nothing at all(if that is not possible) if the override is not pressed.

    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

  • in reply to: Issue with label and surface override #4606

    Barry Kelly
    Participant

    I have never really liked the fact that the surface name is greyed out and you can actually see what is the ‘wrong’ surface.
    But I know that it is then using the building material surface – but as David says you can’t see what this is.
    It would be nice if it could show this or maybe not show anything at all until the override button is pressed.

    Some people still don’t even realise that is an override button.

    Yes, complex profiles complicate it even more as it could be the building material used for the fill (not to mention there could be more than one fill on that surface), an overridden edge surface of the fill or the actual override of the entire wall itself.
    Which is why I think it should be blank until the override button is pressed, and then it shows just the override surface.

    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

  • in reply to: Issue with label and surface override #4598

    Barry Kelly
    Participant

    Hi Peter
    If you look at the upper part of the attachment the name “A001:Brickwork Face” appears but this is the override surface not the surface of the Building Material. The building material surface is correctly reported in the label text.

    That is correct.
    The greyed out text is what the surface would be if the override was turned on.
    When the override is not turned on, it doesn’t show the actual building material surface – which maybe it should?
    Is that the problem here?
    The label should always be correct.

    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

  • in reply to: Opening oversize no longer instantly updating #4596

    Barry Kelly
    Participant

    Thanks Péter,
    Drawing the end lines works but you don’t have the same control when the automatic wall hole is used.
    Yes I can check ‘AC_WallContours’ and draw the lines or not.
    But when I have 2 opening butting up next to each other, one with an opening extension because of a connecting column between the windows, and I need the side lines, there is a problem.
    Drawing them manually they are either on or off – on in this case because I need the side lines.
    With the automatic hole there is no joining line even when the side lines are on.

    Yes, I could script and control each side line separately, but I really don’t want to.

    Hoping this fix will find it’s way into an update soon.

    Thanks again.

    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

  • in reply to: Opening oversize no longer instantly updating #4587

    Barry Kelly
    Participant

    Thank you.

    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

  • in reply to: DESCTIVATING A CUTPLANE FROM 2D SCRIPT or similar method #4549

    Barry Kelly
    Participant

    If you can get the correct views with the cutting planes in the PROJECT2 command then in the 2D script you use it twice.

    PROJECT2 - top view with desired cutting planes
    if show_elevation = 1 then
        ADD2 x,y
        PROJECT2 - side view with desired cutting planes
        DEL 1
    endif

    If you need to use an actual CUTPLANE in the 3D script to get the projection you want then use the if/then command to control the CUTPLANE and CUTEND as I mensiomed before (but you won’t need the GLOB_VIEW_TYPE = 2).
    The thing is you will need to turn off the CUTPLANE for one of the passes.
    Again this may not be the best scripting but I would do this.

    show_elevation_orig = show_elevation
    show_elevation = 0   !!!!temporarily turn of show in elevation mode
    PROJECT2 - top view with or without built in cutting planes
    show_elevation = show_elevation_orig   !!!!set elevation mode back to original
    
    if show_elevation = 1 then
        ADD2 x,y
        PROJECT2 - side view with or without built in cutting planes
        DEL 1
    endif

    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

  • in reply to: DESCTIVATING A CUTPLANE FROM 2D SCRIPT or similar method #4533

    Barry Kelly
    Participant

    So I need this, either:
    a) A condition that can deactivates the CUTPLANE in the “3D script” when the user asks for an elevation view on Plan.

    I assume the showing of the elevation in plan view is a parameter option.
    I would then do this.

    if elevation_in_plan = 1 and GLOB_VIEW_TYPE = 2 then				!Plan view
    !!!!do nothing
    else
          CUTPLANE 0, cutplane_height
    endif
    
    ... 3D model script ...
    
    if elevation_in_plan = 1 and GLOB_VIEW_TYPE = 2 then				!Plan view
    !!!!do nothing
    else
          CUTEND
    endif

    I am sure it could be scripted differently.

    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

  • in reply to: Gradient fill #4514

    Barry Kelly
    Participant

    Thanks Peter.
    I don’t think a rotational and moveable hotspot can be linked which is why I was asking.
    I will give your hidden calculations a go – I think that might be the only way.

    Usually with something like this I would have one hotspot for the origin x & y, another for the length and a rotation one at half the length.

    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

  • in reply to: Gradient fill #4512

    Barry Kelly
    Participant

    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	!moveable

    And 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 hotspot
    

    But 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 1

    I 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 64bit

  • in reply to: Access to Minimum Space with GDL #4633

    Barry Kelly
    Participant

    The only way I know of to control this globally for all doors would be to use Model View Options.
    I see with the default Graphisoft library there is an MVO setting to show/hide the minimal space, but not to control the sizes.

    Or select all doors at once and make the changes you need (so long as the doors have been scripted with those options of course and they are not hidden).

    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

Viewing 15 posts - 16 through 30 (of 139 total)