[Rxtx] gui v1.0, example of use

Bob Jacobsen Bob_Jacobsen at lbl.gov
Sat Sep 30 12:46:27 MDT 2006


Very nice!!

One thing that would be useful is a way for the invoking code to 
limit the GUI.  If the program is for talking to a particular piece 
of hardware which has certain requirements, e.g. you know the right 
answer, it would be better not to have the user have to set it 
correctly.

*) If it's a question with only one correct answer, e.g. even parity 
is required, it would be good if the invoking program had an easy way 
to set that answer and make the corresponding control not show (set 
it not visible, or just not create it in the first place)

*) If there are a restricted range, e.g. the device only talks at 
1200 or 9600 baud, it would be good to not display other choices.

Sorry to sound like I'm asking you to do even more work; I certainly 
appreciate what you've contributed so far.  If you'd like, I'd be 
happy to try to figure out a way to do this consistent with the 
structure of your existing code.

Bob
-- 
Bob Jacobsen, UC Berkeley
jacobsen at berkeley.edu +1-510-486-7355 fax +1-510-643-8497 AIM, Skype JacobsenRG



More information about the Rxtx mailing list