Barry Kelly

Forum Replies Created

Viewing 15 posts - 121 through 135 (of 170 total)
  • Author
    Posts
  • in reply to: Reposition-able text #2918
    Barry Kelly
    Participant

    Without actually writing the code all you need to do is create the script for the moveable (stretchy) hotspot – you can ad a rotating hotspot too if you want.
    Then use an ADD2 command (and ROT2 command if desired) using the hotspot parameters.
    Then TEXT2 0,0,”text” and the text will move with the hotspots.

    If you are not worried about moving the text differently for different scales and/or rotating then you can skip the ADD2 and ROT2 and use the hotspot parameters directly in the TEXT2 command.

    If you need an actual coded example let me know.

    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: 2D view for 3D object #2903
    Barry Kelly
    Participant

    Your object is calling another object called “stages 45” in the 3D script.
    I would be guessing this is in the embedded library of your original file which is why it works there but is not loaded in any new file which is why you are not seeing any 3D.
    You need to export that object from the original embedded library and place it in your loaded library.

    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: Array Parameter Lock Issue #2879
    Barry Kelly
    Participant

    I can confirm this and other strange things are happening in the script editor for 20.

    If I copy and paste in the main script window it appears correct but it is not really working.
    Look in the pop-out window and it is not there or something completely different happens which destroys the script.
    It may look Ok but it isn’t.
    Look at this simple example where I have copied and pasted a small piece of 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 64bit

    in reply to: PROJECT2 bug in version 20 #2781
    Barry Kelly
    Participant

    Thanks for the fix.
    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 i can set WIDO_​SILL_​HEIGHT ? #2740
    Barry Kelly
    Participant

    I’m still not sure I am on the right track but you could place your door and manually set the sill height to what you want in relation to the wall base or storey level.

    But if you want to automatically raise the height based on the door type then I would just add something like this to your 3D script …

    if door_type = "type A" then
    ADDy 0.005
    endif
    
    if door_type = "type B" then
    ADDy 0.007
    endif
    
    if door_type = "type C" then
    ADDy 0.009
    endif

    Then when you place the door make sure you place it with the sill set to zero height above the wall base (or storey).

    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 i can set WIDO_​SILL_​HEIGHT ? #2738
    Barry Kelly
    Participant

    I am a little confused as to what you are trying to do.
    WIDO_SILL_HEIGHT is a value calculated from the height of the door or window from the base of the wall it is placed in.
    It is not a value you can set in the object script as it is not a parameter like height and width (A & B).
    While you are scripting it may always return a value of zero as you object as yet does not belong to a wall.
    It is not until you place an instance of the door in a wall that it can determine a value.

    You can force it (for testing) in your script by saying WIDO_SILL_HEIGHT = 0.100 in the master script but you will need to remove that line when saving the object for real as otherwise it will always use that value regardless of what height you place 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 64bit

    in reply to: How i can set WIDO_​SILL_​HEIGHT ? #2735
    Barry Kelly
    Participant

    You set it where you show your image – in the settings dialogue or info box.
    WIDO_SILL_HEIGHT will read this value for use in your script – not set the value.

    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: Total sum of value in buffer #2724
    Barry Kelly
    Participant

    Maybe this?

    for n = 1 to (NSP)
    	totalSum = totalSum + GET (1)
    next n
    
    print totalSum

    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: Testing for D_​iSlidingType in LibraryGlobals13 #2723
    Barry Kelly
    Participant

    Still doesn’t answer the question why the GS door worked though.

    I am guessing the GS door knew to use the LibraryGlobals13 file for the 19 library and your doors would have been using the other one.
    You will probably see two GDL options in your MVO dialogue.

    I know when you CALL a macro by name it actually compiles the GUID into the script (although we only see the name).
    Once saved you can rename the call macro file in your operating system and the object will still find the correct macro even though it is calling the old name.

    So I am assuming the same is happening with the LIBRARYGLOBAL command – each was linked to the GUID for their respective macro file.
    I may be wrong.

    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: Editing text in the graphical interface. #2718
    Barry Kelly
    Participant

    Thanks Dominika,
    I thought that was going to be the answer but I was hoping there may have been something I wasn’t aware of.
    Maybe it could be added to the wish-list of GDL improvements please?

    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: PROJECT2 bug in version 20 #2683
    Barry Kelly
    Participant

    Thank you Dominika.

    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

    In the interface script of the object (in the main dialogue – not the separate script window) press the button at the top for “Set as Default”.

    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: Label handles #2650
    Barry Kelly
    Participant

    Hotspots are only visible when you select the object (label).
    There is no way to make a hotspot visible without selecting that I know of.

    Textblock handles are completely different to hotspots and can’t be scripted.
    They simply show the extents of the text box.

    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: Requesting the length of an autotext string #2635
    Barry Kelly
    Participant

    Unfortunately you can only use autotext values.
    GDL can’t actually read the values in autotext fields so therefore can not determine the text length.
    It is a long standing problem.
    We could do so much with autotext if only we could read the values.

    Follow this link …

    Project Info – REQ?

    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: Migrating to AC20 #2615
    Barry Kelly
    Participant

    A_ is used in the parameter script, which is GLOB_SCALE in old form.

    Thanks for pointing this out – it is a good lesson.
    I now must remember to search for the old form of GLOBALS when fixing up my library parts.
    I might have missed this otherwise.

    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 - 121 through 135 (of 170 total)