Current screen resolution and availability of soundcard under Mac???

Hi
How can I define current screen resolution under Mac OS X?
Under Windows I use function baScreenInfo("width"),
baScreenInfo("height")
for this purpose or baMultiDisplayInfo("primary", "width")
etc
The same question concerns to availability of soundcard
Under Windows I can define, if the soundcard is installed
using function
basoundCard()
What about mac OS X ?
Any help will be appreciated
game_dev

You don't need buddyAPI to find out the user's screen
dimensions. You can just ask for the desktopRectList. This will
give you a list of screen rects. If there is more than one rect in
the list, then the first one is the user's primary screen. All macs
have built in sound. You don't need to check for sound for a mac
user.

Similar Messages

After target display mode, iPhoto reports an error, "The current screen resolution is not optimal for iPhoto."

I have the 27-inch (late 2009) iMac with mini-Display port input. Whenever I return from Target Display Mode, I get the attached error message and iPhoto becomes unresponsive (the window is still active, but clicking on it produces the error/warning system sound), I have to Force Quit it. The current screen resolution is not optimal for iPhoto (sometimes the error message is a little off the screen in the lower left and only the top of the window can be seen. This also seems to affect iTunes at the same time (by resizing the window to be super small), but without the error message or unresponsiveness.
Has anyone else gotten this problem, and or might know of a fix?

Yes, I have the same problem. I have checked the resolution in Sysyem Preferences - display and it is properly set to the highest resolution (which is recommended). I have no idea why this is ocurring but it is annoying.

Best screen resolution and output for CBT

What would be the best screen resolution and output mode IYO for a CBT (Computer Based Training) program? We would like to do either CD or online. We are toying with either, so which do you think would be a better option for what Captivate is capable of? Thanks!

Nclarkats,
While most of our employees have similar screen resolutions, a few have larger (or smaller) set ups and since we wish to avoid horizontal and vertical scroll bars; we publish with Captivate's 800 x 600 setting. This allows us to get a bit larger imagery in place.
Whatever you choose, try and pick something and stay consistent. This is beneficial in the event you have to transfer slides between modules.
Hope that helps.
Chuck

I was trying to fix my screen resolution and now it's stuck on auto detect cannot display this video mode. I tried another monitor and it still won't show anything. I'm locked out

I was trying to fix my screen resolution and now it's stuck on auto detect cannot display this video mode. I tried another monitor and it still won't show anything. I'm locked out

Reset the SMC and PRAM
Intel-based Macs: Resetting the System Management Controller (SMC)
About NVRAM and PRAM
Next try Safe Mode boot and and then normal boot
OS X: What is Safe Boot, Safe Mode?

Hi: When I open my iPhoto the popup shows up and I don't know how to correct it. Here is the popup "The current screen resolution is not optimal for iPhoto?" Can you help

When I open my iPhoto a popup shows up and I don't know how to correct it the popup:
"The current screen resoulation is not optimal for iPhotp"?
Can you help?

Go to the System/Accesability preference pane and enable the Zoom capability either with keystrokes or Magic Mouse:
See if that will work for you.
OT

What screen resolutions are available on His-res 15" MacBook Pro?

Hi. I can see in the apple web site specs what the various screen resolution settings are for the standard resultion, 1440x900,
15" MacBook Pro (1440x900, 1280x800, 1152x720, etc.)
But what are the settings available for the 15" MacBook Pro with the hi-res (glossy to be specific) screen?
I know the native resolution is 1680x1050. Are the other settings as for the standard res also available?
And while I have your attention, does anyone know what type of LCD panels are used on the standard and hi-res displays?
TN, PVA, IPS ?

The hi-reolution one :
The Glossy one :

Windows XP Pro Desktop - Screen Resolution and Color Quality

When synchronizing my Zire after many successful and no problems the XP Pro screen resolution reverted to the lowest profile.
I can reset the resolution to the True color 1024 x 768 but after a minute or two it reverts again.
1. Reinstalled driver for Intel video on Compaq D510C motherboard and get same problems as well as corrupted looking graphics on screen.
2. Switched to a known good monitor and same problems (which I did not think was the problem but did to verify).
3. Installed new gForce5200fx graphics card and video still reverts and is corrupted looking even when in higher reset resolution.
4. Created new user to see if user profile was corrupted and still reverts and is corrupted looking even when in higher reset resolution.
Any suggestions?????

I also flashed the bios

Adobe Reader 9.3.4 causes poor screen resolution and unreadable pdf documents. Why?

When I open Reader (9.3.4) the screen resolution becomes very poor - like a color monitor from the early 80's - and text in pdf documents is highlighted black or some other random color, making it unreadable. This has been the case since I upgraded from Reader 8 recently. Any ideas on how to fix this?

To those that tried to assist me with trying to get Reader to display
correctly. Thanks for your assistance.
I resolved the problem by doing a backup of all my files, then formatting the hard drive and reinstalling all programs, from XP to Trend Micro, to Office 2003 and finally Reader 9.
The problem has gone and the speed and stability of my PC has been greatly improved.

|Solved| - Screen resolution and nVidia

I installed arch, xorg, nvidia's drives, openbox and gnome.
I can run gnome and openbox without any problem, however, my screen resolution isn't recognised. Here's my /etc/X11/xorg.conf:
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 1.0 (buildmeister@builder58) Thu Jun 5 00:08:24 PDT 2008
# File generated by xorgconfig.
# Copyright 2004 The X.Org Foundation
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
# The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
# Except as contained in this notice, the name of The X.Org Foundation shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from
# The X.Org Foundation.
# Refer to the xorg.conf(5) man page for details about the format of
# this file.
# Module section -- this section is used to specify
# which dynamically loadable modules to load.
# Files section. This allows default font and rgb paths to be set
# Server flags section.
# Input devices
# Core keyboard's InputDevice section
# Core Pointer's InputDevice section
# Other input device sections
# this is optional and is required only if you
# are using extended input devices. This is for example only. Refer
# to the xorg.conf man page for a description of the options.
# Section "InputDevice"
# Identifier "Mouse2"
# Driver "mouse"
# Option "Protocol" "MouseMan"
# Option "Device" "/dev/mouse2"
# EndSection
# Section "InputDevice"
# Identifier "spaceball"
# Driver "magellan"
# Option "Device" "/dev/cua0"
# EndSection
# Section "InputDevice"
# Identifier "spaceball2"
# Driver "spaceorb"
# Option "Device" "/dev/cua0"
# EndSection
# Section "InputDevice"
# Identifier "touchscreen0"
# Driver "microtouch"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "1412"
# Option "MaxX" "15184"
# Option "MinY" "15372"
# Option "MaxY" "1230"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# Section "InputDevice"
# Identifier "touchscreen1"
# Driver "elo2300"
# Option "Device" "/dev/ttyS0"
# Option "MinX" "231"
# Option "MaxX" "3868"
# Option "MinY" "3858"
# Option "MaxY" "272"
# Option "ScreenNumber" "0"
# Option "ReportingMode" "Scaled"
# Option "ButtonThreshold" "17"
# Option "ButtonNumber" "1"
# Option "SendCoreEvents"
# EndSection
# Monitor section
# Any number of monitor sections may be present
# Graphics device section
# Any number of graphics device sections may be present
# Standard VGA Device:
# Device configured by xorgconfig:
# Screen sections
# Any number of screen sections may be present. Each describes
# the configuration of a single screen. A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
# ServerLayout sections.
# Any number of ServerLayout sections may be present. Each describes
# the way multiple screens are organised. A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option. In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.
# Section "DRI"
# Mode 0666
# EndSection
Section "ServerLayout"
# The Identifier line must be present
# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens. The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen. In this example, screen 2 is located to the
# right of screen 1.
# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used. Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".
Identifier "Simple Layout"
Screen "Screen 1" 0 0
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection
Section "Files"
# The location of the RGB database. Note, this is the name of the
# file minus the extension (like ".txt" or ".db"). There is normally
# no need to change the default.
# RgbPath "/usr/share/X11/rgb"
# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
# FontPath "/usr/share/fonts/TTF"
# FontPath "/usr/share/fonts/Type1"
# FontPath "/usr/lib/X11/fonts/local/"
# FontPath "/usr/lib/X11/fonts/misc/"
# FontPath "/usr/lib/X11/fonts/75dpi/:unscaled"
# FontPath "/usr/lib/X11/fonts/100dpi/:unscaled"
# FontPath "/usr/lib/X11/fonts/Speedo/"
# FontPath "/usr/lib/X11/fonts/Type1/"
# FontPath "/usr/lib/X11/fonts/TrueType/"
# FontPath "/usr/lib/X11/fonts/freefont/"
# FontPath "/usr/lib/X11/fonts/75dpi/"
# FontPath "/usr/lib/X11/fonts/100dpi/"
# The module search path. The default path is shown here.
# ModulePath "/usr/lib/modules"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/75dpi:unscaled"
EndSection
Section "Module"
# This loads the DBE extension module.
# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
# This loads the font modules
# Load "type1"
# This loads the GLX module
# Load "glx"
# This loads the DRI module
# Load "dri"
Load "dbe" # Double buffer extension
SubSection "extmod"
Option "omit xfree86-dga" # don't initialise the DGA extension
EndSubSection
Load "freetype"
# Load "xtt"
Load "glx"
EndSection
Section "InputDevice"
# Option "Xleds" "1 2 3"
# Option "LeftAlt" "Meta"
# Option "RightAlt" "ModeShift"
# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc105"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
# Option "XkbLayout" "de"
# or:
# Option "XkbLayout" "de"
# Option "XkbVariant" "nodeadkeys"
# If you'd like to switch the positions of your capslock and
# control keys, use:
# Option "XkbOptions" "ctrl:swapcaps"
# These are the default XKB settings for Xorg
# Option "XkbRules" "xorg"
# Option "XkbModel" "pc105"
# Option "XkbLayout" "us"
# Option "XkbVariant" ""
# Option "XkbOptions" ""
# Option "XkbDisable"
Identifier "Keyboard1"
Driver "kbd"
Option "AutoRepeat" "500 30"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
Option "XkbRules" "xorg"
Option "XkbModel" "logicd"
Option "XkbLayout" "pt"
Option "XkbVariant" "pt"
EndSection
Section "InputDevice"
# Identifier and driver
# Option "Resolution" "256"
# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.
# Option "BaudRate" "9600"
# Option "SampleRate" "150"
# Mouse wheel mapping. Default is to map vertical wheel to buttons 4 & 5,
# horizontal wheel to buttons 6 & 7. Change if your mouse has more than
# 3 buttons and you need to map the wheel to different button ids to avoid
# conflicts.
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)
# Option "Emulate3Buttons"
# Option "Emulate3Timeout" "50"
# ChordMiddle is an option for some 3-button Logitech mice
# Option "ChordMiddle"
Identifier "Mouse1"
Driver "mouse"
Option "Protocol" "Auto" # Auto detect
Option "Device" "/dev/input/mice"
# Mouse-speed setting for PS/2 mouse.
Option "ZAxisMapping" "4 5 6 7"
# Emulate3Buttons is an option for 2-button mice
EndSection
Section "Monitor"
# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
# HorizSync 30-64 # multisync
# HorizSync 31.5, 35.2 # multiple fixed sync frequencies
# HorizSync 15-25, 30-50 # multiple ranges of sync frequencies
# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY. REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.
Identifier "My Monitor"
HorizSync 80.0 - 80.0
VertRefresh 75.0
EndSection
Section "Device"
# The chipset line is optional in most cases. It can be used to override
# the driver's chipset detection, and should not normally be specified.
# Chipset "generic"
# The Driver line must be present. When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module. Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for. When this line isn't present, a device
# section can only match up with the primary video device. For PCI
# devices a line like the following could be used. This line should not
# normally be included unless there is more than one video device
# intalled.
# BusID "PCI:0:10:0"
# VideoRam 256
# Clocks 25.2 28.3
Identifier "Standard VGA"
Driver "nvidia"
VendorName "Unknown"
BoardName "Unknown"
EndSection
Section "Device"
# unsupported card
#VideoRam 319488
# Insert Clocks lines here if appropriate
Identifier "My Video Card"
Driver "nvidia"
EndSection
Section "Screen"
Identifier "Screen 1"
Device "My Video Card"
Monitor "My Monitor"
DefaultDepth 24
SubSection "Display"
Viewport 0 0
Depth 8
Modes "1440x900"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
Modes "1440x900"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
Modes "1440x900"
EndSubSection
EndSection
If I run "xorgconfig" and after that "nvidia-xconfig", my screen resolution is 1024x860, but after changed very mode to my native resolution ("1440x900"), is changes to "800x600".
Last edited by Nomearod (2008-07-23 09:19:07)

