20,741
edits
Howto:Processing legacy PUI dialogs using Canvas: Difference between revisions
Jump to navigation
Jump to search
Howto:Processing legacy PUI dialogs using Canvas (view source)
Revision as of 10:59, 26 February 2017
, 26 February 2017no edit summary
No edit summary |
|||
| Line 42: | Line 42: | ||
}}</ref> | }}</ref> | ||
While most people seem to agree PUI needs to be replaced, it sounds as if the fallout from doing [using Qt5] | While most people seem to agree PUI needs to be replaced, it sounds as if the fallout from doing so [using Qt5] would be more painful (cumulatively) than the pain its existence causes.<ref>{{cite web | ||
|url = https://sourceforge.net/p/flightgear/mailman/message/35623408/ | |url = https://sourceforge.net/p/flightgear/mailman/message/35623408/ | ||
|title = <nowiki> Re: [Flightgear-devel] canvas non svg-elements broken </nowiki> | |title = <nowiki> Re: [Flightgear-devel] canvas non svg-elements broken </nowiki> | ||
| Line 60: | Line 60: | ||
}}</ref> | }}</ref> | ||
If you plan a solution to a problem, but it might get ready in two years (or not), we still may want/need something now. So | If you plan a solution to a problem, but it might get ready in two years (or not), we still may want/need something now. So could create some quick hack filling the gap with the expectation that the hack gets replaced once a proper solution is there <ref>{{cite web | ||
|url = https://sourceforge.net/p/flightgear/mailman/message/35631515/ | |url = https://sourceforge.net/p/flightgear/mailman/message/35631515/ | ||
|title = <nowiki> Re: [Flightgear-devel] Fwd: Canvas-svg parsing breakage </nowiki> | |title = <nowiki> Re: [Flightgear-devel] Fwd: Canvas-svg parsing breakage </nowiki> | ||