| | [ Return to Bugs & Features | Roadmap 2.0 | Post Text | Post File | SVN ⇄ GIT ]
STR #2010
| Application: | FLTK Library |
| Status: | 5 - New |
| Priority: | 1 - Request for Enhancement, e.g. asking for a feature |
| Scope: | 3 - Applies to all machines and operating systems |
| Subsystem: | Unassigned |
| Summary: | need copy_tooltip |
| Version: | 2.0-feature |
| Created By: | bnolsen |
| Assigned To: | Unassigned |
| Fix Version: | Unassigned |
| Update Notification: | |
Trouble Report Files:
[ Post File ]
Trouble Report Comments:
[ Post Text ]
| |
| #1 | bnolsen 18:33 Jul 18, 2008 |
| I'd like to be able to use dynamic tooltips, ie, change them on the fly based on the data being shown (specially in an elided header in a browser).
I added copy_tooltip in the same way that copy_label is implemented.
HOWEVER that means another flag() value is burned which could cause all kinds of trouble. | |
| |
| #2 | matt 13:21 Jul 19, 2008 |
| A better way to do this is to send a message to the widget before the toolti[p is shown. This avoids having to set the tooltip text over an over again. This should be part of the tooltip source file. | |
| |
| #3 | bnolsen 21:41 Jul 23, 2008 |
| I'm not exactly sure what you mean by this. I'm creating a widget then "building" the tooltip. I *could* keep around an array of char* in my application and manually delete them but I shouldn't have to do that. As mentioned this tooltip is for elided text...meains the widget itself is too small to display the full text so it displays a subset of the contents and the tooltip shows the real contents. | |
| |
| #4 | matt 23:28 Jul 23, 2008 |
| OK, I explained this badly. There are two issues: 1, making a tooltip copy the string, so you don't have to keep track of it is nice. But it is also not very diffigult to query the current tooltip, free it, then create a new tooltip. Not a big deal though.
The second issue is a problem that can arise if you continously change tooltips around. It is time consuming and may fragment memory by constantly allocating and deallocating memory, just in case the user may need a tooltip. It would be neat to get a TOOLTIP event just before an actual tooltip would be displayed, so I can allocate a ew string just once, when it is actually shown. | |
| |
| #5 | greg.ercolano 00:47 Dec 02, 2010 |
| Devs: this STR is similar to #1944. http://fltk.org/str.php?L1944 | |
| |
| #6 | greg.ercolano 01:00 Dec 02, 2010 |
| Side note: I'm making similar changes to 1.3, and was just perusing this STR for reference, since its similar.
2.x Devs: note in OP's patch, copy_tooltip() docs still refer to 'label()' and 'copy_label()'; be sure to correct. Also, note patch introduces unusual indenting in the flags definition. Check carefully when applying. | |
[ Return to Bugs & Features | Post Text | Post File ]
|
| |