heleos wrote:
Widescreen resolutions are not possible with newest vista and linux drivers if the tft is connected with dvi.
Use an older driver or the vga-port instead.
There are maybe some hacks, but I tried many times in vista and linux. And it's always the same, only 1280x1024.
did some googling:
http://forums.nvidia.com/lofiversion/in … 20005.html
Thanks for the reply, but I don't believe that's the problem since that topic is from 2006 and I didn't had any problems last time I instaled arch (3 months ago).

Solaris 10 x86 console screen resolution and blank console after exiting X

Hello,
At some point my Solaris 10 machine stopped showing the console after leaving Xorg for the console login. I know the console is active because I can blindly pass the shutdown or other command and it will respond, or after waiting a few minutes will bring the GUI login back. I can see the console before the GUI login while booting but not after. I have a dual output Nvidia 6200 on a 22" LCD running Solaris 10 using the latest Nvidia drivers. I would also like to know if it possible to set the console screen resolution somehow either from the shell or from grub? I have been searching the internet for weeks about this and am unable to find a solution.
TIA,
Brett

After doing even more searching, it looks as if this is an issue with Nvidias drivers. At least similar issues on Linux and FreeBSD that I have seen. Anyone know of a fix other than reverting to much older drivers? Still cannot find any info on setting the console screen resolution, though I can't even see it at the moment unless I refrain from ever starting X again. There has to something similar to vga= that's used in Linux. Anyone?
Brett

Windows XP Pro Desktop - Screen Resolution and Color Quality - After Palm 6.2 Installation for Palm TX

Recently upgraded my Palm software to 6.2. for my TX. Now when I sync to Outlook, my windows desktop reverts to lower quality screen resolution (640 x 480 pixels) and lower color quality (8 bit).
I then make the necessary display changes for my windows desktop back to higher quality screen resolution (1280 x 800 pixels) and highest color quality (32 bit). Everything is fine until I sync again or shut down the computer and restart, causing the windows desktop to revert back to the lower quality screen.
Any thoughts on possible solutions to this annoying problem.
Thank you
Post relates to: Palm TX

Hello!
First thing to do is to update the display driver for your computer. Also make sure to use 96 DPI for the DPI setting, using another setting can cause this issue too.
Post relates to: Treo 650 (Unlocked GSM)
Message Edited by thetreoguy on 03-17-2009 10:29 AM

How to find out the current screen resolution/width in webdynpro.

HI,
Can any one please tell me how to get the screen resolution in webdynpro?
Regards
-Sandip

Hi Sandip,
- view size can be set by setting the 'width' of the RootUIElementContainer. By defalut, it will be 100% only. Also, It is always better to use the % coz it does not distort your view with different screen resolutions.
- while creating the iview, you have the property like 'HeightType'. There you can set the value as FIXED, AUTOMATIC & FULL_PAGE. If you wish, you may leave it as it is.
- All you have the properties like 'Fixed Height' etc to set the size values.
Regards
Chander Kararia
# Please close the thread once get the correct answer. Give rewards for answers.
Edited by: Chander Kararia on Feb 20, 2009 9:55 AM

