shaun coomber

Forum Replies Created

Viewing 13 posts - 1 through 13 (of 13 total)
  • Author
    Posts
  • in reply to: Checking library for file names #4531

    shaun coomber
    Participant

    For example, is it possible to use n = APPLICATION_QUERY (“LIBRARY_MANAGER”, “”, files_list) for txt files, or only IES and image files?

  • in reply to: Requesting platform, mac or windows #4189

    shaun coomber
    Participant

    Hi Dominika,

    Thank you, I will try that too.

    I’ve just found another difference between Mac and Windows interfaces… UI_INFIELD with method 8 can be set with different heights on Windows, but on Mac this setting is ignored and the drop-down list is also displayed with the same height.

    UI_INFIELD{3} “editField”, 75, ypos-3, 313, 22,
    8, “”, 0, 0, 0, 0, 0, 0,
    “”, editType[1], editType[1],
    “”, editType[2], editType[2],
    “”, editType[3], editType[3],
    “”, editType[4], editType[4]

  • in reply to: Requesting platform, mac or windows #4173

    shaun coomber
    Participant

    ! Parameters for ArchiCAD version and Platform
    Dose = 0
    sts = REQUEST(“Name_of_program”, “”,TeX)
    IF STRSTR(TeX,”.EXE”) OR STRSTR(TeX,”.exe”) THEN Dose = 1

    That is brilliant, it works perfectly! Thank you

  • in reply to: Requesting platform, mac or windows #4171

    shaun coomber
    Participant

    Here is the code for method 1:

    UI_INFIELD{3} SelectField, xpos, ypos+yspc, useWidth*4+20, useHeight*2,
    1, 25,
    8, 2,
    useWidth, useHeight, useWidth, useHeight,
    1, “”, 1,
    2, “”, 2,
    3, “”, 3,
    4, “”, 4,
    5, “”, 5,
    6, “”, 6,
    7, “”, 7,
    8, “”, 8

    And here is the code for method 6:

    FOR k = 1 TO 4

    UI_INFIELD{3} SelectField, xpos+useWidth*(k-1), ypos+yspc, useWidth, useHeight,
    6, 25,
    8, 2,
    useWidth, useHeight, useWidth, useHeight,
    k, “”, k+10,
    k, “”, k

    NEXT k

    FOR k = 5 TO 8

    UI_INFIELD{3} SelectField, xpos+useWidth*(k-5), ypos+yspc+useHeight, useWidth, useHeight,
    6, 25,
    8, 2,
    useWidth, useHeight, useWidth, useHeight,
    k, “”, k+10,
    k, “”, k

    NEXT k

    With the following trick in the parameter script:

    IF SelectField > 10 THEN
    SelectField = SelectField – 10
    PARAMETERS SelectField = SelectField
    ENDIF

  • in reply to: Requesting platform, mac or windows #4168

    shaun coomber
    Participant

    And here are the method 6 images…

  • in reply to: Requesting platform, mac or windows #4165

    shaun coomber
    Participant

    I’ve tried two different methods.

    With ui_infield method 1, the interface leaves more of a space between each option on Windows. Even if I increase the size of the field to accommodate the scroll bar etc. it doesn’t display well. On Mac, it looks fine.

    With ui_infield method 6, I have created a separate ui_infield command for each option. On windows it displays nicely, but on Mac it doesn’t show which is selected.

    Method 1 images are attached…

  • in reply to: Layout size #4077

    shaun coomber
    Participant

    Perfect, thank you

  • in reply to: Label that displays another object's parameter #4074

    shaun coomber
    Participant

    I expect AC22’s calculated element properties will do this, with the standard labels.

  • in reply to: Properties Controlled by MVO #4073

    shaun coomber
    Participant

    It’s possible to request element properties in the model view options, though Graphisoft have told me this isn’t the intended use so not to rely on it. It isn’t possible to request IFC properties.

    I have a zone stamp that uses the MVO, and I am testing other solutions to access the IFC properties – successfully so far. I hope to release an updated version once AC22 is on the market, to take advantage of the Zone’s new text settings and tabbed UI.

    Denny – Rosey has a copy of our Zone Stamp, but not the version I’m working on with IFC.

  • in reply to: Graphical Hotspots & Complex Profiles #3307

    shaun coomber
    Participant

    Hi

    I figured out a way to position hotspots correctly based on the profile dimensions using MUL.

    That brings me on to my next question…

    Although the MUL command affects the hotspots positions, it doesn’t seem to affect the length of the graphical input. See the attached test object.

    Does anyone have any suggestions for this?

    Thanks
    Shaun

  • in reply to: Graphical Hotspots & Complex Profiles #3298

    shaun coomber
    Participant

    Hi

    I understand that, but I am trying to figure out a way to control the number of beams using hotspots (without the profile width if that’s possible)…

  • in reply to: Beam and column display – model view options #3264

    shaun coomber
    Participant

    anyone?

  • in reply to: Requesting the length of an autotext string #2634

    shaun coomber
    Participant

    It wouldn’t let me attach the .gsm, but it’s attached to testtrack #58007 if you can access that.

Viewing 13 posts - 1 through 13 (of 13 total)