http://bugs.winehq.org/show_bug.cgi?id=3904
Summary: Difficulty to use wine within automated tools Product: Wine Version: 0.9.1. Platform: Other URL: http://www.office2pdf.lll.lu OS/Version: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-binary AssignedTo: wine-bugs@winehq.org ReportedBy: wine@wine.lka.org.lu
Up until wine-20041201-0.1, wine used to include button labels in the X properties of its windows. For instance, an OK button would be recognizable by its name "OK" in the xwininfo -root -tree output.
This was handy for tools that automatically drive windows applications running within wine. No need to do any bitmap matching, just looking at the button labels via xwininfo was enough.
However, recent wine version use empty names for almost all its windows.
Another annoying thing is that between each version, keyboard shortcuts or tabbing order within the various dialog boxes (such as print) are shuffled around, which makes it necessary to change office2pdf whenever a new wine version comes out (or alternatively: to recommend a really old version...).
Would it be possible to stick to some consistency here?