You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The block diagram of Actor.vi is messy and can be difficult to explain for new users (especially when teaching AF*). After speaking with @niACS at GDevCon, I propose to reorganize the diagram to improve readability while preserving all existing functionality. This refactoring will focus solely on the visual layout of the code, with no changes to the underlying logic or behavior.
* Usually block diagrams under vi.lib are unseen by LabVIEW developers. However, it is important AF students get a solid understanding of Actor.vi to understand why things work the way they do.
Additional context
This issue stems from a presentation I gave at GDevCon where I showed how actor.vi doesn't confirm to best practices and how straightforward changes would improve it.
The block diagram of Actor.vi is messy and can be difficult to explain for new users (especially when teaching AF*). After speaking with @niACS at GDevCon, I propose to reorganize the diagram to improve readability while preserving all existing functionality. This refactoring will focus solely on the visual layout of the code, with no changes to the underlying logic or behavior.
* Usually block diagrams under vi.lib are unseen by LabVIEW developers. However, it is important AF students get a solid understanding of Actor.vi to understand why things work the way they do.
Additional context
This issue stems from a presentation I gave at GDevCon where I showed how actor.vi doesn't confirm to best practices and how straightforward changes would improve it.
The following are screenshots I presented at GDevCon, which @niACS followed up with me to implement.
Link to presentation: https://www.youtube.com/watch?v=VUACQwXTXzk&t=1736s
This is the current Actor.vi block diagram
![Image](https://private-user-images.githubusercontent.com/104849466/412977593-27cb3d76-2472-42fa-b3d4-2e6093a42037.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk2NTcxMjgsIm5iZiI6MTczOTY1NjgyOCwicGF0aCI6Ii8xMDQ4NDk0NjYvNDEyOTc3NTkzLTI3Y2IzZDc2LTI0NzItNDJmYS1iM2Q0LTJlNjA5M2E0MjAzNy5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjE1JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIxNVQyMjAwMjhaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0xZjY2YjYyOTFiNDlmODJjM2RiMDBjNDgzMWRlMzNlNWVlZWZkODM1ZjUwYjZiZjJhZGE1NWVhYWVjYzRkNjc2JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.ucT68wof_KH-fCRcrc3y0bwtx7nLcv46jPu0Y7aJae8)
My proposed solution is the following:
With the following layout:
The text was updated successfully, but these errors were encountered: