20,741
edits
Tooltips: Difference between revisions
Jump to navigation
Jump to search
m
→Known Issues
m (→Known Issues) |
|||
| Line 49: | Line 49: | ||
To see if that applies here, it would make sense to try an arbitrary canvas/image snippet in conjunction with a png image: http://wiki.flightgear.org/Canvas_Snippets#Adding_Raster_Images | To see if that applies here, it would make sense to try an arbitrary canvas/image snippet in conjunction with a png image: http://wiki.flightgear.org/Canvas_Snippets#Adding_Raster_Images | ||
As far as we can tell, it's working for some OS, including OSG 3.4: that's actually very good news, because it must be a system specific thing, which kinda makes the whole libpng suspicion even more likely - presumably, it is png loading that fails then for people who don't get to see a proper tooltip, at which point the heuristics mentioned above (running a Canvas snippet showing a PNG from the base package) should be simple to verify if this is right or wrong, which is a good thing. | |||
As a matter of fact, this may be distro-specific, we've previously seen incidents where png support was optional, i.e. not included in the binary version of OSG, so that the corresponding driver/library could not load the png plugin. | |||
the log file, conjunction with --log-level=bulk, may show additional information - alternatively, people can refer to the property browser to see if the Canvas image elements in the tooltip window is showing an error in the status-msg property. | |||
If that's indeed the case, we really ought to fix up cmakelists.txt to specifically check for libpng built into osg, because that's not the first time this is happening - at the very least, we should add a startup check and a console error, and probably expose the whole thing as a property to show it in the help/about dialog (link) | If that's indeed the case, we really ought to fix up cmakelists.txt to specifically check for libpng built into osg, because that's not the first time this is happening - at the very least, we should add a startup check and a console error, and probably expose the whole thing as a property to show it in the help/about dialog (link) | ||