Targeting multiple screen resolutions

Hello,
I'm creating my first ios app and I'm unsure of the best way to handle the fact that there are 3 different potential target screen resolutions (iPhone3, iPhone4 & iPad).
Do I need to create optimised assets for all three resolutions and then detect the full screen stage size of the device and adjust accordingly? Or is there a better approach than that?
Thanks

Does this help?
http://www.adobe.com/devnet/flash/articles/authoring_for_multiple_screen_sizes.html
http://www.adobe.com/devnet/air/articles/multiple-screen-sizes.html
Roy

Similar Messages

How to adjust website to work with multiple screen resolutions?

http://www.allenkey.com.au/
hello i have recently designed this website and the formatting isnt correct when veiwed with different screen resolutions
Pleese help!

hello i have recently designed this website and the formatting isnt correct when veiwed with different screen resolutions
Just so you'll know, and to keep the thread clear, resolution has nothing to do with how your page renders or is formatted. A given page will look exactly the same on any resolution screen provided you keep the browser width the same pixel value. It's the variation in that width from one resolution screen to another that causes the difference. And yes, it's the fact that you have used absolute positioning as a primary layout method that is the problem for the reason that JTANNA has already mentioned.
Now - how do you want your page to behave? Do you want it to be fixed width and centered (that would be the easiest). In that case, change this -
<body>
to this -
<body>
<div style="width:928px;margin:0 auto;position:relative">
and this -
</body>
to this -
</div>
</body>
Now, reposition all of your AP containers so that the page is again aligned the way you want, and you're done.

How do I develop for multiple screen resolutions using Adobe Air

Hi,
I'm looking at developing mobile apps using Adobe Air but there's something I'm not quite sure. Sorry if this is a newbie question or has been repeated but I have looked at tutorials, etc but just want to get a general idea on how to prepare the assets. Here are some of my questions:-
1) If I want to develop for the iPhone non-retina and retina resolution, do I actually need to only write the code and layout the graphics in retina(960 x 640) stage size and it will automatically scale down for non-retina resolution?
2) How do I cater for iPhone 5 resolution? Do I actually need to swap say the background images through code by detecting the resolution size it was in? or do I actually just leave the background image longer it exceeds the stage height so when it's iPhone 5 it will show everything?
thanks for the help!

If you are talking about regular Flash work, and not your own code-layout application, then what happens depends on the scale mode of the stage. Typically, when doing code layout the stage is set to no_scale, and you have to do all the hard work yourself, calculating the size of things, and laying them out with ActionScript.
If it's more of a typical Flash graphical scene there are two other scale modes that make life easier for you.
The default scale mode is show_all. With that you will be certain to see all of the content of your original Flash stage, and if the screen is a wider ratio than your stage, the content that is off the sides of the stage will be revealed. See this app I made, that uses that technique:
https://itunes.apple.com/us/app/meet-heckerty-funny-interactive/id514220257?mt=8
It works well enough, I have enough extra background graphics to go out to a 16:9 screen, including iPhone 5. That particular stage is 1024x768, and it will scale all the way from iPad 3 Retina down to iPhone 3gs.
The other scale mode that is useful is no_border. In that mode you are certain to not have any black borders around the stage. It achieves that by cropping into either the left and right, or the top and bottom, of the stage. See these apps I made, that work that way:
https://itunes.apple.com/us/app/milkshake-mayhem/id556962979?mt=8
https://itunes.apple.com/us/app/p.s.-snowflake-yourself/id571384475?mt=8
In both of those cases I have content that is correct for half way between the ratio limits of 16:9 and 4:3 (or 9:16 and 3:4 for the portrait case). When the app runs on your device, some amount of the left and right, or the top and bottom, of the stage is cropped. I have enough background content for that to be ok, and all of the important content is within the middle 14:9 or 9:14 area of the screen. The stage size for the landscape app is 1680xx1080, exactly 14:9. This approach is better than the show_all one, in that the user doesn't feel like they are seeing a lot of blank space, as can be the case when viewing a 4:3 stage on a 16:9 screen.
One last thing, even with either of those techniques the app won't fill the iPhone 5 screen. To get that to work you have to include a splash screen that is 640x1136, and name [email protected]. With that in place iOS knows to make your app use the full width or height of the iPhone 5.

Director 12 IOS screen resolution scaling

Hi All,
At of this moment Director 12 does not offer screen resolution scaling, my question is how does one overcome screen resolutions of different iDevices.
I want my project to run in full screen but Director doesn't allow you to target different screen resolution of different iPad, iPhone and iPod.
Thank you for any feedback.
Regards
Paul

on prepareMovie
(the stage).rect = the desktopRectList[1]

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.

Auto-Detect Screen Resolution Does Not Work Across Multiple Monitors With Different Resolutions