Screen resolution and published output

Hi Gurus
I am recording content using 5.5 using a laptop with resolution of 1366 x 768.
Created a blank project with resolution of 1024 x 768. When I publish this and then select Yes at the prompt "...Do you wish to view the output?" it requires quite a bit of scrolling down to see the Playback Control (as you might expect).
Created a blank project with resolution of 800 x 600. When I publish this and then select Yes at at the prompt "...Do you wish to view the output?" it requires less scrolling down to see the Playback Control (as you might also expect).
Here's the bit that I don't get. When I open the .swf files directly, they both "size" to fit the browser window and no scrolling is required to see the Playback Control. The only difference, of course, is that the lower resolution capture has less screen area covered. I am using IE7.
I had expected that the output when opening the .swf files would be the same as when I view after publish - kind of threw me there for a while.
Can someone kindly shed some light on this?
Thanks
Lynton123

Viewing the published files by launching the HTM page that has the SWF embedded will display the SWF at a fixed height and width that is set to the same height and width found in your project.
Launching the SWF directly by double-clicking it will cause it to be displayed in the web browser but it will maximise or shrink to whatever height or width is available. This is just the way that SWFs work in browsers when not embedded in a HTM wrapper.
So why wouldn't you want it to always work this way? Well, just launching the SWF is NOT going to give you all the functionality you need in many cases. For example, any functionality like SCORM or right-mouse-click that depends on JavaScript will not be available to you unless you launch via the HTM file. Secondly, resizing the SWF content to a different height/width ration than what it was created at will inevitably sacrifice some crispness in the output. This is especially evident with software screenshots for tutorials and simulations.

