Re: kButtonX processing, Root 2.23/10, WinNT 4

From: Rene Brun (Rene.Brun@cern.ch)
Date: Mon Jan 10 2000 - 14:17:36 MET


Hi Mariusz,
Your problems reflect the status of our old GUI under NT.
All what you request is available in the new GUI under Unix, including
double click.
We will report about the NT plans at the coming Root workshop.
More info about the ROOT 2000 workshop is available at:
            http://root.cern.ch/root/R2000Welcome.html

Rene Brun

Mariusz Stanczak wrote:
> 
> On Fri, 07 Jan 2000 15:12:27 +0000, Rene Brun wrote:
> 
> >Hi mariusz,
> >
> >Mariusz Stanczak wrote:
> >>
> >>    I've ran into a difficulty in my my class ExecuteEvent member.  It
> >> appears that kButton{2|3}{Down|Up} are being trapped, and are not accessible
> >> to the user program.  I successfully use kButton1, and now I need to use
> >> kButton2.
> >
> >Button2 and 3 are currently trapped by TCanvas::HandleInput.
> >Clicking on button2 sets the current pad.
> >The button 3 is used bor the context menus.
>    I have not tested it yet, but are the other events available, like double
> click on any button?
> >
> >>    As a side thought, I'd like to suggest that the dialogs displayed to the
> >> user by root, for example to change graphing options on a TPad, etc. display
> >> the current values.  A nice, ergonomic touch.
> >
> >Which graphing options would you like to see ?
>    I think it would be "nice" to display the current values, ie. the values
> presently in force at the time any dialog is displayed; for example, from
> the right click menu on a canvas Range displays a dialog with four edit
> boxes for x1, y1, x2, y2.  Those boxes are displayed empty (as it's true for
> most fields on most dialogs (some display default values))... I'm suggesting
> that the current values (in this example, the current range values for the
> canvas) are displayed to the user for editing.  Even in this simple case
> there is the benefit of letting the user know what the current setting are
> (a starting place to assist in what the values could be in order to make the
> canvas smaller/larger, whatever user's need is).  In other cases displaying
> current values would also save some typing, for example in TCutG::Fit
> dialog.
> >
> >>    Also which class could/should I use to display such a dialog window with
> >> a few (five is my present need) edit boxes and some static labels in my
> >> program?
> >
> >If I remember you are working on NT where the new GUI is not available.
> >To give an answer, I would need more explanation on what you want to do.
>    Something akin to the dialog in the TCanvas Range right click menu.
> >
> >Rene Brun
> >
> Thank you,
> 
> /Mariusz



This archive was generated by hypermail 2b29 : Tue Jan 02 2001 - 11:50:16 MET