Hi,
The Acrobat Pro DC (15.007.20033.2203) auto-detect screen resolution feature does not work with multiple monitors at different resolutions. Acrobat looks fine on my hidpi primary laptop display (Razr 14" 2014) but is completely unusable if I drag or extend the application to a standard HD resolution secondary monitor. Dragging Acrobat from my primary desktop display to the secondary display causes the UI elements to become 2x as large as they should be and makes Acrobat unusable.
Is there a way to make Acrobat auto-detect the display that it is currently on?
Thanks!
-Donald

To prevent it from happing again, you can
1. go to the Mouse preference and turn off the scroll zoom feature.
2. go to the Universal Access preference and disable the zoom features.

Screen resolution of target system

Hi,
My webdynpro application looks different when opened on browsers having different screen resolutions. The reason for this is that I have hardcoded the width/height specs of different UI elements. Therefore, I would like to know a mechanism by which I can get the screen resolution of the broswer opening my application, so that all the UI elements have relative dimensions.
Regards, Sameer

Hi Valery,
Good Reply but are you sure that it cannot happen via Webdynpro ? I do not know how standard SAP applications e.g leave request, payroll or performane management apps all look the same even on different screen resolutions.
Also can we read a cookie stored in browser via webdynpro ? If yes, what is the way to do that ?
Regards, Sameer.

Creating an app for different screen resolutions/sizes

Hi
I'm currently in the process of learning application development for the iPhone and could do with some help on how to cater for retina and non-retina screens. I want to create image assets for each screen type.
What the best way to go about detecting if the user has an iPhone 4 for example and selecting the appropriate images for that resolution? I understand that you attach '2x' to file names when coding natively but for a pure Actionscript project where the assets might be contained in a swc file what would be best to do?
Thanks

Hi Vic,
The biggest advantage of building apps in Flash CS5.5 or Flex is the ability to target multiple devices and the 2 major platforms, iOS and Android oh and also Blackberry (anyone?).
Best way to approach a build is to assume you do not know the screen size your app will be used on, since Android is so all over the place.
I have been using stage.stageHeight and stage.stageWidth religiously for all my scaling although I have heard that method has its problems, it has worked well for me, I have put out 2 apps personally and 3-4 for work using this method both in Landscape and Portrait orientations and this method has worked well.
The easiest way to build a multi screen app is to design it for an average ratio, 3:4 being the lowest = iPad so lets say you pick some decent size that wont be too big for smaller screens like the iPhone 3gs 480x320 and wont be too low for high res screens like the new Google Nexus or the Motorola Xoom 1280x800. I usually target the iPhone 4 screen 960x640 right now it seems to fall in the middle between older phones and tablets.
The real quick and dirty way of doing it is to build all your assets inside a movie clip and then scale that movie clip proportionally to the stage, first checking to make sure none of it would be cut off due to different screen ratios, this is not the best way of doing it but it works well and its the easiest method.
A better way is to scale and place your content in relation to the stage, again the stage.stageWidth and Height properties are your friends so if you have an element that always goes in the middle you would place it my_mc.x = stage.stageHeight / 2 and same with the y, you can also scale it to the stage my_mc.width = stage.stageWidth/4 this way the movie clip is always 1/4th of the stage width regardless of the screen, its a lot planning up front but this method allows you to cover the entire screen instead of just cramming your movie clip in there however it fits.
Let me know if any of that helped I can go into further detail but I feel like I am rambling on.

Unable to Change Screen Resolution in Remote Session - Windows Server 2012 R2

Does anybody know of a way to allow Remote Desktop users to adjust their own screen resolution in a remote session under Windows Server 2012 R2? We are struggling with this and can't seem to find a solution.
When users login to their RDP session and try to adjust their screen resolution this message is displayed in Control Panel:
"The display settings can't be changed from a remote session."
We don't want to use the "make text and other items larger or smaller" scaling feature, as this produces undesirable results with some of our applications. We also don't want to have to support multiple types of RDP clients or RDP shortcut
files.
We have looked at other posts but can't find an answer that applies to Windows Server 2012 R2. The closest thing we could find is KB2726399, but it only applies to Server 2008.
Does anybody have a solution for Server 2012?
Thanks

Hi,
Currently you cannot change the resolution from within the session. This is normal and expected behavior.
Unfortunately this means you need to set the desired resolution before connecting by using custom .rdp files, manually within the Remote Desktop Client, custom web launch page, custom windows launch program, etc.
-TP

Android Multiple Screens

Hi,
I was wondering if it is possible with Adobe air to allow for multiple screens in Android. I have a HTC Incredible and a Galaxy Nexus both of which support video out. Android currently only supports mirroring for Video out. I wanted to know if it would be possible for adobe air to recognize the video out of the device as an external display that use either a MHL HDMI Out (Galaxy Nexus) or Analog-Composite video out (HTC Incredible). To illustrate a scenario that would use this: let say the app is a gallery and has x amount of pictures. The user has a video out cable connected and is recognized as the second monitor. Once the user sees a picture they like they would click on the image. Once the image is clicked it is sent to the 2nd display (the video out of the Android device) so the picture is being displayed on the larger screen while the user is still free to browse the pictures. Is this in realm of Adobe Air capabilities? Or am I misinterpreting "Multiscreen Development"?
Thanks,
-Nick

Hello,
Anyone have information about this problem ? I have warning about hight resolution for tablet when I publish my application on Android Store ?
Thanks for you help.

24"iMAC optimal screen resolution for photo processing

I have a 24" iMAC (matte) and do mostly photo editing. What is the optimal screen resolution for photo processing work?
thanks
a/d/

All Screens are 72 dpi (dots per inch- in reference to pixels) no matter what screen resolution you use. The only difference the screen resolution will make is the size of the photo when you are viewing. Higher resolution means the picture will take up less space in you work area, but you will most likely have to zoom in to edit finer areas. Lower resolution will cause the picture you are editing to take up more of your work space and to see multiple photos side by side you will have to zoom out of fron the photos. So, really the choice is up to you.
When creating the original document, this is where you need to monitor the dpi. The higher the dpi, the clearer your photo will look in print. A high dpi also means more disk space is being taken up by the photo. Generally a good dpi for print is 300 dpi. Anything that is only purposed for a screen based project (i.e. internet logos) should be saved at 72 dpi. Why use disk space and cause your pages to take longer load if no one will be able to tell the difference on screen between 72 and 300 dpi?
Hope this helps!

Facebook screen resolution changes automatically everytime on Mozilla Firefox 4. Other websites opens fine.

I have recently updated to Firefox 4. I am having many problems with this version.
I am unable to use Facebook properly. The Facebook screen resolution changes every time automatically. The screen resolution gets very big.
When I open the FB site the resolution will be fine as soon I open another tab to check other website and roll back to the FB tab the screen resolution gets big and can't get back to normal view.
I have to close the FB tab and open a new tab to put the FB URL to use it. When I try to view other tabs and then open the FB tab the screen resolution is changed.
I have problem with only FB on Firefox 4, other websites are working fine.
I also tried opening FB on IE8 and Chrome. Their the site is opening normal. Have no issues with their browsers. I spotted it to be a problem with Firefox 4 and also the IDM (Internet Download Manager) doesn't work on the FF4 where it used to work on the earlier version of FF.
Do something about the IDM integration with FF4 to download FLV,MP4 videos from YouTube and other websites.
There is no "Go back to multiple pages" button in a FF4 tab. It only allows us to go back to the previous page. If I have open 10 pages in a single tab then I have to click the back button 10 TIMES to open the last (10th page) but in the previous FF3 there is a facility to view all the pages in a drop down which the current version of FF4 doesn't have :-( I am using Windows XP 2 Professional 32-bit and owner of the computer.
Please fix the issues asap else I have to move back to the earlier version or have to shift to some other browser :
Here goes the screenshots :
http://i55.tinypic.com/2s8s8c6.jpg
http://i51.tinypic.com/j7vynq.jpg
http://i55.tinypic.com/1yuwbq.jpg

Reset the page zoom on pages that cause problems: <b>View > Zoom > Reset</b> (Ctrl+0 (zero); Cmd+0 on Mac)
* http://kb.mozillazine.org/Zoom_text_of_web_pages

|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).

