04-30-2012 09:12 AM
Hello,
I'm developing an tool with LabVIEW 8.5.1 where GUI is attached here; I'm trying my best to put together as nice GUI. Would you guys turn my GUI Skeleton to Better Looking GUI. Appreciate your help.
Thanks,
BlessingStar
04-30-2012 09:19 AM
Hi Star,
I would suggest:
- using system controls for good looking GUIs. The user is used to them...
- use system colors for good looking GUIs. They adapt to Windows UI schemes.
- use system frames/lines for GUIs. They adapt to Windows UI schemes.
- when you already started to customize buttons ("Exit") you should do so for all buttons ("Send").
- Use captions of the FP elements. That way you can use descriptive labels for controls while still providing meaningful "names" to the user.
- I would prefer an enum or a ring to select a "set" instead of sliders or knobs.
04-30-2012 10:05 AM
Any other suggestions are welcome.
Thanks
04-30-2012 04:12 PM
Unlike GerdW I am not a fan of the system controls. I work across platforms too much.
Even within one OS you need to be careful about fonts and font sizes. Try your GUI on every combination of OS version and screen size that you expect your users to have. Then either make several GUIs and choose the appropriate one for the particular system or try to make a GUI that works reasonably well across the range of systems.
Also be cautious about colors. Consider that some of your users may be color blind. Red-green color blindness is quite common among white males. Other forms of color blindness are much more rare. If color is important to the operation of your program, find some color blind testers before you make the final choices.
Here is what your GUI looks like on my system. Note the overlapping text.
Lynn
05-01-2012 07:38 AM
<my2¢>
</my2¢>
05-01-2012 07:45 AM
Additionaly provide Tip Strip to all the Objects that you place in the GUI this helps the user to identify the use of each controls and indicators.
05-01-2012 09:27 AM - edited 05-01-2012 09:29 AM
One thing that may be confusing is the checkboxes that change the text depending on the setting. I look at the checked box that says "Stop Industry Mode". Is it stopped or do I need to uncheck it to stop? It may be better to just always leave the text "Industry Mode". It is more clear that it is in that mode when the checkmark is there. As for the "Start/Stop Tester" box, those seem to be commands and should probably be command buttons. Reserve checkboxes for settings. If you really want to use a checkbox here then make the text always say something like "Tester Running" and make it run when the box is checked. Maybe it's just me but if I were running the program I might have to think a little too hard and might only get it right if my caffene levels were correct.
05-01-2012 09:49 PM
Thanks for all the suggestions & inputs. Based on the inputs, I'm customizing most of the objects with Modern Controls.
As for the Start Industry Mode, i do have to trigger one event when it's true and another event for False. Also, our end users are more familiar with Checkbox object (especially for that specific function). Even i don't like the Dial, but, what object would you suggest to Mimic Car Steering Wheel (Off, ACC, Run, Crank)...?
Thanks
05-02-2012 07:54 AM
That is an interesting question. The common paradigm for a key switch is a circle, which would use a knob control (you can customize it to look like a key). However, for ease of computer use, you would want to use a slider (small, set number of settings and visual position is important). You could also use a listbox or ring, but you would use the visual positioning you get with a slider or knob. A slider may be your best compromise, but be prepared for feedback that you should have used a knob. This type of decision needs to be made based on the existing paradigms and how willing you are to break them.