gnumed-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnumed-devel] bootstrap database


From: Sebastian Hilbert
Subject: Re: [Gnumed-devel] bootstrap database
Date: Fri, 25 Mar 2011 20:54:03 +0100
User-agent: KMail/1.13.6 (Linux/2.6.37.3-16-desktop; KDE/4.6.0; i686; ; )

Am Freitag, 25. März 2011, 09:53:47 schrieb Karsten Hilbert:
> Hello Vaibhav,
> 
> > Please have a look at the attached screen shot. You will notice that the
> > default placement (centering ) of gui for addition of drug (substance) is
> > such that the menu items on left side are not visible and one has to use
> > horizontal scroll every time.
> 
> Ah, I see. Well, GNUmed does not do much of anything to
> define the size of dialogs. 

Yeah but that does not mean it cannot help out here. Maybe some clever use of 
the wx size hints (if there is such a thing) might make it calculate the 
needed space. maybe the children do not properly report their size.

> In this very case, in fact, it
> even defines a minimum size as a hint to the GUI engine.
> GNUmed cannot do much about the fact that the widget toolkit
> decides that scrolling is desirable here.
>

It might work by increasing the size hint as a crude hack.
 
> > This can be dealt with by reducing the length of entry field by few cms.
> 
> No, because GNUmed does not define (and cannot define
> either) the lengths of fields.

I see.

> 
> > Moreover, the "OK" button at the lower end of gui is out of focus (not
> > visible and accessible by mouse) as gui is not resizing according to the
> > display/desktop size.
> 
> Exactly. This is the same problem. And, as you say, the
> reason is that "gui is not resizing according to the
> display/desktop size".
> 

It might get the wrong size hints.


> > This problem also occur with gtklp (printing gui).
> 
> Yes, because gtklp uses the same GUI toolkit, namely gtk, which is GNOME.
> 

That would indeed make gtk the culprit and one would hope it will be fixed 
upstream.


Sebastian



reply via email to

[Prev in Thread] Current Thread [Next in Thread]