An update, for anyone in the future who encounters this issue: having upgraded to macOS Mojave, the problem’s resolved itself. On Oct 16, 2018, 12:20 PM -0500, Drake Thomas <[email protected]>, wrote: > Hi Dan! > > I inserted exactly those lines into Info.plist on Mnemosyne 2.6.1, and I > didn’t see any change in resolution; attached is the Info.plist file my copy > of Mnemosyne 2.6.1 is currently using. (I’ve also got the old application > version on my desktop, since the upgrade didn’t replace it, but since the > display issue was present prior to upgrading I would be surprised if that had > any effect). > On Oct 16, 2018, 8:00 AM -0500, Dan Schmidt <[email protected]>, wrote: > > That's /Applications/Mnemosyne.app/Contents/Info.plist, of course. > > > > On Tuesday, October 16, 2018 at 8:59:27 AM UTC-4, Dan Schmidt wrote: > > > I just checked in on the mailing list for the first time in a while and > > > saw this thread. For what it's worth: > > > - I agree that your screenshot is blurry! > > > - On my MacBook Pro, High Sierra 10.13.6, Mnemosyne 2.6.1, adding the > > > following four lines at the end of the body of the <dict> tag in > > > /Applications/Mnemosyne.app/Contents/ produced crisp output for me: > > > > > > <key>NSPrincipalClass</key> > > > <string>NSApplication</string> > > > <key>NSHighResolutionCapable</key> > > > <string>True</string> > > > > > > I realize that you probably already tried this, but maybe you did > > > something slightly different, and in any case it's useful to have another > > > data point. > > > > > > Dan > > > > > > On Sunday, September 9, 2018 at 10:34:09 PM UTC-4, Drake Thomas wrote: > > > > Hi Devin, > > > > > > > > I added the lines in that link to the Info.plist file, saved, quit > > > > Mnemosyne, and reopened, and didn’t see any change. > > > > > > > > (I was worried that maybe I wasn’t seeing any change because I hadn’t > > > > done a hard enough reset for the contents of Info.plist to be > > > > rechecked, so I also tried saving Info.plist as a blank text file. This > > > > made Mnemosyne stop working, so it seems that changes I made to the > > > > file were in fact being propagated to the application - they just > > > > didn’t affect the display.) > > -- > > You received this message because you are subscribed to a topic in the > > Google Groups "mnemosyne-proj-users" group. > > To unsubscribe from this topic, visit > > https://groups.google.com/d/topic/mnemosyne-proj-users/Wn8AUtnjbH8/unsubscribe. > > To unsubscribe from this group and all its topics, send an email to > > [email protected]. > > To post to this group, send email to [email protected]. > > To view this discussion on the web visit > > https://groups.google.com/d/msgid/mnemosyne-proj-users/3749e0cb-bee7-4d2d-ba6f-e38e4efe14e8%40googlegroups.com. > > For more options, visit https://groups.google.com/d/optout.
-- You received this message because you are subscribed to the Google Groups "mnemosyne-proj-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/mnemosyne-proj-users/4b6e71f4-69a4-41f5-b927-f285bc2faa72%40Spark. For more options, visit https://groups.google.com/d/optout.
