lmi
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [lmi] PreviewFrameEx questions


From: Greg Chicares
Subject: Re: [lmi] PreviewFrameEx questions
Date: Wed, 27 Jul 2022 21:10:53 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.8.0

On 5/19/22 15:13, Vadim Zeitlin wrote:
[...]
>  Please let me know what, if anything, should I do about these 2 problems
> (and IMO both of them are actual UI problems, especially the first one,
> even if the only reason I noticed them was due to looking for the "WX !!"
> comments in the code).

I really don't want to touch this code.

I don't use "print preview" myself, and I'm not even sure I can.
IIRC, this facility uses a mime-type to figure out how to display
a preview. My chroots have no pdf viewer; my "host" system does,
but not the chroots. Thus, when I try "File | Print preview", I see:

0048:fixme:imm:ImeSetActiveContext (0x257fd0, 0): stub
0048:fixme:imm:ImmReleaseContext (0000000000010020, 0000000000257FD0): stub
0024:fixme:imm:ImeSetActiveContext (0x269f40, 1): stub
0024:fixme:imm:ImmReleaseContext (0000000000010056, 0000000000269F40): stub
0024:fixme:shell:IQueryAssociations_fnGetString assocstr 7 unimplemented!
In file /opt/lmi/src/lmi/third_party/wx/src/msw/mimetype.cpp at line 287: 
'AssocQueryString' failed with error 0x80004001 (Not implemented.).
0024:fixme:shell:IQueryAssociations_fnGetString assocstr 10 unimplemented!
In file /opt/lmi/src/lmi/third_party/wx/src/msw/mimetype.cpp at line 287: 
'AssocQueryString' failed with error 0x80004001 (Not implemented.).
00fc:err:winebrowser:launch_app could not find a suitable app to open 
L"file:///opt/lmi/print/unnamed1.pdf"

I don't really want "winebrowser" to launch any applications.
My chroots seem to have no "associations" for GTK either:

Alarum: Unable to determine command to 'open' file 
'/opt/lmi/print/unnamed1.pdf'.
[file_command_wx.cpp : 95]

And I'm not sure whether end users ever use this facility. IIRC, a few
years ago they even had difficulties with "File | Print", due to the
way their employer set "associations" in the msw registry; I remember
identifying an incorrect corporate setting and asking it to be fixed,
with the predictable corporate lack of response. I just tell people to
use "File | Print to PDF", because that's under our control and always
works; then, once they have a PDF file, if they can't view it or print
it, that's not an lmi problem--it's an msw problem, and one that the
corporation actually will fix.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]