LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

A Thing of Nightmares. Recommendations when reworking abhorrent code?

Solved!
Go to solution

@altenbach wrote:

@Ben wrote:
he crashes I have seen with diagram clean-up and very bad code, I think there is at about 65535 pixels wide.

Yes, the coordinates are I16 and there is no validation, making things go haywire once you step over the invisible boundaries. Bam!


From my experience, things tend to go awry before actually getting outside of those bounds. I've seen more than a few customers complain that they are "only" 20,000 pixels from the origin in one direction and have wires extending off into the block diagram ether. I'm sure you're not surprised to hear that those same customers tend not to use any source code control.

Matt J | National Instruments | CLA
0 Kudos
Message 61 of 68
(1,157 Views)

@Jacobson-ni wrote:

@altenbach wrote:

@Ben wrote:
he crashes I have seen with diagram clean-up and very bad code, I think there is at about 65535 pixels wide.

Yes, the coordinates are I16 and there is no validation, making things go haywire once you step over the invisible boundaries. Bam!


From my experience, things tend to go awry before actually getting outside of those bounds. I've seen more than a few customers complain that they are "only" 20,000 pixels from the origin in one direction and have wires extending off into the block diagram ether. I'm sure you're not surprised to hear that those same customers tend not to use any source code control.


I think it should be I64 to future-proof it against ever-growing monitor sizes.  😄

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 62 of 68
(1,146 Views)

@billko wrote:

 

I think it should be I64 to future-proof it against ever-growing monitor sizes.  😄

Because I'm such a nice guy, I'll let you post this to the idea exchange so you can get all of those kudos.

Matt J | National Instruments | CLA
Message 63 of 68
(1,138 Views)

@Jacobson-ni wrote:

@billko wrote:

 

I think it should be I64 to future-proof it against ever-growing monitor sizes.  😄

Because I'm such a nice guy, I'll let you post this to the idea exchange so you can get all of those kudos.


Very good Idea!  Mr, Ko, when you post that make sure to include just how big you expect monitors to get.

 

HINT: LEDs will need to get @100 Times smaller for a 64 bit monitor to fit inside the Kuiper Belt. ( the hole in the middle for the sun is a negligible size).


"Should be" isn't "Is" -Jay
Message 64 of 68
(1,131 Views)

How do you drive a display that is 8 light-hours wide?


"Should be" isn't "Is" -Jay
0 Kudos
Message 65 of 68
(1,124 Views)

@JÞB wrote:

How do you drive a display that is 8 light-hours wide?


I am sure the G-Force 108000000000000000-ti will have no problem 

========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 66 of 68
(1,120 Views)

Press the cleanup button and go home for the weekend.

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
Message 67 of 68
(1,107 Views)

@billko wrote:

Press the cleanup button and go home for the weekend.


Have you seen what happens when you hit diagram cleanup? Smiley LOL At any rate, I am going home for the weekend.

0 Kudos
Message 68 of 68
(1,075 Views)