I have a problem with my Photoshop version 13.0.1 x32. When I load something, it looks like that (it's fullscreen mode).
I don't know what to do. I tried reinstalling and updating, but nothing helped. It's Windows 10 x64, so could that be a problem? I also tried it on another machine also Windows 10 x64 and it works fine.
Another problem is that when Photoshop is in windowed mode, it loads images correctly, but the tool panel disappears.
Any suggestions on what to do?
Thanks for any answers.
Intermittently, while programming using Qt Creator, the Qt Creator interface appears with garantuan, unusably huge fonts for the text in toolbars and other elements.
I am attaching a screenshot.
This issue only happens intermittently, but I cannot find any hint of this problem when searching via Google, and I cannot understand why it is happening or what to do about it.
I am using a high-resolution monitor (4K, 2160 x 3840) with Windows 10; the Windows setting for "Change the size of text, apps, and other items" is set to 100% in the Settings - and I have not noticed any other applications with this problem (except perhaps once or twice in the past and I think the application must have been built with Qt - but I do not remember).
How do I resolve the issue of Qt Creator displaying gargantuan fonts in various elements of its user interface?
Edit: The issue is even more severe than I thought. Now, the application I am building in Qt has the same problem. Here is a screenshot:
What is going on here? Obviously, although the problem is intermittent for me, I am concerned that my client might suddenly have the problem appear.
I do not think the solution is for me to set the font size for my widgets with a stylesheet. Usually, this problem does not occur, and I am think this is a bug with Qt - not with my code.
What can I do to prevent this?
I have IntelliJ IDEA on my PC for java programming language.
There is a font (Consolas) and I want to make it looks like Mac font but I don't know how
My font
Mac OS X font (I want the same)
I believe this issue occurs due to Windows rendering truetype differently and not up to the standard of Linux and Mac OS X.
Take a look at these 2 applications to adjust your fonts in Windows it should make a difference - http://www.askvg.com/how-to-get-mac-os-or-linux-style-font-smoothing-in-windows/
You can also change the Anti-aliasing settings within IntelliJ IDE.
http://hivelogic.com/articles/top-10-programming-fonts/ Lists the top 10 programming fonts - Inconsolata would be a font that would give a similar feel to Mac OS X/Linux.
i recently installed fresh win 7 pro OS on brand new DELL i5 desktop machine. while trying to use word 2013, i noticed that text written in Monotype Hadassah font is displayed using Times new roman font.
is anybody noticed such an issue?
thanks.
after some experiments:
the fonts works OK in notepad - which means that probably the problem is in office 2013 and not in the OS itself.
since the font is registered as restricted with respect to the "embedding" ability i thought that it may be due to this restriction, but nevertheless, removing the restriction ( i recommend on TTFPatch utility didn't change the behaviour.
interestingly, i found that saving the document as PDF resulted in correct rendering of the
font - which is pretty satisfactory to me.
I prefer google chrome in almost every way above IE10, but one thing I hate is that fonts just look much better in IE10. This especially visible with small math fonts. They look like pdf quality in IE10.
After searching a little bit, I found out that this is because IE10 use DirectWrite in windows 7/8 for font rendering. I was searching if chrome will support this in the future and I found this information:
Apr 24, 2013:
An update for everyone that's watching this one:
Our Windows font rendering is actively being worked on. Basic support
for DirectWrite is now in Skia (to update from comment #13). At the
same time, GDI was very deeply embedded in the Windows WebKit port and
is still being rooted out. We hope to have something within a
milestone or two that developers can start playing with. How fast it
goes to stable is, as always, all about how fast we can root out and
burn down any regressions.
We'll update the thread here when it's available behind a runtime flag
for y'all to try out.
Oct 8, 2013
The following revision refers to this bug:
http://src.chromium.org/viewvc/blink?view=rev&rev=159071
Changed paths: M http://src.chromium.org/viewvc/blink/trunk/Source/core/platform/graphics/skia/FontCacheSkiaWin.cpp?r1=159071&r2=159070&pathrev=159071
M
http://src.chromium.org/viewvc/blink/trunk/Source/core/page/RuntimeEnabledFeatures.in?r1=159071&r2=159070&pathrev=159071
Add runtime flag for using DirectWrite on windows
Add runtime enabled feature for using the DirectWrite skia backend on
windows.
BUG=25541 R=bungeman#chromium.org, eseidel#chromium.org
Review URL: https://codereview.chromium.org/26335002
I don't even know what a runtime flag is, but this sounds to me that it may be possible to somehow enable directwrite in chrome. Is this true ? Or should I wait a little longer before I can use directwrite font rendering in chrome ?
Sadly not yet (as of 2013-10-31, no Chromium channels supports this feature out-of-the-box).
If you look at the latest RuntimeEnabledFeatures.in, DirectWrite doesn't have any status assigned to it. According to Blink document, users cannot enable a feature via about:flags unless status=experimental is assigned.
But hopefully soon, so windows users may have a better time with web fonts :)
Update 2013-11-16: with latest issue 25541 comment, it seems we are very close to be able to enable DirectWrite in Canary.
Update 2014-01-04: Canary build now has a command line switch that can enable DirectWrite font rendering, but disabling sandbox mode are required (not safe for everyday browsing). There are also a few font rendering problem associate with it. Hopefully they can get them fixed and add this feature to about:flags soon.
Update 2014-05-09: latest Canary build (m36) now has proper support for DirectWrite within sandbox mode (implemented via issue 333029), which means developers can enable DW directly by going to about:flags#enable-direct-write. As for consumers, Google is targeting release on m37.
Update 2014-08-09: Chrome 37 beta enables DirectWrite by default, expect Chrome 37 official release to have it by default as well.
Update 2014-08-31: Chrome 37 stable release has DirectWrite enabled by default! Just note that users can still turn it off at about:flags (some of them use MacType instead).
Chrome 35 (beta) comes with an option to enable DirectWrite for Windows font rendering. Paste the following command in your address bar and click enable:
chrome://flags/#enable-direct-write
Reference: http://www.reddit.com/r/web_design/comments/22q9r9/chrome_35_beta_has_finally_fixed_windows_font/
It's currently in development for chrome on windows.
http://www.chromestatus.com/features/4725550652325888
Update: on August 26, 2014, Google updated the stable version of their Chrome browser to version 37.0.2062.94 on Windows, OS X, and Linux. With this release, Chrome move from Microsoft's Graphics Device Interface rendering method to Microsoft's DirectWrite text rendering API. Switching to DirectWrite has been requested for years by users on Windows, and Google has stated that it took significant rewriting of their font rendering engine which is why it has taken so long.
It's in Chrome as a flag as of 33 (and as of this time of writing), however from what I understand you still need to run it with the sandbox disabled via the command line --no-sandbox. This is not a recommended action for everyday use. You can enable the rendering flag, but it will only change if sandboxing is disabled.
(I would have added this as a comment to #chickenbooze, but I've switched SE accounts and don't have enough reputation yet :)