Michael Herse

Forum Replies Created

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • Michael Herse
    Participant

    Hi Leah

    Label formatting is a fairly complex things, especially when you start taking into account the need to respond to rotated views, flipping/mirroring, rotation and anchor points. If I need to make a new parametric one, I usually start by taking a standard Graphisoft supplied labels and modifying it.

    The parameter that holds the location of the label text relative to the leader is Label_Position, so have a read up on this in the GDL reference guide and check out a few existing labels to see how it is being used.

    Alternatively, the functionality you seek has already been added to Archicad 23 by Graphisoft. You can now set the leader of the text/auto text label to start in the middle of the first row of text.

    Hope that is of some help
    Cheers,
    Michael.

    in reply to: Writing to a text file #4264
    Michael Herse
    Participant

    A good starting point would be to have a look at the example script and files here http://gdl.graphisoft.com/tips-and-tricks/how-to-read-and-write-text-files.

    Cheers,
    Michael.

    in reply to: XML addon & script location #3674
    Michael Herse
    Participant

    Hi Gergely. Thanks for the help. Some more info below.

    – and the purpose of using external data…

    The goal is to allow users to create and assign ‘user defined types’ to doors and their sub-elements (frames, leafs, seals, size, vision panels, finishes etc) that impact the 3D model + some other things such as locking, door stops, closer, hinges etc. that will be stored with a door type for scheduling purposes. The external file is used to centrally store the values of the parameters for the user defined types, and push any change to a defined door type of sub-element through the model. Types will be specific to each project. Some project will have 1000+ doors. One of our current projects has about 5000+ doors made up of about 250 different door types, spread across 4 teamwork files, and is the reason why we are investigating this to see if it will provide an efficient way to push change through the projects and standardise door settings for doors that are meant to be the same, but aren’t in the model.

    – how often the source will change

    Not too often I hope. There will be times when the changes are intense, but hopefully that will be limited to only a couple of periods during the life of the project (late DD and Mid CD). Most of the time, I expect people will just be adding new doors and assigning a type to them, or changing individual doors to a particular type.

    – will it be a part of the library, and loaded together with the objects

    I haven’t got that far yet. Ideally the external file will live in the project library, but the projects will be teamworked, so I need to investigate the implications of this further. At the moment, while we are testing & developing things, the XML is hosted on our file server (OSX)

    Cheers,
    Michael.

    in reply to: XML Extension #3655
    Michael Herse
    Participant

    Thanks for the suggestions guys, especially your offer of assistance Kristian. The tool that Joachim posted is all I need for the time being.

    Cheers,
    Michael.

    in reply to: XML Extension #3631
    Michael Herse
    Participant

    Hi Kristian

    Did you ever work out how to create a new line? I’m just starting to play around with the XML Extension, and having new Children and Siblings that I write to the XML file on new lines would make interrogating my results much easier. Currently everything is just on 1 line, making the xml difficult to read when I open it in Xcode.

    Cheers,
    Michael.

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