20,741
edits
Tooltips: Difference between revisions
Jump to navigation
Jump to search
→Known Issues
m (→Known Issues) |
|||
| Line 51: | Line 51: | ||
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 far as we can tell, it's working for some OS, including OSG 3.4 (OSG 3.4 compiled against libpng16 seems fine<ref>{{cite web | ||
|url = https://sourceforge.net/p/flightgear/mailman/message/35127885/ | |||
|title = <nowiki> Re: [Flightgear-devel] Pop up messages unreadable </nowiki> | |||
|author = <nowiki> jasin colegrove </nowiki> | |||
|date = May 31st, 2016 | |||
|added = May 31st, 2016 | |||
|script_version = 0.40 | |||
}}</ref> | |||
): 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. | 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. | ||