Barry Kelly

Forum Replies Created

Viewing 15 posts - 136 through 150 (of 170 total)
  • Author
    Posts
  • in reply to: Migrating to AC20 #2613
    Barry Kelly
    Participant

    Laura,
    Do you mean that the arrow head moves when you stretch the text hotspot?
    If so that is happening to me using your object in 18, 19 and 20 – they are all working the same.
    I don’t see any problems with GLOB or REQUEST in the master/parameter scripts.
    Those you have used are allowed (although judging from my other posts I am no expert in this field!).

    It seems to me the problem is with the 2D hotspots in that the one for the text position is altering the value for the arrow head.
    I haven’t got time to dig into it in detail though just at the moment but hope this helps.

    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: What is the proper replacement for GLOB_​CONTEXT=1? #2608
    Barry Kelly
    Participant

    I meant to say ‘GLOB_CONTEXT = 1’ not 5…

    But I guess I am desperately after a way to have a parameter not be set while in the library part editor – i.e. the old ‘GLOB_CONTEXT = 1’ which now of course doesn’t work.

    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: What is the proper replacement for GLOB_​CONTEXT=1? #2607
    Barry Kelly
    Participant

    Thanks Gergely.
    I think it is finally sinking in that GLOB_VIEW_TYPE will have a default of ‘2’ which is why the ‘if GLOB_VIEW_TYPE = 2 then …’ set ‘firstRun = 1’ but the ‘if GLOB_VIEW_TYPE = 3 then …’ doesn’t (because it actually equals’2′ not 3).

    I think that is what keeps confusing me – not that the command no longer works but that it has a default value that can make it appear that it is working in some circumstances.

    But I guess I am desperately after a way to have a parameter not be set while in the library part editor – i.e. the old ‘GLOB_CONTEXT = 5’ which now of course doesn’t work.
    So I am looking for anything that will work and am clutching at straws.
    I thought I might be on a winner her but no I wasn’t.

    There is a solution for me and it requires migration of the objects.
    It works fine, just more involved to get it working.

    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

    Barry Kelly
    Participant

    This has just cropped up again in ArchicadTalk … https://archicad-talk.graphisoft.com/viewtopic.php?t=53078

    I was having a bit of a play again and noticed if ‘GLOB_VIEW_TYPE = 2’ is used (in master or parameter script) then whatever script is run after that command will run while in the library part editor.
    For example …
    IF GLOB_VIEW_TYPE = 2 THEN !do only in 2D
    IF firstRun = 0 THEN !parameter that allow to run code only once
    parameters firstRun = 1 !prevents running code again
    ENDIF
    ENDIF

    So if there is a boolean parameter in the parameter list called ‘firstRun’ then it is automatically set to ‘1’ and you can’t manually change it.

    If you alter the script to … IF GLOB_VIEW_TYPE = 3
    or any other value then it is not run and you can manually change the parameter.

    Is this a bug that GLOB_VIEW_TYPE = 2 is ignored while in the library part editor? – seeing as technically it is not a 2D view and this part of the script should be ignored.
    Just as it is ignored if GLOB_VIEW_TYPE = 3 (or any other value) is used.
    Just finding it hard to see any logic here.

    To test this I used this code in the master script.

    IF GLOB_VIEW_TYPE = 2 THEN         !do only in 2D 
          IF firstRun = 0 THEN            !parameter that allow to run code only once 
             parameters firstRun = 1   !prevents running code again 
          ENDIF 
    
    	!SET STYLE "switch"
    	!!! ---------- show Selector hotspot----------
    		HSID=HSID+1
    		hotspot2 0, 0    , HSID, firstRun, 1    ! base
    		HSID=HSID+1
    		hotspot2 0,0-1    , HSID, firstRun, 3    ! ref
    		HSID=HSID+1
    		hotspot2 0, firstRun, HSID, firstRun, 2    ! moving
    		HSID=HSID+1     
    	
    	TEXT2 0,0,firstRun 
    
    ENDIF 
    
    IF GLOB_VIEW_TYPE = 3 THEN         !do only in 2D 
          IF firstRun = 0 THEN            !parameter that allow to run code only once 
             parameters firstRun = 1   !prevents running code again 
          ENDIF 
    
    	!SET STYLE "switch"
    	!!! ---------- show Selector hotspot----------
    		HSID=HSID+1
    		hotspot 0, 0,0    , HSID, firstRun, 1    ! base
    		HSID=HSID+1
    		hotspot 0,0-1,0    , HSID, firstRun, 3    ! ref
    		HSID=HSID+1
    		hotspot 0, firstRun,0, HSID, firstRun, 2    ! moving
    		HSID=HSID+1     
    	
    	DEFINE STYLE "text" "Arial", 150, 5, 0
    	SET STYLE "text"
    	TEXT 0.001,0,firstRun 
    	
    	ENDIF 

    The hotspots in 2D and 3D views allow me to adjust the value.
    So that is working fine.
    However in the object settings dialogue the parameter can not be altered and it the script editor it can not be altered either unless I comment out the section for ‘GLOB_VIEW_TYPE = 2’

    I hope I have explained this problem OK.

    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: Request skylight marker visibility from MVO #2509
    Barry Kelly
    Participant

    Thanks Gergely.
    It would be nice if there was.

    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: Request skylight marker visibility from MVO #2496
    Barry Kelly
    Participant

    Is there no REQUEST for this?

    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: Non-solid objects for BIMx. #2493
    Barry Kelly
    Participant

    Thanks Gergely.
    This is as I thought – just hoping there may be some other trick.

    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: How to protect your library? #2482
    Barry Kelly
    Participant

    I have no idea about the legalities but I would say if you are selling your objects and are prepared to provide support for them (bug fixes, upgrades) then by all means password protect them.
    If you are not prepared to support them then don’t password protect. Allow others to maintain them in the future.

    I wouldn’t have a problem with all objects having their scripts password protected so long as the parameters were still editable.
    A person may make an object and protect it but it will be useless to me as I may use different fills, pens, materials in my template that don’t suit their defaults for the object. I then have no way to edit the default parameter settings as they a locked together with the scripts. (yes I know I can set up favourites).

    Please Graphisoft at least allow us to still edit the default parameters even when an object is password protected.

    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: Angle editing hotspot locks at '0' in 3D #2413
    Barry Kelly
    Participant

    Maybe you do need to use ‘7’.

    Here is the code I use to change the pitch on my barge object.
    No problem stretching it to or from zero.

    		r = 0.350
    		HSID = HSID +1
    		hotspot 0, 0, 0, HSID, Ptch_Inp, 6			!center of angle
    		HSID = HSID +1 
    		hotspot r, 0, 0, HSID, Ptch_Inp, 4+128			!base hotspot
    		HSID = HSID +1
    		hotspot r * cos (Ptch_Inp), 0, r * sin (Ptch_Inp), HSID, Ptch_Inp, 5		!moving
    		HSID = HSID +1
    		hotspot 0, -1, 0, HSID, Ptch_Inp, 7			!center of angle
    		HSID = HSID +1
    

    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: Defining materials in a macro #2363
    Barry Kelly
    Participant

    If you define a material in a ‘Master_GDL’ file then they will automatically be available in the material list for all objects and elements.
    No need to call them at 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 64bit

    in reply to: Zone Stamp not outputting to schedule #2317
    Barry Kelly
    Participant

    Try doing the conversions in the master script rather than the 2D script.
    Anything you calculate in the 2D script can only be used in the 2D script and the values can’t be used to be sent back as parameters.

    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: Attempting to add Transformations to IF/THEN statement #2271
    Barry Kelly
    Participant

    I have never used Imperial measurements in a script but I suspect what you have shown is incorrect.
    ADD command requires just one value, you seem to have two for each.
    There must be another way of writing it as one figure.

    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

    Barry Kelly
    Participant

    We don’t rarely use the Graphisoft libraries as we have our own custom library that suits our needs better.
    I certainly would not call objects/macros in your libraries as I am aware they can change without me knowing what has changed.

    I am just getting into migrating objects this last week actually and have spotted the possible problem of migrating objects called by other objects.
    But I am hoping that if I keep the original names then the call will still work.
    I am aware that migrating an object with a new name is probably a more logical way to keep track of them but I am hoping keeping the same name solves the ‘CALL’ problem.
    Obviously there will be problems if parameters have changed in the called object but that would apply if calling a place-able object or a macro. So I just have to be careful to update any called parameters in the master objects as well.
    The biggest problem I am having at the moment is remembering/finding all the objects that call other objects/macros that I want to amend/migrate.

    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

    Barry Kelly
    Participant

    Tony,
    Please never use placeable elements as macros, it can cause many problems.

    Such as?
    I do this all the time and have not noticed any problems so far.

    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: Project Info – REQ? #2261
    Barry Kelly
    Participant

    I for one have been wanting to be able to use the autotext values for years.

    https://archicad-talk.graphisoft.com/viewtopic.php?p=159752&highlight=autotext#159752
    https://archicad-talk.graphisoft.com/viewtopic.php?p=160358&highlight=autotext#160358

    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 - 136 through 150 (of 170 total)