kicad-developers team mailing list archive

[Jerry Jacobs <xor.gate.engineering@xxxxxxxxx>]

It would be much better if all the toolbar options also in the menus, 
eventually with (configurable) hotkeys. Then there should be a option 
to disable the toolbar(s) :-). Also enabling the AUI to move the 
toolbars to a other screen with overflow would be good to overcome the 
problem if one screen is to small.

I was not able to get it fixed that the toolbars put the entries that 
overflow if it is rescaled under the overflow arrow.

Hope this is clear enough.

Jerry

On Wed Aug 24 22:25:34 2011, Wayne Stambaugh wrote:
> On 8/24/2011 3:41 PM, Dick Hollenbeck wrote:
> > On 08/24/2011 02:07 PM, Wayne Stambaugh wrote:
> > > On 8/24/2011 2:12 PM, fabrizio wrote:
> > > > Hi,
> > > > thanks, I am glad you like them.
> > > >
> > > > may I ask why you want the buttons size to stay at 16pt? is it only a
> > > > matter of space? if so, how?
> > > For toolbar images, 26 or 24 pixels is fine for all platforms.  On some
> > > platforms (read Windows) the larger icons will make the menu spacing much wider
> > > than the menu text (assuming your not using a 26 pixel font).  Menu images are
> > > disabled by default on Linux with the latest Gnome 2 (not sure about Gnome 3)
> > > so it wont effect Linux users.  If the user enables the Gnome menu images, the
> > > same problem will exist on Linux.  I'm not an OSX user so I cannot comment on
> > > how the larger menu images will look.  I could personally live without images
> > > in the menu bar.  I would prefer to use the space taken by the image for more
> > > descriptive menu text but I'm sure there are plenty of folks who would disagree
> > > with me on that one.
> > >
> > > Wayne
> >
> >
> > Guys,
> >
> >
> > I committed to write an automation script which generates all the bitmaps from
> > *.svg to *.cpp.  I believe it will be possible to parameterize the target image
> > size(s).
> >
> > I am now only waiting for the *.svg s.
> >
> > This *.svg ->  *.cpp automation is to live outside the normal Kicad build process.
> >
> > However, it can be done twice, or three times, resulting in multiply sized PNG
> > containing *.cpp directories.
> >
> > Each of these directories can be checked into the source tree.
> >
> > Then, the master CMakeList.txt file for the Kicad project can dynamically pick
> > which one gets chosen, based on a parameterized *.cpp containing directory name.
> >
> > I won't take it that far, only to the point of having parameterized build
> > automation, with a specific view to reward Fabrizio for his efforts, meaning I
> > intend to honor whatever bitmap size he wants, as payment for his efforts.
> >
> > Others can cater to the hobbyist computers, later.  This infra-structure will at
> > that point be easy to extend, but I personally will not have time for that 2nd
> > stage effort.
> >
> > Dick
> >
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~kicad-developers
> > Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~kicad-developers
> > More help   : https://help.launchpad.net/ListHelp
>
> Dick,
>
> I appreciate your and Fabrizio's efforts on this and think the new images will
> give the Kicad user interface a much needed face lift.  I was merely pointing
> out the potential pitfalls of using the larger images in the menu bar.  I was
> hoping someone would take my hint and suggest removing the images from the menu
> bar altogether.  I would be willing to do this if we can get a consensus among
> the Kicad users and developers.  As it currently stands, they are only
> displayed on Windows by default.
>
> Wayne
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp