Well, non-printable characters are supposed to be translated into readable text by the interpreter. I am not quite sure, why this does not happen in this particular case.
I see a lot of cases of "Alt+" and "Shift+" in the qpdf menus - with nothing following the plus sign. When switching BOOPSI menus off, only the modifier key is shown.
Well, non-printable characters are supposed to be translated into readable text by the interpreter. I am not quite sure, why this does not happen in this particular case.
I see a lot of cases of "Alt+" and "Shift+" in the qpdf menus - with nothing following the plus sign. When switching BOOPSI menus off, only the modifier key is shown.
There is something funny about qpdfview menus.
I was going to check this out myself, but I can't even get qpdfview to load any more.
That is a possibility. It works here, though. Does it give output or no?? If it uses 'single app' structure, it can be a problem with the tcp/ip stack. Just reboot, and all should be ok.
Hmm... My best guess is still, that is has something to do with the SingleApp localhost connection. It will always load all the basic components, but if it reaches main() and thinks, that another instance is running, it will stop execution at that point and never show the user interface.
Have you checked, if the app shuts down properly? You can see, if the process disappears from the process list in Ranger.
Can you maybe build a version with no SingleApp handling?? Usually there is an alternative main() function, that can easily be enabled or some other easy way of turning on SingleApp checking.
OK, just tried again and it is loading, it's just taking forever. Maybe something to do with fonts? I enabled the native fonts to try and stop that but maybe it's still doing the fontconfig stuff?
Anyway, it loads but I'm now not getting the Amiga key in any of the menus, open is just "O" and there are instances of "Alt+". It was OK previously. I'm very very confused. All I have knowingly done is disabled and then re-enabled native menus.
Where are the latest Qt includes? I'll try building the latest version of qpdfview over the weekend, if I can remember how to do it.
The latest includes are in the 'examples and docs' archive. I think the version number is 0.9.3, but it is not different from 0.9.4.
Sounds strange. I could try and reenable the fontconfig window, so you can check if that is the issue. Have you tried deleting the fontconfig cache file? I think, it is somewhere in your sys: partition.
I think your change of setting and the beginning of your probelms is a coincidence. Native fonts only loads AmigaOS fonts and displays them - nothing else is changed.