[Gnumed-devel] Feedback on GNUmed-client.0.2.8.0.dmg for Mac OS

[James Busser]

Differences with 0.2.8.0 on Intel as compared to 0.2.7.1 on PowerPC:
... testing from both done connecting to remote salaam db...
... screenshots and logs in next email

Can't remember whether both defaulted to connect to local (Mac) db  
and whether both afterward remember the most recent setting, or whether
0.2.7.1 defaulted to use the remote salaam db.

0.2.8.0 on Intel suffers the same display problem while showing  
status of plug-in modules being loaded

0.2.8.0 on Intel opens with better-formed and properly positioned  
windows
... still shows some incorrectly-formed rectangles (see lower  
corners) but *much* better!

The "Patient Details" screen is nice except that, at the bottom edge  
of the buttons, a couple of pixels are missing.

... it is now possible to see, and use, the patient search field
... searching for Kirk still shows 2 matches (are these 2 distinct  
persons in database?)
... searching for Ki Ja shows 6 matches (3 instances of each of 2  
distinct persons in database?)
... searching for Ja Ki shows the same 6 matches

I tried the Tools > Snellen chart command which did pop open a  
"Snellen Chart Setup" window however triggered a GNUmed exception  
handler. The handler did allow me to enter/edit in the Comment field  
however the "View log" button remains unresponsive... when I clicked  
"Send report", the next window did pop open and I accepted the option  
to include the log and, after apparent processing, I was returned to  
the original exception handler window. This makes it hard to know  
whether a report had in fact been sent. Is it desirable for the  
exception handler to default to "Send report"  and perhaps code it so  
that after this is clicked, the default button becomes "Keep running"?

After the Snellen exception, I continued to run GNUmed, though could  
not get the Snellen window to do anything (clicking OK just dismissed  
it and changing settings within it appeared to make no difference).

From within the exception handler, the button "Close GNUmed "  
worked. This generated a Python "quit unexpectedly" log and I include  
that in the next email.