Client Screen Resolution

Hello-
I think there may not be a way around this but i figured Id ask.
I have a 13" MacBook, my fiance a 24" iMac.
Trying to use Illustrator on my baby screen is no fun at all. I dont have the right hardware to try to connect my mac to his and use his screen as a monitor (could I even do that?)
I was looking for and option without having to buy a monitor.
I installed ARP (3.3) on his computer and connected to mine, looks great and is not really a delay that I thought there would be.
But I didn't think that the screen resolution would be limited to what the laptop can handle 1280 x 800
any trick or work around to be able to view my screen on the laptop as large as his monitor (1920 x 1200)
Hope I explained well.
Thanks!
Jennifer

Toggling the "fit screen in window" button will change between a scaled and a scrolling view of the target machine.

Screen Resolution for ALL monitors

IN FLASH MX, I set my screen resolution to 760px (width) x
560px (height). My monitor screen resolution is 1152x864. It looks
fine at that monitor screen resolution. HOWEVER, the website looks
h-u-g-e on monitor screen resolution 1024x768. It looks elongated
on monitor screen resolution 1280x768.
So I am wondering what is the best screen resolution to set
when in Flash? that will look good on all monitor screen
resolutions?
[email protected]

I have four files that show my settings plus another file
that shows the code that comes automatically. Not sure how to
attach the files with this reply.
My monitor setting is 1152x864. My movie setting is 760x560.
I am not sure what you mean by embedding in HTML. I thought
that came automatically.
My movie might be 760x560 but on a monitor screen 1024x768,
my site is huge because the screen is smaller. And on a monitor
screen 1280x768, my site becomes elongated.
I am working solely in Flash, no Dreamweaver. I thought the
target to HTML is automatic.
I need to solve the situation of being huge on 1024x768 and
the situation of becoming elongated on 1280x768.
[email protected]

Targeting multiple screen resolutions

Similar Messages

Maybe you are looking for