Editing Line Weight settings from excel data (not linestyles)

Revit
, ,
1

I’m trying to build a dynamo file for editing line styles, line weights using an excel file. Input the data in excel, translate it in dynamo, then run it and apply them to the project. I figured out the linestyle creation part of it and it works well, but I can’t even find the options for editing the line weights. I can’t even find the api reference to this setting. Does anyone know what the api reference section is? Maybe provide a link?

My current script i pieced together should have the scales for IN[0] and the values for each style are in IN[1]

Here’s my script:

import clr
clr.AddReference('RevitAPI')
clr.AddReference('RevitServices')
from Autodesk.Revit.DB import Document, Transaction
from RevitServices.Persistence import DocumentManager

# Getting the document
doc = DocumentManager.Instance.CurrentDBDocument

# Inputs from previous nodes
scales = IN[0]  # List of scales, e.g., ['1"=1-0"', '1/2"=1-0"', ..., '1/32"=1-0"']
lineWeights = IN[1]  # Matrix of line weights, each row corresponds to a scale, each column to a line weight number

# Start a transaction to modify the document
t = Transaction(doc, "Update Line Weights")
t.Start()

try:
    for scaleIndex, scale in enumerate(scales):
        for lwNumber in range(1, 17):  # Assuming line weights are from 1 to 16
            lwValue = lineWeights[scaleIndex][lwNumber - 1]  # Access the corresponding value
            # Set the line weight for each number at the current scale
            doc.GetLineWeightSettings().SetLineWeight(lwNumber, lwValue, scale)
    t.Commit()  # Commit the changes if successful
except Exception as e:
    t.RollBack()  # Roll back if there's an error
    output = str(e)

# Output success message or error
OUT = "Line weights updated successfully!"

image
image1645×668 12.6 KB

image
image1319×807 33.5 KB

2

This is a long standing (7.5 years) API feature request - you can add you vote here

3

7.5 years!?! Holy moly autodesk. What’s the hold up on this one?

4

I’m not in that team, there are a few reasons to not do something. They all break down to the benefit vs the cost.

In this case we have a topic which is 7.5 years old, and has a total of 101 votes in favor of it.
Makes ~14 people each year who voted for it, and if we assume 1/10 of users would go looking this far we can say 140 people each year might want it. That isn’t much impact to divert any resource, and if that part of the application requires significant effort to fix it means things that impact way more people aren’t getting done (look at any new feature and you’ll see more impact in number of users).

Further, if there is another way to achieve the desired outcome (in this case transfer project standards from one file which is set up correctly) the value becomes even less. That is a semi manual way of working in that you need to open two files first, but an easy enough work around for what should be a once per model (or less) action.

Personally I think the development team would like to make all the features for all the users (not an under statement - they love to build new stuff!), but the reality is that they have to carefully pick and choose what to work on, and there is a lot of careful planning which goes into those decisions.

5

Yeah as Jacob stated earlier, at a conservative estimate, lets say there are 500,000 users of Revit worldwide… then the 101 people that want this feature would be 0.0202%

Personally, i don’t want them to waste time on it, so i haven’t voted. i’d rather them work on things more fundimental.

1 Like