----- Original Message -----
From: Jonathan Wilkes jancsika@yahoo.com To: "pd-list@iem.at" pd-list@iem.at Cc: Sent: Wednesday, February 27, 2013 3:42 PM Subject: [PD] tooltip rfc
Ok, I have a plan to revise the tooltips that are in pd-ext 0.43
[...]
----- Original Message -----
From: Ivica Ico Bukvic ico@vt.edu To: Jonathan Wilkes jancsika@yahoo.com Cc: Sent: Wednesday, February 27, 2013 4:46 PM Subject: Re: [PD] cxc library
[...]
tooltips in pd-l2ork already differentiate between the dynamic (floating) ones and static/manual ones that appear in the bottom-left corner. What is not clear whether both of them can coexist (I think currently they cannot).
Just to clarify, I'm proposing to separate them completely. So there would be "autotips" in edit-mode that follow the mouse and that the user can only turn on or off[1]. There would additionally be a "canvas tip" which the user can already write to using the "tip" method (which could be renamed if that causes confusion).
As far as the canvas tips, I'm thinking just use the current syntax for the current behavior: tip 1 foo <-- show "foo" in canvas tip tip 0 <-- hide canvas tip
Then external objects that want to show a canvas tip can call pdtk_tip (or whatever it's named) directly for stuff like text appearing on entering the object with the mouse then going away when leaving the object. The only change would be that when the external wants to remove the text it wrote to the tip, I think the canvas tip widget should return to the state the user had it in previously. So if the canvas receives the message "tip 1 Hello world!", and then someone mouses over a pddplink that shows the tip "http://puredata.info", when the mouse leaves the pddplink it should return to "Hello world!". But that's pretty easy to do through.