Replies: 5 comments
-
The warning dialog box already exists. |
Beta Was this translation helpful? Give feedback.
0 replies
This comment was marked as off-topic.
This comment was marked as off-topic.
-
@niACS had a suggestion to just add "(Deprecated)" to the end of the abstract message menu it. Bonus: adding that text could be conditional on the version of LabVIEW being used. Get's a thumbs up from me. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Sounds good to me too! |
Beta Was this translation helpful? Give feedback.
0 replies
-
I am moving this into a discussion. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Is your feature request related to a problem? Please describe.
LabVIEW 2020 introduced interfaces which was a huge boon for Actor Framework. In most cases, interfaces provide a better/easier way to decouple Msgs from actors than did their predecessors, abstract messages. The UX should point users away from abstract messages and to interfaces.
Describe the solution you'd like
Abstract functionality should NOT be removed, but Project Provider tools around making their messages should be moved out of the top-level of AF menu items. Perhaps move their scripting menu item into a "Deprecated" sub-folder in the menus.
Describe alternatives you've considered
Perhaps, when the user chooses to create an abstract message, a dialog appears that asks the user if they really want to do that vs using interfaces. It could be like the message rescripting dialog where users can choose to skip the dialog in the future.
Additional context
Move these into a nested menu.
Beta Was this translation helpful? Give feedback.
All reactions