Auto-wiring bug?

[Jick]

When I bring for example Greater or Equal function close to case structure's tunnel outputs, LV 2010 tries to auto-wire two different wires (U8 and Boolean) to both function inputs. Why?

Should there be some kind of priority between different wires when suggesting auto-wiring?

See my attachments.

BR,

Jick

[Jick]

Nobody knows...?

[Haneef]

Hi Jick,

The Greater or Equal function accepts two different inputs. The criteria here is when you try to close towards two different inputs the 'Greater or Equal function' understands that there are two inputs and it connects to 'x' and 'y'. Before click it doesn't look for the type of the input because inputs are not connected to the block Greater or Equal function. But one after the click it looks for the criteria that 'Greater or Equal function' compares only same kind of tow inputs (means same data type), that is teh reason it shows immidiately unwired. And you can notice one more issue here first connects the input 'x' and looks for 'y' should be of same type. that is why unwired at boolean (input y).

Reagrds

Haneef

[Jick]

Hi Haneef,

Yes, that is same what I noticed.

For me, it would be more user friendly if function checks the types of data in wires before suggesting to connect them to inputs. And if there is two different kind of acceptable data available it should make a decision before click which one to wire based on higher priority.

Jick