Open GoogleCodeExporter opened 9 years ago
I've just tried to use the portable version of old Google Chrome 27 and MacType
works well there. I guess the problem is in the current version of Google
Chrome. Could you actualize your software for the latest versions of Chrome?
Original comment by route...@gmail.com
on 29 Aug 2014 at 9:18
Screenshot of current font
Original comment by route...@gmail.com
on 29 Aug 2014 at 9:37
Attachments:
ENABLE #disable-direct-write FLAG helped! ISSUE RESOLVED!
Original comment by route...@gmail.com
on 29 Aug 2014 at 10:08
Attachments:
The same problem seems to be happening again. Now with chrome version
37.0.2062.124 m.
Disabling Direct write doesn't fix it for me anymore.
Original comment by robison....@gmail.com
on 30 Sep 2014 at 3:53
[deleted comment]
I've just checked my Google Chrome version:
"Version 37.0.2062.124 m
Google Chrome is up to date."
Notice that I'm using a Registry Mode of MacType now and I have no problems.
Perhaps, you should try playing with that flag I showed. I would have tried
something like this:
- enable flag => restart browser => check what happens.
then
- disable flag => restart browser => check what happens.
If this will not work, you can also try looking through the list of other flags
and search for possible flags related with "fonts". I'm not sure, but, perhaps,
there's some flag that blocks MacType.
Original comment by route...@gmail.com
on 30 Sep 2014 at 8:30
Hi!
It got back to normal, my eyes are not hurting or bleeding anymore.
Chrome is still at Version 37.0.2062.124 m, and Disable DirectWrite is enabled
(as it was before the problem appeared).
All MacType Chrome processes are "Running".
The problem appeared after I updated and relaunched chrome.
It was solved after disabling and enabling again the flag, restarting chrome,
restarting everything else which could be interfering with it, and restarting
the computer.
It was probably the PC restart that solved it though.
Original comment by robison....@gmail.com
on 1 Oct 2014 at 3:03
It's great to hear that. Congrats!
Original comment by route...@gmail.com
on 1 Oct 2014 at 3:10
I believe restarting chrome after disabling direct write is the solution
Original comment by vascomat...@gmail.com
on 26 Nov 2014 at 12:01
After update 40, refer here:
https://code.google.com/p/mactype/issues/detail?id=130&start=100
Original comment by alphapan...@gmail.com
on 6 Mar 2015 at 6:16
@alpha, thanks for the reference, it helped!
Original comment by route...@gmail.com
on 9 Mar 2015 at 11:44
Original issue reported on code.google.com by
route...@gmail.com
on 29 Aug 2014 at 9:15Attachments: