The LIST 2

[tbob]

CC:  You have entirely too much free time on your hands, n'est pas? 

[tst]

What about the 7.1ly challenged people?

[chilly_charly]

Some improvements :

- the issue date is now displayed in the window title bar, when a new List file is loaded

- the reference column (actual replies) is slightly colored in green

- it's a LabVIEW 7.0 version !!! That should make tst happy and generate a flow of stars...

I need some help to solve an annoying detail :

the table doesn't update correctly. For instance, after sorting a column, the header should be colored in dark grey. However, this is only effective after clicking in 2 different table cells ! I have spend several hours on this problem, and it starts smelling as a LV bug. Similarly, each click on the table, in an "inert" zone generates a flicker. Any idea ? (for those who are willing to help, the colorize vi is in the upper while loop)

[Ben]

Hi JLV,

Take a look at LV-Pro's posting in this thread for the new form of carrot.

http://forums.ni.com/ni/board/message?board.id=BreakPoint&message.id=318&jump=true

tst,

LV-Pro, Molly and I had a disgreement on how to pronounce your name.

Would you prefer

"Test"

or

"Tee-Ess-Tee"

or

other?

See Y'all back here after NI-Week.

Ben

[tst]

Ben, those should be your troubles...

I can think of another option you didn't mention - how about the sound "tst" which you can make (like when you want to call someone's attention without making a lot of noise)?

As another tip - it's not an abbreviation of "test", so you can say T.S.T, although you can say whatever you like, as long as I'm not around. There is a story behind that name, but it shall not be told at the moment. Maybe NIWeek 2006?

[Ray.R]

Tttttsssssttttttt thhhaanks Ben,

I forgot about that thread.

😄

Very Nice Mug..

ttttttttttttttsssssssssssssstttttttttt  or   pppppppppppppppsssssssssssssssssttttttttttt

^^^^  English ^^^^^^^                                        ^^^^^^^^^^^ French ^^^^^^^^^^^^^^                        >>>>>>>>>>>>>> ?????????? <<<<<<<<<

[tst]

BUGS???

In a LIST related VI?

Noooo....

Anyway, it's really nice and some advantages over viewing in excel.

A few points:

1. Not all people have a 235434 by 454363 screen resolution. You could make the table adapt and have a horizontal scrollbar.
2. The browser (nice touch, BTW) uses Activex, which isn't nice for non-windowers. How about using the Open URL... VI from the App Control>>Help palette (at least if the target isn't windows)?
3. You can place all the code that's in the coloring subVI into the user event case "2" and get rid of the top loop (and the subVI). Any reason not to do that?
4. I assume you're right and this is a bug, but the problem with coloring the cell happens when you edit the cell. The cell seems to become "unselected" only after you click in 2 other cells. You can work around this by adding a KeyFocus property set to F at the top of your property node with all the colors.
5. I have no idea where the flickering comes from, because that happens even when you don't do anything except selecting a cell. It happened even when I deleted almost all the code in the VI (everything except the mouse up event).

[tst]

You can get rid of the flickering by having a small control (even a transparent one) over the table. This causes invalidation, according to Greg, which is apparently good for us. I posted a bug message with an example here.

[chilly_charly]

tst

Thanks for your input. You deserve... and get 5 stars.

Not all people have a 235434 by 454363 screen resolution. You could make the table adapt and have a horizontal scrollbar.
I choosed to hide the horizontal scroll bar because it had a poor look (kind of a black arrow overimposed, appears in LV 7.0 and 7.1... bug ?). However, since you are sympathetic, I have added a menu item to allow the display of the H-scrollbar for the LVwers that can't afford large screens 🙂

The browser (nice touch, BTW) uses Activex, which isn't nice for non-windowers. How about using the Open URL... VI from the App Control>>Help palette (at least if the target isn't windows)?
You teached me something here. The modification has been done.

You can place all the code that's in the coloring subVI into the user event case "2" and get rid of the top loop (and the subVI). Any reason not to do that?
There is a good reason for that. I found that in some occasions, the colorize rate became very slow (up to 3 seconds, could not identify the problem, may be related to my code, not to LabVIEW). During that time, of course, the event loop was not responsive. That's why I have moved this vi in a separate loop, just to keep a "nervous" user interface.

I assume you're right and this is a bug, but the problem with coloring the cell happens when you edit the cell. The cell seems to become "unselected" only after you click in 2 other cells. You can work around this by adding a KeyFocus property set to F at the top of your property node with all the colors.
Nice to admit that there might be a bug here. Thanks for the work around : it works !

I have no idea where the flickering comes from, because that happens even when you don't do anything except selecting a cell. It happened even when I deleted almost all the code in the VI (everything except the mouse up event).
The flickering occurs even after removing all the code, and running the vi in repetitive mode. So this could be another bug (or the same...)

Three LabVIEW bugs detected in a single vi !!?  I guess that could be a record. Let's report it then wait and see if somebody at NI can homologate this score...

I'll post soon the new version.

Any more comments ?

[chilly_charly]

---

tst a écrit:
You can get rid of the flickering by having a small control (even a transparent one) over the table. This causes invalidation, according to Greg, which is apparently good for us. I posted a bug message with an example here.

---

Unfortunately, this creates also a strong slowing down of the colorize rate. This is a way of demonstrating the role of the separate loop...