pyRevit Challenge - Day 12 (Click-Counter)

PLAN

Click. Click. Click. But Better!

Renumbering manually sucks… You need to select an element, click on parameter and fill in the data while remembering the right ordering number. BOOOORING….

So, the Goal for Today:

Create Click Counter tool where we'll be able to set our numbering rules and then click through elements one by one to renumber them.

We can also add control for Renumbering Rules, Category, Parameter name to make it really universal and useful in your daily work.

RESEARCH

Coding CheatSheet

Here's everything you might need for today's challenge.

Coding Blocks

Pick Element (with WarningBar)

Read/Write Shared Parameter

Infinite Loop: Pick Element

RPW Simple Form

Pick Element (with WarningBar)

Infinite Loop: Pick Element

Read/Write Shared Parameter

RPW Simple Form

Notes

🔸Watch Out For Infinite Loops

Whenever you use while loops double-triple check your exit conditions. Because it's very common to overlook and end up in an infinite loop. And for Revit it means you'll have to kill it to restart and it's annoying…s.

🔸Transaction In/Out Loops?

As a rule of thumb - Transactions should always stay outside of loops for better performance.

However, today we have an exception and we'll put it inside loops. Because we'll be in a loop where users can pick elements one by one and we want to apply results right after the click.

RESEARCH

Coding CheatSheet

Here's everything you might need for today's challenge.

Coding Blocks

Pick Element (with WarningBar)

Infinite Loop: Pick Element

Read/Write Shared Parameter

RPW Simple Form

Revit API Docs

Parameter Class
- LookupParameter Method
Transaction Class
- Start Method
- Commit Method
- RollBack Method

pyRevit Dev Docs

pyRevit - Efffective Inputs
pyRevit - Efffective Output
Docs - pyrevit.revit.pick_element_by_category()

Extra:

LRA Code Samples - Selection
RPW FlexForm

Notes

🔸Watch Out For Infinite Loops

🔸Transaction In/Out Loops?

As a rule of thumb - Transactions should always stay outside of loops for better performance.

However, today we have an exception and we'll put it inside loops. Because we'll be in a loop where users can pick elements one by one and we want to apply results right after the click.

OUTLINE

Step-by-Step Plan

Break down logic of the tool idea into smaller chunks so it's easier to brainstorm, find hidden steps and code.

Set Numbering
Rules

Optionally: Create
UI Form for Rules

Pick One
Element at the time

Calculate
New Value

Write To
Parameter

OUTLINE

Step-by-Step Plan

Break down logic of the tool idea into smaller chunks so it's easier to brainstorm, find hidden steps and code.

Set Numbering
Rules

Optionally: Create
UI Form for Rules

Pick One
Element at the time

Calculate
New Value

Write To
Parameter

NB!

TRY BUILDING
THIS TOOL YOURSELF
DON'T RUSH TO SOLUTION

Unless… You're a Beginner

According to GENERATION EFFECT

The Harder You Work, The Deeper It'll be Wired in Your Brain

NB!

TRY BUILDING
THIS TOOL YOURSELF
DON'T RUSH TO SOLUTION

Unless… You're a Beginner

According to GENERATION EFFECT

The Harder You Work, The Deeper
It'll be Wired in Your Brain

CODE

Code Quick-n-Dirty.

The Goal is to create a proof of concept. Don't try to make it perfect. Skip steps if necessary. Keep it ugly. Keep it slow. JUST. MAKE. IT. WORK…

Proof Of Concept

SCRIPT: PROOF OF CONCEPT

CODE

Code Quick-n-Dirty

The Goal is to create a proof of concept. Don't try to make it perfect. Skip steps if necessary. Keep it ugly. Keep it slow. JUST. MAKE. IT. WORK…