Hello everybody,
first of all I hope my mails on the issue 'Prompt/TextBox/InputButton' don't
become to many.
But I had one more idea and I want to share it with you.
If you don't like my usage of lists as a pointer to variables, one could
replace this in two steps:
1) Adding a new method 'get_text' to get the actual label text
(def get_text(self):
return self.label.get_text() )
2) In the example one would include a function to set one's variable to the
evaluated label-text. Than one would add this function into the
self.observers and so call it after every finished typing mode.
This new behaviour has the big advance that error-handling during evaluation
of the text is a task for users and not to mpl.
I hope I could explain my idea ...
best regards,
Matthias
On Wednesday 27 June 2007 18:19, Matthias Michler wrote:
> Hello everybody,
>
> in my last version I forgot to include a very useful function (it is
> comparable with the 'Button.on_clicked' function). I added it now. It
> allows the user to interact with other widgets ( I needed it to interact
> with the Silder) or his own program (e.g. updating external values or
> plots).
>
> I attached this new version.
>
> best regards,
> Matthias
>
> On Tuesday 26 June 2007 19:46, Matthias Michler wrote:
> > Hello John,
> > Hello all,
> >
> > I thought once more about the textbox and added some of your (Johns)
> > features to my class 'InputButton'. Probably my solution isn't the best
> > possible, but I attached this version to express what I'm thinking of and
> > to see what others think about my solution and needed skills of the
> > textbox .
> >
> > Could this be helpful / useful for others?
> >
> > best regards,
> > Matthias
> >
> > On Wednesday 06 June 2007 17:25, John Hunter wrote:
> > > On 6/6/07, Matthias Michler <[EMAIL PROTECTED]> wrote:
> > > > By the way: What do you think about the "insert a 'l' or 'g' into
> > > > your TextBox and get a grid or log-scale"-issue? Is there a
> > > > possibility to switch the mpl-meaning of 'l', 'g' and 'f' off?
> > >
> > > Yes, this is clearly an issue that has to be dealt with in a cleanup.
> > > The current implementation has no concept of whether the text box is
> > > the active widget. We would need to do something like activate the
> > > text box when you click on it (and figure out the right cursor
> > > location based on the click if there is already text in there) and
> > > deactivate it on a carriage return or click in another axes. The
> > > current implementation was only a proof of concept.
> > >
> > > JDH
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users
