Archive for the ‘User Interface’ Category
Monster Panel IV
0
51 wires? No – use a cable. In Part III, we talked about how to take 3672 copies of a 300-channel list and cut the memory requirements down to size. The price we pay for that savings is a bit more work on our part. But it’s a
Monster Panel III
Re-think the easy ways you have used forever. In Part I, I gave the rough outline of the task: how to manage over 12000 controls/indicators on one panel. In Part II, we started whittling the task down to size, using sub panels and reentrancy.
Monster Panel II
Figuring out what you do NOT have to do. In Part I, I gave the rough outline of the task: How to manage over 12000 controls/indicators on one panel. The first thing to realize is that the beginner’s reaction (“holy crowdation Batman, that’s impossible”) is
Monster Panel I
Handling thousands of controls is easier than you think. LabVIEW programmers progress from the excitement of the new paradigm to just using it as a tool. We’ve all produced some “spaghetti” code, and we’ve all had to look at somebody else’s flavor of spaghetti and
Keeping your charts up to date
Use your chart to indicate time of day. LabVIEW charts, out of the box, don’t lend themselves to displaying the actual time of day. By default they give you 1024 history points and a visible scale of 0-100 so what you see is in terms
An Improved Analog Clock
Sometimes all that digital stuff is just too bland. A bug undocumented feature of the original analog clock was that the markers on the scale were at intervals of 1.25 seconds, a consequence of LabVIEW preferring to use 4 intervals per major tick, when we silly
An Analog Clock (first version)
Sometimes all that digital stuff is just too bland. If you want to display a time-of-day clock in LabVIEW, it takes three seconds to plop down a TIMESTAMP indicator, and 10 more seconds to enter ADVANCED EDITING mode, and skip the month, day and year,
The Terminator
Make sure that quitting time is followed by happy hour. Generally, you don’t do anything special in a LabVIEW program to quit; when it runs out of things to do, it terminates. (Quite clever, that). Your program has a loop waiting on the user to
Where Am I?
Use a tool to find yourself. When your program is large enough to have multiple folders to store files in, or read them from, then you have to know, or find, where those folders are. Asking your users to create those folders will surely raise
Contact Info
207-593-8109
Culverson Software
184 Lakeview Drive
Rockland, ME 04841
General questions:
Accounts/billing questions:
