Indesign interface screen resolution

I just switched from indesign CC to (2014). When I opened it up, the resolution on the interface sucked, it's really poor. How do i adjust this? Note, the resolution on the files are perfect, it's just the resolution of the interface. See below to compare screenshots of my photoshop vs my indesign...
It may not seem so obnoxious reduced to 400 px wide, but blow it up to about eight times that size and it looks like I'm using 1280x720 instead of 1920x1080. I can't seem to find a place to adjust the resolution of the interface, no other programs are bad, just this one... any thoughts?

I don't mean to be a stickler here, it did fix indesign, but made everything on my computer (besides other adobe programs, ie photoshop is still correct) much smaller. This issue has not existed with previous indesign updates, this is the first I've experienced it. any way to get the rest of my computer back to how it was without affecting indesign?

Similar Messages

Please help. My Adobe InDesign document keeps crashing when I adjust the screen resolution to High in the View menu. Desperately trying to get my magazines prepared for press today! HELP!

Please help. My Adobe InDesign document keeps crashing when I adjust the screen resolution to High in the View menu. Desperately trying to get my magazines prepared for press today! HELP!
My magazine last month is still working ok - but this month's version has just started crashing for some reason.

We can't know. You have not provided any system info, not told us what version of ID you use nor provided any specifics about the document like images, color profiles, fonts, paragraph styles and what have you...
Mylenium

Yoga 2 Pro REAL Screen Resolution

SECOND THREAD on this HERE.
I've just discovered that the Yoga 2 Pro seems to be fudging its screen resolution claim. I wouldn't care, except ... it actually has become a small problem ... and one that I presume will get bigger over time
The Y2P has a "3200x1800" screen. It's beautiful. And in most regards its also overkill, since there's no such thing as 3200x1800 content, AND because it cause some issues with size of things on the screen. For this reason, and because pushing fewer pixels will tend to improve battery life, I run my Y2P at 1920x1080, or "normal full HD" resolution.
I recently tried to log into an on-line app I use, as was greeted with a strange error message:
Well, since I'm running 1920x1080 and using a current version of the Chrome browswer, none of that made sense. I tried Internet Explorer as well ... no luck.
I installed Speccy, a tool to check things out inside a computer, and when I got to the display settings, here's what I found:
That's right; I'm "set to 1920x1080", but something is seeing that the REAL resolution is 1280x720. Oh, and elsewhere in Speccy I found that the Y2P is reporting itself as a tablet rather than as a computer ... which probably isn't the issue here, but still unsettling.
So I changed the resolution to 3200x1800. Good news: I was able to get to the web app I need. BAD NEWS: The real resolution appears to be 1600x900:
I called Lnove tech support and got a representative who tells me that this is a Windows 8.1 problem; Windows 8.1 cannot support resolutions higher than 1920x1080, so even though the actual hardware resolution of the Y2P is 3200x1800, it needs to scale itself so Windows doesn't cry. This appears to be false (http://blogs.msdn.com/b/b8/archive/2012/03/21/scaling-to-different-screens.aspx), but I don't really know.
As such, my conclusion is that the representative told me something that was actually the opposite of correct, with correct SEEMING to be that the maximum REAL resolution of the Y2P hardware is in fact 1600x900, with Lenovo's claim of a 3200x1800 resolution being a software/upscaling/interpolation trick.
If that's so, it's really distressing, because it would appear to be a lie about hardware capabilities.
I didn't start out caring about that, although obviously as this point I feel like I've uncovered a smoking gun and would like an answer from Lenovo. But at the end of the day, since I don't need or want that 3200x1800 for the reasons I explained at the top of this post, I just want to know the truth—whatever it is— and to know how to get Windows to report the same resolution to "the world" that it's reporting to me, the user.
And I guess I wouldn't mind knowing why the scaling between real and interpolation is different depending on the settings one selects, too (do the math).
Anyone know anything conclusive? And even better, anyone from Lenovo have an ideas what the truth is here?

I don't know if any of these settings (resolution and/or item sizing) affects battery duration. But you could do a battery test: set it to one mode with full battery charge and then leave it on unused until the battery is 50%. Check how long that took. Repeat for the other mode and compare the time difference if any.
As to why there are these two layers of settings I think this is the answer: Windows metro apps and some Windows desktop application and the new elements in Windows 8 (the new start screen, the charms bar and all metro apps) have smart scaling of user interface elements (text, buttons and so on) designed to support very high resolution screens like ours. So buttons and text in such programs will adapt in size to fit the resolution. But older desktop applications, including the Windows 8.1 desktop taskbar and its icons it seems, does not do such smart scaling. So running them full resolution mean that everything is really tiny. To work around that everything can be scaled up to 200% (or 150% or 125%). I suspect that future versions of Windows or some Windows update may improve these things since the settings and the button descriptions in the settings aren't very user friendly.
But I'm not sure about this. I hope someone in the know jumps in this thread and gives more details.
It is a pity that Lenovo doesn't provide new Yoga 2 Pro users with a user friendly guide with information and tips on good ways to deal with resolutions and these scaling settings.

Screen resolution in Lightroom 4 on Lenovo windows 8

How can I increase the resolution so I can read the text

Hi Jim
Think Young, but it is already "large"
The text is so small that to Read need a magnifying glass to Read the text
The program is useless at present
Sendt fra min iPad
Den 07/04/2014 kl. 18.32 skrev Jim Wilde <[email protected]>:
Re: Screen resolution in Lightroom 4 on Lenovo windows 8
created by Jim Wilde in Photoshop Lightroom - View the full discussion
JIm, you can make the text larger....look at the Interface Tab on the Preferences menu and you'll see several different Font size options (although there are less on OSX apparently). Make a selection, then close and restart Lightroom for the change to take effect.
http://forums.adobe.com/servlet/JiveServlet/downloadImage/2-6278230-626541/450-184/Untitle d.png
Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/6278230#6278230
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/6278230#6278230
To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/6278230#6278230. In the Actions box on the right, click the Stop Email Notifications link.
Start a new discussion in Photoshop Lightroom at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/thread/416458?tstart=0.

1280x800 screen resolution is missing...

Hello. I just purchased a Mac Mini, and I'm using it without a monitor attached. Instead, we use it as a media server in our house, and we access it using a remote connection (Chicken of the VLC).
Unfortunately, I cannot get the Mac Mini's screen size to match my Macbook Pro, which is requiring painfully annoying scrolling in the virtual window. I can't change the Mac Mini's screen resolution to 1280x800, because that option is not available. How can I add that resolution to the list of possible options without a physical monitor attached?
I've looked at DisplayConfigX and SwitchResX but neither will do the trick without a monitor attached. Anyone have any ideas?

Unfortunately I am pretty certain that the resolution list used for headless configurations resides in firmware somewhere, not a normal file in the OS X file system. As such, it can't be written to with programs like DCX and SRX. This question comes up occasionally on this forum and I have never seen a good answer for it.
All you really need is for the mini to see a valid display ID. That can be done with something like a DVI Detective from Gefen, but that's an expensive way to go. I you have an old, broken monitor, you could rip out the interface board and hang it off the mini's video port. With many such boards the EDID circuit block will take power from the auxiliary power pin on the video cable so the board wouldn't need a power supply of its own in order to power up the EDID and comm channel. That's also a heavy hammer solution but could be cheaper if you can get a broken monitor for free somewhere.

Changing screen resolution with a button

Hi,
I would like to ask if there is a way for an interface to change the screen resolution of the computer? I am wanting to build an interface that loads an interactive camera that works with processing however I am needing it to be at the resolution 800*900 as the webcam screen is too small on a full 1680x1050 resolution.
Is there a way for the flash application to change the screen resolution with a button click? Are there any alternatives to this?
Thank you
Jess

It is to display a portfolio at my design school for assessment, they will accomodate any necessary things that i may need for assessment viewing so it is very important to me.
Do you know what programs will work with this? What program would i have to install?
I only need to do this for my assessment so it is almost a desperate search for something that would work.

Why Does The Display Cable Length Change Screen Resolution?

I have a Power Mac running two 23" Samsung Displays using 6' cables. This has worked fine for 3 years. Recentily I tried to use 15' cables, but it changes the resolution of the displays. The resolutions are not even the same.
Any ideas on this? The 1st image shows the screen resolutions with the shorter cables. The 2nd image shows the resolutions with the longer cables.
Thanks!

Do not use the menuBar item for debugging. It shows only "greatest hits". The full range you can select from will be shown in:
System Preferences > Displays
The DVI connector on the computer outputs a "regular" VGA signal in the blade at the end and the four pins around it, plus H-Sync (which is in the top row of the grid next to them). Its "adapter" just swaps the signals around.
The Mini DisplayPort adapter asserts a signal to the Mini DisplayPort which requests VGA-compatibility mode, and the interface produces an approximation of VGA.

Screen Resolution for CS4 apps?

I'm finding my 22" screen distorts my files. What are some tips for the best screen resolution for the following:
PhotoShop
Illustrator
InDesign
Dreamweaver
This is Windows XP Pro.
Thanks for your help.

LCD panels must be used at their native resolution. Whatever it is for you monitor is what you must set it to.
Bob

High screen resolution problems

Hi.
Just bought a Dell XPS lapptop with screen resolution 3200x1800 and windows 8.1. After installing photoshop CS6 the program interface, menus and icons are extremly smal and almost impossible to see. That also happens in Bridge but not in Lightroom. Thankfull for your help. Best regards/janis lukas

Ideally For a Image editor you want a high resolution display so you can edit your images at a high resolution near or actual print quality. And the editor should have a UI that is easy to see and use. That is what CC 2014 2x UI is all about.   You can can have an OS like Windows scale your display image effectively run you display at a lower resolution so that things display larger. Scaling the display to 1/2 resolution is easy for its and even multiplayer 2x A 200DPI display would be like a 100DPI display with 1/4 the number of pixels. Scaling the display defeats the reason to have a high resolution display. However it may work well for a Application like the bridge. The the bridge only displays previews and thumbnails. It is not what you want for an image editor like Photoshop. You want to be able to use the high resolution for editing.
As I wrote Windows can scale the system display for application to lower resolutions.   Application have that option. Adobe application do not the have windows scale the display so their Applications can take advantage of all the pixels and resolution the display has to offer. However Only Photoshop has a option to scale its UI 2x.
It is possible to have Windows scale the display for an Adobe Application by making a registry update and adding an external manifest file for applications yo want Windows to scale.
I can show you the difference between Adobe CC 2x UI and Windows scaling. CC 2014 2x UI works well on 4K displays that have high resolution. However it does not work well on a Surface Pro 3 Display that has a 216PPI resolution for the display only has 2160 x 1440 Pixels Scaling the UI 2x effectively make the display look like a 108 PPI display with 1080x720 pixels. Which doe not meet Photoshop 1024x768 requirement. Photoshop UI just doesn't fit.
Windows Scaling for the Surface Pro 3 has 4 preset dor scaling the display 150% being the default for the surface pro 3
Microsoft Preset Display scaling
100% 2160x1440   216 PPI
125% 1728x1152   173 PPI
150% 1440x960    144 PPI SP3 Default setting
200% 1080x720    108 PPI
The 150% scaling works well for Photoshop UI however it alsi scala Photoshop image window where CC 2014 2C UI does not. Windows scaling can also be use on other versions of Photoshop and bridge etc. It would be helpful if Photoshop also offered a 1.25x and 1.5x UI. Here are some screen captures I did on my Surface Pro 3 the shows the difference between 2x UI and Display scaling.   CC 2014 Adobe scaling vs Windows scaling.

Will Adobe CS6 work on a laptop with screen resolution of 1366 x 768 pixels?

I'm looking at this laptop -
HP ProBook 15.6-Inch Laptop 2.1 GHz AMD A8-5550M Processor, 8GB DDR3L, 500GB HDD, Windows 7 Professional and a 7200 RPM drive.
All the specs are great except for the screen resolution, which Adobe says should be 1280X900. So I would love to know if CS6 would still work on this laptop.
Thanks for your help!!
Dalevideo

Not only is the screen resolution below minimum requirements, the rest is also very underpowered and slow for CS6.
If CS6 installs, you will not be able to see critical parts of the user interface, making you work in the blind.

Screen resolution reset on wake up

screen resolution reset on wake up
I have a macbook Pro (13 inch, Mid 2010, Processor 2.4 GHz Intel Core 2 Duo, memory 4 GB 1067 MHz DDR3) running Yosemite OS X 10.10.2 (14C1514) connected to a high resolution display (2560x1440 BenQ BL2710) via a MDP2DVID adapter and a dual link DVI cable. Just sometimes (apparently randomly about once in 20 occasions) when I wake up the computer it turns both screens off for a second then turns them on again with the resolution reset to a low level on the built-in screen, and the external display is reduced to a small window in the centre. Sleeping and waking the computer usually brings it back to normal but with many of my open windows resized to a small level.
Does anyone know how this could be corrected?
Thanks
John Nixon

This happened again this morning. Here are the Apple System Log (ASL) Messages at the time:
2015-May-01 11:13:36 kernel[0]: AirPort_Brcm43xx::powerChange: System Wake - Full Wake/ Dark Wake / Maintenance wake
2015-May-01 11:13:36 kernel[0]: RTC: PowerByCalendarDate setting ignored
2015-May-01 11:13:36 kernel[0]: RTC: PowerByCalendarDate setting ignored
2015-May-01 11:13:36 kernel[0]: Previous sleep cause: 5
2015-May-01 11:13:36 kernel[0]: The USB device Apple Internal Keyboard / Trackpad (Port 3 of Hub at 0x6000000) may have caused a wake by issuing a remote wakeup (2)
2015-May-01 11:13:36 kernel[0]: full wake promotion (reason 1) 108 ms
2015-May-01 11:13:36 watchdogd[213]: [watchdog_daemon] @(         pm_callback) - ref=0x0 msg_type=0xe0000320 msg=0x0
2015-May-01 11:13:36 kernel[0]: wlEvent: en1 en1 Link DOWN virtIf = 0
2015-May-01 11:13:36 kernel[0]: AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
2015-May-01 11:13:36 kernel[0]: en1: channel changed to 1
2015-May-01 11:13:36 kernel[0]: en1::IO80211Interface::postMessage bssid changed
2015-May-01 11:13:36 kernel[0]: en1: 802.11d country code set to 'X0'.
2015-May-01 11:13:36 kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 149 153 157 161 165
2015-May-01 11:13:36 kernel[0]: en1: channel changed to 1
2015-May-01 11:13:36 discoveryd[51]: Basic Bonjour,Warn Warning: IPv4 listener multicast send failed en1, 50
2015-May-01 11:13:36 discoveryd[51]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 192.168.1.254 Port 53 errno 50, fd 69, ErrLogCount 1 ResolverIntf:5
2015-May-01 11:13:36 sharingd[277]: 11:13:36.321 : SDStatusMonitor::kStatusWirelessPowerChanged
2015-May-01 11:13:36 discoveryd[51]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 192.168.1.254 Port 53 errno 49, fd 95, ErrLogCount 2 ResolverIntf:5
2015-May-01 11:13:36 discoveryd[51]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 192.168.1.254 Port 53 errno 49, fd 96, ErrLogCount 3 ResolverIntf:5
2015-May-01 11:13:36 discoveryd[51]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 192.168.1.254 Port 53 errno 49, fd 95, ErrLogCount 4 ResolverIntf:5
2015-May-01 11:13:36 discoveryd[51]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 192.168.1.254 Port 53 errno 49, fd 95, ErrLogCount 5 ResolverIntf:5
2015-May-01 11:13:36 discoveryd[51]: Basic DNSResolver UDNS Send(): UDP Sendto() failed to DNSNameServer 192.168.1.254 Port 53 errno 49, fd 95, ErrLogCount 6 ResolverIntf:5
2015-May-01 11:13:36 configd[26]: setting hostname to "John-Nixons-MacBook-Pro.local"
2015-May-01 11:13:36 configd[26]: network changed: v4(en1-:192.168.1.123) DNS- Proxy-
2015-May-01 11:13:36 discoveryd[51]: Basic WABServer NetResolverEvent no resolvers, resetting domains
2015-May-01 11:13:36 UserEventAgent[16]: Captive: CNPluginHandler en1: Inactive
2015-May-01 11:13:36 discoveryd[51]: Basic Warn DD_Warn: Corrupt NSEC RDATA size
2015-May-01 11:13:36 discoveryd[51]: Basic Bonjour,Warn Warning: IPv6 listener multicast send failed en1, 49
2015-May-01 11:13:36 discoveryd[51]: Basic Bonjour,Warn Warning: IPv6 listener multicast send failed en1, 49
2015-May-01 11:13:36 WindowServer[136]: handle_will_sleep_auth_and_shield_windows: NULL shield_window (lock state: 1)
2015-May-01 11:13:36 WindowServer[136]: CGXDisplayDidWakeNotification [346636855129711]: posting kCGSDisplayDidWake
2015-May-01 11:13:36 discoveryd[51]: Basic Bonjour Failed to delete registration recordId=119 error=4
2015-May-01 11:13:37 kernel[0]: en1: 802.11d country code set to 'GB'.
2015-May-01 11:13:37 kernel[0]: en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 12 13 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140
2015-May-01 11:13:37 networkd[141]: +[NETLedBelly stopFastFail] Clearing ledbelly failure cache
2015-May-01 11:13:37 discoveryd[51]: Basic Bonjour,Warn Warning: IPv6 listener multicast send failed en1, 49
2015-May-01 11:13:37 discoveryd[51]: Basic Bonjour,Warn Warning: IPv6 listener multicast send failed en1, 49
2015-May-01 11:13:37 kernel[0]: en1: channel changed to 1
2015-May-01 11:13:37 sharingd[277]: 11:13:37.246 : SDStatusMonitor::kStatusWirelessPowerChanged
2015-May-01 11:13:37 sharingd[277]: 11:13:37.284 : SDStatusMonitor::kStatusWirelessPowerChanged
2015-May-01 11:13:37 kernel[0]: en1: channel changed to 1
2015-May-01 11:13:37 discoveryd[51]: Basic Bonjour,Warn Warning: IPv6 listener multicast send failed en1, 49
2015-May-01 11:13:37 netbiosd[4354]: network_reachability_changed : network is not reachable, netbiosd is shutting down
2015-May-01 11:13:37 discoveryd[51]: Basic Bonjour,Warn Warning: IPv6 listener multicast send failed en1, 49
2015-May-01 11:13:37 kernel[0]: MacAuthEvent en1   Auth result for: 4c:09:d4:15:e8:39 MAC AUTH succeeded
2015-May-01 11:13:37 kernel[0]: wlEvent: en1 en1 Link UP virtIf = 0
2015-May-01 11:13:37 kernel[0]: AirPort: Link Up on en1
2015-May-01 11:13:37 kernel[0]: en1: BSSID changed to 4c:09:d4:15:e8:39
2015-May-01 11:13:37 kernel[0]: en1: channel changed to 48,-1
2015-May-01 11:13:37 kernel[0]: en1::IO80211Interface::postMessage bssid changed
2015-May-01 11:13:37 kernel[0]: AirPort: RSN handshake complete on en1
2015-May-01 11:13:37 configd[26]: network changed: DNS* Proxy
2015-May-01 11:13:37 UserEventAgent[16]: Captive: [CNInfoNetworkActive:1709] en1: SSID 'BTHub4-H2J5' making interface primary (cache indicates network not captive)
2015-May-01 11:13:37 UserEventAgent[16]: Captive: CNPluginHandler en1: Evaluating
2015-May-01 11:13:37 UserEventAgent[16]: Captive: en1: Not probing 'BTHub4-H2J5' (cache indicates not captive)
2015-May-01 11:13:37 configd[26]: network changed: v4(en1!:192.168.1.123) DNS+ Proxy+ SMB
2015-May-01 11:13:37 UserEventAgent[16]: Captive: CNPluginHandler en1: Authenticated
2015-May-01 11:13:37 networkd[141]: +[NETLedBelly stopFastFail] Clearing ledbelly failure cache
2015-May-01 11:13:37 networkd[141]: +[NETLedBelly stopFastFail] Clearing ledbelly failure cache
2015-May-01 11:13:37 kernel[0]: en1: BSSID changed to 4c:09:d4:15:e8:39
2015-May-01 11:13:37 kernel[0]: en1: channel changed to 48,-1
2015-May-01 11:13:37 sharingd[277]: 11:13:37.880 : SDStatusMonitor::kStatusWirelessPowerChanged
2015-May-01 11:13:38 WindowServer[136]: Received display connect changed for display 0x42731c0
2015-May-01 11:13:38 WindowServer[136]: Found 18 modes for display 0x042731c0 [18, 0]
2015-May-01 11:13:38 WindowServer[136]: Received display connect changed for display 0x746050c5
2015-May-01 11:13:38 WindowServer[136]: Found 2 modes for display 0x746050c5 [2, 0]
2015-May-01 11:13:38 WindowServer[136]: disable_update_timeout: UI updates were forcibly disabled by application "Finder" for over 1.00 seconds. Server has re-enabled them.
2015-May-01 11:13:38 WindowServer[136]: common_reenable_update: UI updates were finally reenabled by application "Finder" after 1.65 seconds (server forcibly re-enabled them after 1.64 seconds)
2015-May-01 11:13:38 WindowServer[136]: Received display connect changed for display 0x42731c0
2015-May-01 11:13:38 WindowServer[136]: Found 18 modes for display 0x042731c0 [18, 0]
2015-May-01 11:13:38 WindowServer[136]: Received display connect changed for display 0x31000001
2015-May-01 11:13:38 WindowServer[136]: Found 2 modes for display 0x31000001 [2, 0]
2015-May-01 11:13:38 WindowServer[136]: Display 0x042731c0: GL mask 0x1; bounds (0, 0)[1280 x 800], 18 modes available
Main, Active, on-line, enabled, built-in, boot, OpenGL-accel, Vendor 610, Model 9cc7, S/N 0, Unit 0, Rotation 0
UUID 0xcb5a19e16c20c98ebb2d70fc3bb550b4, ColorSpace { 1632878172 }
2015-May-01 11:13:38 WindowServer[136]: GLCompositor: GL renderer id 0x0102261a, GL mask 0x00000003, accelerator 0x000036cf, unit 0, caps QEX|MIPMAP, vram 256 MB
texture max 8192, viewport max {8192, 8192}, extensions NPOT|GLSL|FLOAT
2015-May-01 11:13:38 WindowServer[136]: Display 0x31000001: GL mask 0x2; bounds (1280, 0)[640 x 480], 2 modes available
Active, on-line, enabled, OpenGL-accel, Vendor 3ac4, Model 0, S/N 0, Unit 1, Rotation 0
UUID 0x5a88aeaaae3bbb86e9aec154726397dd, ColorSpace { 1331579117 }
2015-May-01 11:13:38 WindowServer[136]: GLCompositor: GL renderer id 0x0102261a, GL mask 0x00000003, accelerator 0x000036cf, unit 0, caps QEX|MIPMAP, vram 256 MB
texture max 8192, viewport max {8192, 8192}, extensions NPOT|GLSL|FLOAT
2015-May-01 11:13:38 WindowServer[136]: CGError post_notification(const CGSNotificationType, void *const, const size_t, const bool, const CGSRealTimeDelta, const int, const CGSConnectionID *const, const pid_t): Timed out 0.250 second wait for reply from "Adobe Reader" for synchronous notification type 100 (kCGSDisplayWillReconfigure) (CID 0x20243, PID 2268)
2015-May-01 11:13:38 WindowServer[136]: CGError post_notification(const CGSNotificationType, void *const, const size_t, const bool, const CGSRealTimeDelta, const int, const CGSConnectionID *const, const pid_t): Timed out 0.250 second wait for reply from "Console" for synchronous notification type 100 (kCGSDisplayWillReconfigure) (CID 0x16403, PID 262)
2015-May-01 11:13:39 WindowServer[136]: CGError post_notification(const CGSNotificationType, void *const, const size_t, const bool, const CGSRealTimeDelta, const int, const CGSConnectionID *const, const pid_t): Timed out 0.250 second wait for reply from "Notification Center" for synchronous notification type 109 (<unknown>) (CID 0x14d13, PID 361)
2015-May-01 11:13:39 WindowServer[136]: CGError post_notification(const CGSNotificationType, void *const, const size_t, const bool, const CGSRealTimeDelta, const int, const CGSConnectionID *const, const pid_t): Timed out 0.250 second wait for reply from "Activity Monitor" for synchronous notification type 109 (<unknown>) (CID 0xa26b, PID 261)
2015-May-01 11:13:39 WindowServer[136]: Display 0x042731c0: Unit 0: Mode 640 x 480, CGSThirtytwoBitColor, Resolution 1, ioModeID 0x80003006, ioModeDepth 0x2, IOReturn 0x0
2015-May-01 11:13:39 WindowServer[136]: hw_mirror_device_if_possible: driver picks 0x31000001 as primary
2015-May-01 11:13:39 WindowServer[136]: CGXDisplaysDidReconfigure: Display mode changed
2015-May-01 11:13:39 WindowServer[136]: CGXDisplaysDidReconfigure: Display added
2015-May-01 11:13:39 WindowServer[136]: CGXDisplaysDidReconfigure: Display removed
2015-May-01 11:13:39 WindowServer[136]: CGXDisplaysDidReconfigure: Displays mirrored
2015-May-01 11:13:39 WindowServer[136]: Display 0x31000001: GL mask 0x2; bounds (0, 0)[640 x 480], 2 modes available
Master in mirror set; Main, Active, on-line, enabled, OpenGL-accel, Vendor 3ac4, Model 0, S/N 0, Unit 1, Rotation 0
UUID 0x5a88aeaaae3bbb86e9aec154726397dd, ColorSpace { 1331579117 }
2015-May-01 11:13:39 WindowServer[136]: GLCompositor: GL renderer id 0x0102261a, GL mask 0x00000003, accelerator 0x000036cf, unit 0, caps QEX|MIPMAP, vram 256 MB
texture max 8192, viewport max {8192, 8192}, extensions NPOT|GLSL|FLOAT
2015-May-01 11:13:39 WindowServer[136]: Display 0x042731c0: GL mask 0x1; bounds (0, 0)[640 x 480], 18 modes available
Hardware mirror of 0x31000001; on-line, enabled, built-in, boot, Vendor 610, Model 9cc7, S/N 0, Unit 0, Rotation 0
UUID 0xcb5a19e16c20c98ebb2d70fc3bb550b4, ColorSpace { 1632878172 }
2015-May-01 11:13:40 identityservicesd[224]: <IMMacNotificationCenterManager: 0x7f960b460af0>: notification observer: com.apple.iChat   notification: __CFNotification 0x7f960b4aaee0 {name = _NSDoNotDisturbDisabledNotification}
2015-May-01 11:13:40 WindowServer[136]: **DMPROXY** (2) Found `/System/Library/CoreServices/DMProxy'. Run with arg = -discovery
2015-May-01 11:13:40 WindowServer[136]: **DMPROXY** (2) Found `/System/Library/CoreServices/DMProxy'. Run with arg = -discovery
2015-May-01 11:13:40 identityservicesd[224]: <IMMacNotificationCenterManager: 0x7f960b460af0>:    NC Disabled: NO
2015-May-01 11:13:40 identityservicesd[224]: <IMMacNotificationCenterManager: 0x7f960b460af0>:   DND Enabled: NO
2015-May-01 11:13:40 identityservicesd[224]: <IMMacNotificationCenterManager: 0x7f960b460af0>: Updating enabled: YES   (Topics: (
2015-May-01 11:13:40 WindowServer[136]: **DMPROXY** (2) Found `/System/Library/CoreServices/DMProxy'. Run with arg = -discovery
2015-May-01 11:13:40 WindowServer[136]: **DMPROXY** (2) Found `/System/Library/CoreServices/DMProxy'. Run with arg = -discovery
2015-May-01 11:13:41 identityservicesd[224]: <IMMacNotificationCenterManager: 0x7f960b460af0>: notification observer: com.apple.iChat   notification: __CFNotification 0x7f960b44dd70 {name = _NSDoNotDisturbEnabledNotification}

Trouble with screen resolution when using Parallels and ACT on Macbook Pro (late 2013)

Hello, I have installed my Sage ACT 2013 software on my Macbook Pro 13" Retina (late 2013) computer that has 16GB of RAM and an i7 core processor using Parallels 9 desktop and Windows 7- 64bit. The problem is that the screen resolution is very small and condensed to the left side making reading the title boxes and content very difficult. I reached out to Parallels who was unable to resolve the screen resolution by either adjusting the display settings or the Windows 7 video settings. Right now they have the Resolution listed as "Scaled" as the "Best for Retina" & "More Space" options did not help the issue. What is even more strange is that I have Office 2013 installed on the Parallels side so that it can interface with ACT and those screen resolutions read just fine. Are there any ACT/MAC users out there that might have any insight for me? Thx!

See -> http://manuals.info.apple.com/MANUALS/1000/MA1636/en_US/boot_camp_install-setup_ 10.8.pdf.
In addition to the Windows disc (or USB flash drive with the Windows installer) you'll need a 8GB+ flash drive.
The referenced manual - on page 3, I think, gives you a run-down of what you'll need before you begin the installation. You may also want to post any further Boot Camp questions in the Boot Camp forum -> https://discussions.apple.com/community/windows_software/boot_camp.
Good luck,
Clinton

Where can I set the screen resolution

I am trying to use do a course online and they said that the screen resolution needs to be set at 1024 x 768. Where do I do this?

You can paste this in the Code field in the Firefox > Web Development (or Tools) > Error Console and click the Evaluate button and enter 1024x768 on the prompt.
<pre><nowiki>
var Cc=Components.classes, Ci=Components.interfaces;
var ps = Cc["@mozilla.org/embedcomp/prompt-service;1"].getService(Ci.nsIPromptService);
var wm = Cc["@mozilla.org/appshell/window-mediator;1"].getService(Ci.nsIWindowMediator);
var nb = wm.getMostRecentWindow("navigator:browser");
var txt = 'width x height';
var obj = new Object; obj.value = nb.window.outerWidth + 'x' + nb.window.outerHeight;
if(ps.prompt(null, 'Resize', txt, obj, null, {}) && (obj.value != null)){
var vA = obj.value.split("x");
if(vA[0]) nb.window.outerWidth = vA[0];
if(vA[1]) nb.window.outerHeight = vA[1];
</nowiki></pre>

[SOLVED]Screen resolution began to be incorrectly detected

After installing some packages not having obvious relations to video issues (mysql and zfs related packages), the screen resolution on my 1280x1024 screen began to be set as 1024x768 without 1280x1024 in the list of possible modes. I tried to X -configure but to no avail. Reinstalling xorg-server also didn't help. I tried to manually detect and add 1280x1024 mode with xrandr, this mode began to appear in the modes list, but the resolution remains 1024x768 when it's selected.
I have an ancient SiS videocard, but it worked OK with the standard vesa driver.
What can be the cause of this issue and how it could be corrected?
Some fragments of Xorg log:
[ 769.623] (II) VESA(0): Total Memory: 512 64KB banks (32768kB)
[ 769.623] (II) VESA(0): Monitor0: Using default hsync range of 31.50-48.00 kHz
[ 769.623] (II) VESA(0): Monitor0: Using default vrefresh range of 50.00-70.00 Hz
[ 769.623] (II) VESA(0): Monitor0: Using default maximum pixel clock of 65.00 MHz
[ 769.623] (WW) VESA(0): Unable to estimate virtual size
[ 769.623] (II) VESA(0): Not using built-in mode "1600x1200" (no mode of this name)
[ 769.623] (II) VESA(0): Not using built-in mode "1280x1024" (no mode of this name)
[ 769.623] (II) VESA(0): Not using built-in mode "1024x768" (no mode of this name)
[ 769.623] (II) VESA(0): Not using built-in mode "800x600" (no mode of this name)
[ 769.623] (II) VESA(0): Not using built-in mode "640x480" (no mode of this name)
[ 769.623] (WW) VESA(0): No valid modes left. Trying less strict filter...
[ 769.623] (II) VESA(0): Monitor0: Using hsync range of 31.50-48.00 kHz
[ 769.623] (II) VESA(0): Monitor0: Using vrefresh range of 50.00-70.00 Hz
[ 769.623] (II) VESA(0): Monitor0: Using maximum pixel clock of 65.00 MHz
[ 769.623] (WW) VESA(0): Unable to estimate virtual size
[ 769.623] (II) VESA(0): Not using built-in mode "1600x1200" (hsync out of range)
[ 769.623] (II) VESA(0): Not using built-in mode "1280x1024" (hsync out of range)
[ 769.623] (--) VESA(0): Virtual size is 1024x768 (pitch 1024)
[ 769.623] (**) VESA(0): *Built-in mode "1024x768"
[ 769.623] (**) VESA(0): *Built-in mode "800x600"
[ 769.623] (**) VESA(0): *Built-in mode "640x480"
[ 769.623] (==) VESA(0): DPI set to (96, 96)
[ 769.623] (II) VESA(0): Attempting to use 60Hz refresh for mode "1024x768" (118)
[ 769.624] (II) VESA(0): Attempting to use 60Hz refresh for mode "800x600" (115)
[ 769.624] (II) VESA(0): Attempting to use 60Hz refresh for mode "640x480" (112)
// Another fragment:
[ 769.384] (II) LoadModule: "glx"
[ 769.384] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 769.392] (II) Module glx: vendor="X.Org Foundation"
[ 769.392] compiled for 1.16.0, module version = 1.0.0
[ 769.392] ABI class: X.Org Server Extension, version 8.0
[ 769.392] (==) AIGLX enabled
[ 769.392] (II) LoadModule: "vesa"
[ 769.393] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 769.395] (II) Module vesa: vendor="X.Org Foundation"
[ 769.395] compiled for 1.16.0, module version = 2.3.2
[ 769.395] Module class: X.Org Video Driver
[ 769.395] ABI class: X.Org Video Driver, version 18.0
[ 769.395] (II) VESA: driver for VESA chipsets: vesa
[ 769.395] (++) using VT number 1
[ 769.395] (--) controlling tty is VT number 1, auto-enabling KeepTty
[ 769.395] (II) Loading sub module "vbe"
[ 769.395] (II) LoadModule: "vbe"
[ 769.396] (II) Loading /usr/lib/xorg/modules/libvbe.so
[ 769.396] (II) Module vbe: vendor="X.Org Foundation"
[ 769.396] compiled for 1.16.0, module version = 1.1.0
[ 769.396] ABI class: X.Org Video Driver, version 18.0
[ 769.396] (II) Loading sub module "int10"
[ 769.396] (II) LoadModule: "int10"
[ 769.398] (II) Loading /usr/lib/xorg/modules/libint10.so
[ 769.399] (II) Module int10: vendor="X.Org Foundation"
[ 769.399] compiled for 1.16.0, module version = 1.0.0
[ 769.399] ABI class: X.Org Video Driver, version 18.0
[ 769.399] (II) VESA(0): initializing int10
[ 769.421] (II) VESA(0): Primary V_BIOS segment is: 0xc000
[ 769.424] (II) VESA(0): VESA BIOS detected
[ 769.424] (II) VESA(0): VESA VBE Version 3.0
[ 769.424] (II) VESA(0): VESA VBE Total Mem: 32768 kB
[ 769.424] (II) VESA(0): VESA VBE OEM: SiS
[ 769.424] (II) VESA(0): VESA VBE OEM Software Rev: 1.0
[ 769.424] (II) VESA(0): VESA VBE OEM Vendor: Silicon Integrated Systems Corp.
[ 769.424] (II) VESA(0): VESA VBE OEM Product: 6330
[ 769.424] (II) VESA(0): VESA VBE OEM Product Rev: 3.72.10
[ 769.448] (==) VESA(0): Depth 24, (--) framebuffer bpp 32
[ 769.448] (==) VESA(0): RGB weight 888
[ 769.448] (==) VESA(0): Default visual is TrueColor
[ 769.448] (==) VESA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 769.448] (II) Loading sub module "ddc"
[ 769.448] (II) LoadModule: "ddc"
[ 769.448] (II) Module "ddc" already built-in
[ 769.533] (II) VESA(0): VESA VBE DDC supported
[ 769.533] (II) VESA(0): VESA VBE DDC Level none
[ 769.533] (II) VESA(0): VESA VBE DDC transfer in appr. 0 sec.
[ 769.576] (II) VESA(0): VESA VBE DDC read failed
[ 769.576] (II) VESA(0): Searching for matching VESA mode(s):
Last edited by nbd (2014-08-05 09:17:50)

I tried the 'xf86-video-sis' from the official repositories, but it didn't work: 'X -configure' outputs that no devices are found.
The command
# lspci | grep SiS
gives the output:
00:00.0 Host bridge: Silicon Integrated Systems [SiS] 662 Host (rev 01)
00:01.0 PCI bridge: Silicon Integrated Systems [SiS] AGP Port (virtual PCI-to-PCI bridge)
00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS964 [MuTIOL Media IO] LPC Controller (rev 36)
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 IDE Controller (rev 01)
00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] SiS7012 AC'97 Sound Controller (rev a0)
00:03.0 USB controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f)
00:03.1 USB controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f)
00:03.2 USB controller: Silicon Integrated Systems [SiS] USB 1.1 Controller (rev 0f)
00:03.3 USB controller: Silicon Integrated Systems [SiS] USB 2.0 Controller
00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet (rev 91)
00:05.0 IDE interface: Silicon Integrated Systems [SiS] SATA (rev 01)
00:1f.0 PCI bridge: Silicon Integrated Systems [SiS] PCI-to-PCI bridge
01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter (rev 04)
The command 'X -configure' with the 'xf86-video-vesa' driver produces the following xorg.conf file:
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc/"
FontPath "/usr/share/fonts/TTF/"
FontPath "/usr/share/fonts/OTF/"
FontPath "/usr/share/fonts/Type1/"
FontPath "/usr/share/fonts/100dpi/"
FontPath "/usr/share/fonts/75dpi/"
EndSection
Section "Module"
Load "glx"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection
Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string>: "String", <freq>: "<f> Hz/kHz/MHz",
### <percent>: "<f>%"
### [arg]: arg optional
#Option "ShadowFB" # [<bool>]
#Option "DefaultRefresh" # [<bool>]
#Option "ModeSetClearScreen" # [<bool>]
Identifier "Card0"
Driver "vesa"
BusID "PCI:1:0:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
The X server is started via startxfce4 in the ~/.xinitrc file:
#!/bin/sh
# ~/.xinitrc
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fi
exec startxfce4
I tried to use the recommendations about using xrandr. The command
# cvt 1280 1024
produces the following:
# 1280x1024 59.89 Hz (CVT 1.31M4) hsync: 63.67 kHz; pclk: 109.00 MHz
Modeline "1280x1024_60.00" 109.00 1280 1368 1496 1712 1024 1027 1034 1063 -hsync +vsync
Then I perfrom the following two commands:
# xrandr --newmode "1280x1024_60.00" 109.00 1280 1368 1496 1712 1024 1027 1034 1063 -hsync +vsync
# xrandr --addmode default "1280x1024_60.00"
This adds the 1280x1024 mode to the list of available modes in the display control panel, but when
this mode is selected - nothing happens and the resolution remains the same: 1024x768.
EDIT:
I tried all three SiS drivers from the repository: sis, sisusb and sisimedia. In all three cases 'X -configure' failed with an error message: "No devices to configure". The strange thing is that the vesa driver worked OK out of the box. What could cause such a strange problem with the screen resolution?
EDIT 2:
The cause of the problem was the cable from the monitor to the computer: it was twisted and apparently was causing some aberrations to the signal. I found out it when added to the xorg.conf file the line HorizSync = 58-61. After adding that line the problem disappeared. I began to think why the things previously have been working OK without that line. And supposed that the matter is in hardware. I straighted out the cable and the problem isn't occuring anymore even without the xorg.conf editings.
Last edited by nbd (2014-08-04 17:58:13)

Flash Island width and height - screen resolution

Hi,
I'm wondering if anybody knows a way to determine the screen resolution used in WDA? You might wonder why do we need screen resolution when you have 100% and flow layout.. well we're using a Flash Island frontend, and you are obligated to enter a height and width for the island. We'd like to support multiple resolutions for users and we could try to bind height and width to context attributes and set these in WWDOINIT perhaps if we'd know how to determine the resolution.
Thanks in advance,
Wouter

and you are obligated to enter a height and width for the island
I'm not sure that's completely true - I have an island that we set the height for - but the width as 100% - that seems to work just fine - albeit that the size is fixed from entry into the application - resizing the window does not resize the island.
I haven't wanted an island with 100% height - but are you sure this doesn't work?
if you watch the teched virtual session [CD203: Best Practices for Designing Web Dynpro ABAP User Interfaces |http://tinyurl.com/2dcp3fv] there is looooooooooong section in there where they go on and on about 100% rendering - it's pretty obvious - but worth repeating (at least it seems so in the session) 100% is only 100% of the container that the container is embedded within.
Have a go - I'm not 100% convinced you can't have a 100% island
Cheers,
Chris

Indesign interface screen resolution

Similar Messages

Maybe you are looking for