LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

wire colour

Solved!
Go to solution

Hello, just a question, maybe someone can give me an idea for "best practice".

 

Often, in a bigger project, I need to use Notifiers, Queues, DynamicUserEvent structures. Usually we pass cluster data through these wires, for communication, broadcasting data, etc...

What I really hate is that since I use cluster data, all of the above wires has the very same color. In a bigger project, even if I try to make everything as simple as possible, it is very difficult to follow which wire is the Notifier, queue, etc, because they have the same color.

 

The question: I understand that, if we specifiy a data type to an ObtainNotifier VI (or queue, dynamicevent, etc..), the reference wire gets the color of that data type. But in my opinion, it would be better to show some difference between the different reference wires...in color, or in shape maybe?

 

Is there a workaround to get a more visible block diagram?

0 Kudos
Message 1 of 7
(4,044 Views)
Solution
Accepted by topic author Blokk

It's not a direct solution to your specific problem. But, if you start using LVOOP you have the ability to customize wire colors.

0 Kudos
Message 2 of 7
(4,036 Views)

You are right. I even want to start learning OOP to increase my productivity, but a feature to use different comm line references (queue, notifier, etc.) with different colors would be nice.

I understand that, the queue, etc ref wires get their color after the data type. In my case this data type is a strict type def cluster, so all of these wires get pink. Really bad to spot which line corresponds which comm line.

 

Actually I have found this idea what could also solve my problem:

http://forums.ni.com/t5/LabVIEW-Idea-Exchange/Allow-Typedefs-to-have-a-User-Defined-Wire/idi-p/92587...

 

Anyway, OOP is a must one for me, but it will take a while to get used to it...(i have never learned object oriented programming before)

0 Kudos
Message 3 of 7
(4,028 Views)

Blokk wrote:

Anyway, OOP is a must one for me, but it will take a while to get used to it...(i have never learned object oriented programming before)


Then get your SSP up to date (or buy the class) and take the self-paced online course! Yes, the LVOOP Class[meaning Course] is online!


"Should be" isn't "Is" -Jay
0 Kudos
Message 4 of 7
(4,022 Views)

yes, I have an active SSP licence, and I just finished Core 3 training (last year I got my CLAD level), it was very useful for my recent projects!

As early as i have time, I will start the OOP online training 🙂  But I have still a kind of feeling that objects are from the devil 😄   (hard to change thinking approach lets say)

0 Kudos
Message 5 of 7
(4,018 Views)

Blokk wrote:)  But I have still a kind of feeling that objects are from the devil 😄   (hard to change thinking approach lets say)

I am not one to bet often.  I'd wager a paycheck that objects are not from the devil.  Those controls, indicators, structures Icons and connector panes you work with today are all "Gobjects" with events properties and methods.  Smiley Wink  It does take a small twist in thinking thoughHeart


"Should be" isn't "Is" -Jay
0 Kudos
Message 6 of 7
(4,007 Views)

@Blokk wrote:

As early as i have time, I will start the OOP online training 🙂  But I have still a kind of feeling that objects are from the devil 😄   (hard to change thinking approach lets say)


Take a look at G#, a small addon that turns lvoop to reference based objects. You can find it in the addon utility or addq.se

/Y

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 7 of 7
(3,984 Views)