Flat sequence bug

[Yamaeda]

With the new icon editor it's rather easy to create logical and nice icons. I personally would limit all red icons to warning/error type vi's, but the red header is a good idea for easy identification.

/Y

[johnsold]

And black text on a red background is hard to read, at least for those of us who are color blind.

Lynn

[JÞB]

---

@Ziv Barlas wrote:

Good morning.

I was working on a report generation vi for my project, and it has grown way too stacked. Loop within case, within sequence etc.

To keep a large VI tidy I was using the cleanup feature.

After another cleanup my 2 stacked sequences and 1 while loop became "bugged".

I tried to restart both labview and, later, the PC. Bug did not disappear.

Is there any way to fix the bug? I tried to replace structures with alternatives from right click menu. After few conversions the problem is not seen, but shortly appears.

Any way maybe with HEX editor?

Flat sequence thinks it has a stacked sequence wall on the right side. Mouse can't be seen on screenshots though.

---

Getting back to the OP (Although E DJ has valid comments)

Bluntly, that is a large vi-  were you aware that you can also write software with LabVIEW? I don't ask to be mean or arrogant but when you need a navagation window to view the navagation window you've exceded the the development enviornments capabilities by poorly structuring your code.

So I tried to read it- I cannot.  I'm reasonably familiar with LabVIEW but there is no VI documentation, no comments I found, no discriptions or tips on the Front Panel objects.  I don't know what the vi does or who it does it too ( it won't take my daughter on a date I GARUNTEE!)

Now to the specific case- after multiple clean-ups the vi behaves badly.  The block diagram clean-up routine tends to move objects down and right from the block diagram origin.  the coordinates the clean-up function can deal with are integer data types and signed!  Your block diagram grew to a point where a known bug exists in that the block diagram requires more area than the compiler can interperate. (or so the theory goes- R&D is still evaluating last I heard and, I only hear rumors).  Its rather hard to duplicate this bug because you have to write very poorly structured code to duplicate it. 

So, lets try to get you back on track.  What do you want the project to do - and what functions do you need the software to perform.  let's code by intention-not spaghetti

[EvenDeejay]

Yamaeda and Lynn, you are absolutely correct. Since I'm the only one that use LabVIEW in my company, I haven't given it that much thought, other than something that was easy for me to use and remember. Is there a standard icon style that programmers usually use? Or is it up to the programmer to pick a style? Like red icons for error sub-VI's, blue for signal handeling, green for DAQ etc.. 

[JÞB]

Flaging for further follow-up

---

@Even Deejay wrote:

Yamaeda and Lynn, you are absolutely correct. Since I'm the only one that use LabVIEW in my company, I haven't given it that much thought, other than something that was easy for me to use and remember. Is there a standard icon style that programmers usually use? Or is it up to the programmer to pick a style? Like red icons for error sub-VI's, blue for signal handeling, green for DAQ etc.. 

---

Yes and no.   OpenG uses a light blue-green.  The point being you can deal with icons the same way you progam... use visual indications...  how do you use the heirachy view?... Might be a new thread!!!

[EvenDeejay]

I'm not quite sure what you mean by "how do you use the heirachy view". I usually creates small applications and haven't used the heirachy view before. Now I have a rather big application and the heirachy view is more confusing than this sign:

My Heirachy:

At least I can tell which are my icons 

[JÞB]

---

@Even Deejay wrote:

I'm not quite sure what you mean by "how do you use the heirachy view". I usually creates small applications and haven't used the heirachy view before. Now I have a rather big application and the heirachy view is more confusing than this sign:

My Heirachy:

At least I can tell which are my icons 

---

Well, E DJ

Start a new thread- PM me to get my attention!

The heirachy view should help you visualize your code--- not confuse it!---- tips and pointers from the best of us might just adjust your  icon style positively. maybe mine too !  though, I keep a nice stash of icon templates that serve ME well

[Yamaeda]

---

@Even Deejay wrote:

Yamaeda and Lynn, you are absolutely correct. Since I'm the only one that use LabVIEW in my company, I haven't given it that much thought, other than something that was easy for me to use and remember. Is there a standard icon style that programmers usually use? Or is it up to the programmer to pick a style? Like red icons for error sub-VI's, blue for signal handeling, green for DAQ etc.. 

---

It's up to the programmer to pick a style. I like graphical icons, some always just write some name/text of the functions. Full Red and Green feels like traffic lights and should behave in a similar manner is my feeling.

When i bundled some DMM communication i drew a picture of the DMM and added the text with the function. That way all DMM vi's looked similar but was fast to glance at and see what they did.

As Lynn mentioned, white text is better on red background. 🙂

/Y

[EvenDeejay]

There has been created a new thread about icon styles here. Stuff regarding OP's original question continues as normal.

Sorry, OP, for hi-jacking your thread. 

[billko]

---

@johnsold wrote:

And black text on a red background is hard to read, at least for those of us who are color blind.

Lynn

---

There was one person in my group a while back that insisted on yellow letters on a light green background and it was impossible for me to read.  (Interestingly enough, many of the new applications being programmed where I work use blue-yellow-red for our "stoplights," which is awesome for us colorblind folks.)

Edit: Oops, hadn't read the post above until after posting.  Sorry.