Changing screen resolution and rotation more easily?

Hi!
I frequently switch between two screen configurations of my LCD: the standard 1024x768 and 768x1024 rotated in portrait mode. The switching process is somewhat tedious:
open sys preferences,
select 90° rotation -> Mac OS switches to 1024x768 rotated
(which my monitor doesn't support -> fuzzy display)
click OK to confirm new resolution
select 768x1024
click OK in dialog
click OK to confirm new resolution
I wish I could use the menu bar thing to switch resolutions, but it doesn't offer rotation. Even if I could eliminate the two-step resolution switching, it would save a lot of trouble. I've tried editing the plist file in /Library/Preferences, but my mini seems to ignore it.
Any suggestions?
thanks
Hendrik
mini G4 Mac OS X (10.4.10)

I have not found anyway to resize the incoming screen, in iChat or the Built-in Screen Sharing app.
7:08 PM Tuesday; January 26, 2010

Screen resolution and Personas

Hi,
When i a design a flavor with 14" monitor and see it in another 14" monitor then it looks fine as designed. But when i see the same flavor in a monitor of size 23" then blank space appears on the right & bottom side of the screen.
Similarly when i design a flavor with 23" monitor and see it on a 14" monitor then a scroll bar appears at bottom & right side of the screen. Entire screen is not visible unless the screen is scrolled.
Is there any setting to make persona smart enough to adjust itself based on the monitor size?
Any help is highly appreciated.
Regards,
Avinash

It isn't documented that you can't do it in Personas 2, no.
How you do it in Personas 3 is documented in this SCN document - Giving an SAP transaction a responsive design with SAP Screen Personas 3.0.
Steve.

Current screen resolution and availability of soundcard under Mac???

Similar Messages

Maybe you are looking for