Dynamic Screen Resolution

Hello Everyone!!! I am having tough times solving query on Dynamic Screen Resolution in J2ME. How can you create an application in J2ME that automatically adjusts to the screen resolution to the phone it is being installed. That means if the resolution is small the layout automatically adjusts to the screen resolution and if its bigger then accordingly... Please help....

If you can use a UI framework/toolkit I suggest LWUIT. If not, code using proportions. Avoid absolute values of x, y, width and height. I made a sample at http://smallandadaptive.blogspot.com/2010/12/bar-chart.html

Similar Messages

How to set Dynamic screen resolution in flex..?

Hi All.,
I am developing a flex application in adobe flex4. to set the application height is 100% width is 100% and using <flexmdi:MDICanvas> to set the height 780 ,so application get displayed on normal window correctly., But i try to press f11 key the screen size is expanded at the time application size is set exactly, MdiCanvass size is not expanding on screen resolution.
My question is how can I make sure that the application should look uniform across different platform/different browsers and different monitors to display screen resolution auto adjust in mdi canvass also.
With Regards.,
LinFlex-

Hi,
Use the below syntax...
CALL TRANSACTION tcode... OPTIONS FROM opt
... OPTIONS FROM opt
Effect
Allows you to control processing using the values of the componetns of the structure opt, which must have the ABAP Dictionary type CTU_PARAMS. The components have the following meanings:
DISMODE
Display mode (like the MODE addition)
UPDMODE
Update mode (like the UPDATE addition)
CATTMODE
CATT mode (controls a CATT)
CATT mode can have the following values:
' ' No CATT active
'N' CATT without single-screen control
'A' CATT with single-screen control
DEFSIZE
Use default window size
RACOMMIT
Do not end transaction at COMMIT WORK
NOBINPT
No batch input mode (that is, SY-BINPT = SPACE)
NOBIEND
No batch input mode after the end of BDC data.
The components DEFSIZE , RACOMMIT, NOBINPT, and NOBIEND always take the following values:
'X' Yes
' ' No
If you do not use the OPTIONS FROM addition, the following control parameter settings apply:
DISMODE
From addition MODE
UPDMODE
From addition UPDATE
CATTMODE
No CATT active
DEFSIZE
Do not use default window size
RACOMMIT
Successful end on COMMIT WORK
NOBINPT
Batch input mode active ( SY-BINPT = X
NOBIEND
Batch input mode remains active after the BDC data
Jogdand M B

Dynamically set Screen Resolution...

Hi All,
Does anybody have an idea of whether its possible to set the screen resolution when starting an Java application and how you would go about doing it?

Hi All,
Does anybody have an idea of whether its possible to set the screen resolution when starting an Java application and how you would go about doing it?

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

Screen resolution problem for components in a canvas

Hi,
I am developing a Flex application, and I am using more than
one canvases in a single page(with in application tag).
And one canvas has elements like Chart, datagrid, legent
& a label.
Width & Height I gave to canvas and all its elements
(except legend & label) is in percentages
The problem I am facing is that,
when I change the screen resolution, and
when I press F11(full screen) in IE, the all objects except
legend & label are increasing/decreasing, and in some cases
lagend & label are overlapping in the chart & data grid.
Could anybody please advise what I need to follow to
eliminate these kind of problems.
Thanks in advance.
Pavan

Ooooooh, haha my bad, I didn't realize you were talking about
relative positioning on your app.
Here's what's happening. Your component/application is in
ABSOLUTE layout mode, so you can specify coordinates for where
controls and components should be placed. When the size of the
application changes, these coordinates are hard-coded, and they
will always display in the same place, which can case them to run
into components that have been resized to fit the new application
size. Now fixing those numbers is not easy. In fact, I don't know
of any way to make those numbers dynamic so they adjust when the
application size adjusts.
Instead, I suggest using constraints or Vbox/Hbox rather than
hardcoded coordinates. With constraints, you can specify how far
your Legend component is from the edges of the container it's in.
Or, you can use the VBox or HBox so your component is always in the
place it needs to be.
<mx:HBox width="80%" height="50%" top="10" left="10">
<mx:PieChart id="piechart1">
<mx:series>
<mx:PieSeries displayName="Series 1" field=""/>
</mx:series>
</mx:PieChart>
<mx:Legend dataProvider="{piechart1}"/>
</mx:HBox>
In this example, You can see I set top and left to 10. This
means that my HBox will be exactly 10 pixels from the top and left
side of my application (or container, or whatever it's confined
to). The Piechart and Legend fit neatly inside the HBox, and
because it's an HBox, they will be side by side horizontally.
If you need spacing between your chart and legend, you can
always use the Spacer control under Layout.
<mx:HBox width="80%" height="50%" top="10" left="10">
<mx:PieChart id="piechart1">
<mx:series>
<mx:PieSeries displayName="Series 1" field=""/>
</mx:series>
</mx:PieChart>
<mx:Spacer width="100%"/>
<mx:Legend dataProvider="{piechart1}"/>
</mx:HBox>
As you can see, the Spacer control is separating our chart
and the Legend by a width specified. Always use a percentage here,
as you'll run into problems I talked about in my previous post.
100% means the chart and the Legend will be as far away as they can
be while staying within the Hbox container. If you decreased it to
50%, they would only be half as far away.
Hope this helps.
EDIT:
One last example of a pie chart and a Legend within a canvas.
Each object has constraints to the canvas, which lets us put them
whereever we want within the canvas:
<mx:Canvas x="0" y="0" width="80%">
<mx:PieChart id="piechart1" left="10" top="10">
<mx:series>
<mx:PieSeries displayName="Series 1" field=""/>
</mx:series>
</mx:PieChart>
<mx:Legend dataProvider="{piechart1}" right="10"
bottom="10"/>
</mx:Canvas>
From this example, the chart will always line up to be 10
pixels from the top and left of our canvas. The Legend however,
will always line up to be 10 pixels from the right side and bottom
of our canvas. Adjusting the canvas size, the chart size, or the
legend size will give you the desired distance between these two
objects.

Screen resolution gone poor in Mac Mini

I cannot get optimum resolution on my Mac Mini. Just a day before I disconnected all the cords, including power and HDMI, just to move my Mac Mini (OS X 10.9.4) to a different room, and connected it back as it was. (Really speaking only two cords) and now I can't seem to get my screen resolution back.
The earlier screen resolution was there since I connected my Mac Mini for the first time to the LCD TV screen and I never had to deal with any resolution settings, but I am clueless now why I can't SET and SAVE optimum screen resolution settings. Here is screen capture for my System Preferences -> Display settings
I also have DISPLAYMENU app which gets me to a better screen resolution now, but it seems I do not have any option to save that configuration so every time I restart my Mac Mini, the display will go back to its weird screen resolution state and I have to start from all over again to get it back in a good viewable screen resolution with the help of DISPLAYMENU. I have contacted Apple Support and have done resetting SMC and PRAM and entering in to SAFE-BOOT as well; nothing seems to help here. Any other suggestions? (I cannot accept that it is LCD TV problem because 1. Earlier it was working absolutely FINE. 2. I have my xbox connected to same LCD TV and I am getting screen resolution what I was getting earlier.)

Backlight
Direct LED
Refresh Rate
60Hz
Resolution
720p
Dynamic Contrast Ratio
100,000:1
Display Aspect Ratio
16:9
Display Resolution
1366x768
Colors:
16.7 million
This is what I found on manufacturer's website for the TV model I have. I do not remember exactly what was the resolution earlier but it was definitely not 720 (in earlier image). All I know is I can observe the difference in the screen resolution.
Also I have tried all sort of setting and resettings; (I was on chat with Apple support over an about 45 mins and on phone call around the same time.)
Also, I cannot accept that I might be using wrong connectors/adapters/TV not compatible to the resolution I am trying to get to; because it was working absolutely fine just few days before and as mentioned I have connected my xbox to the same TV, which works absolutely fine.

Panel collection with auto height for different screen resolution

Hi.
I created a page using panel collection by default height for 1024 * 768 screen resolution and works fine. When I change the screen resolution to 1152 * 864 then my page layout changes as I can see lot more space at bottom due to fixed height define for panel collection.
Here my question is how to make height as dynamic for panel collection which can changed based on screen resolution. Usually percentage for height attribute resolve the issue but JDev 11.1.1.4.0 doesn't support percentage its allows only pixel or em.
Please let me know to resolve this issue.
Thanks

If you want a table to occupy 80% of the height of the screen you should be able to do this with assigining % to the various panelStretch facets - like this:
    <af:form id="f1">
      <af:panelStretchLayout id="psl1" topHeight="10%" bottomHeight="10%">
        <f:facet name="bottom">
          <af:spacer width="10" height="1" id="s2"/>
        </f:facet>
        <f:facet name="center">
          <af:panelCollection id="pc1">
            <f:facet name="menus"/>
            <f:facet name="toolbar"/>
            <f:facet name="statusbar"/>
            <af:table var="row" rowBandingInterval="0" id="t1">
              <af:column sortable="false" headerText="col4" id="c1">
                <af:outputText value="#{row.col4}" id="ot1"/>
              </af:column>
              <af:column sortable="false" headerText="col5" id="c2">
                <af:outputText value="#{row.col5}" id="ot2"/>
              </af:column>
            </af:table>
          </af:panelCollection>
        </f:facet>
        <f:facet name="start"/>
        <f:facet name="end"/>
        <f:facet name="top">
          <af:spacer width="10" height="1" id="s1"/>
        </f:facet>
      </af:panelStretchLayout>
    </af:form>

What Screen Resolution should I Design For?

Hi,
For APEX applications in public sites, what should be the proper screen resolution should I design for? Also, when I put something like a chart in a region, the size of the chart is always fixed. Therefore, it may not fit a particular screen size. I am wondering what should be the proper screen resolution I should target for - considering different desktop monitors and tablets?
Thanks.

Hi,
sky123 wrote:
For APEX applications in public sites, what should be the proper screen resolution should I design for? The resolution is not the only problem. Users can use CTRL+ and CTRL- to dynamically zoom in / out the page!
Also, when I put something like a chart in a region, the size of the chart is always fixed. Therefore, it may not fit a particular screen size. I think it is OK to have some elements with a fixed size, like charts and images, while the rest of the page resizes itself. Charts are a problem because I don't think you can give them a "width=100%" as you can do with images. I think it depends on your audience. If only 5% of users will see the page in a small screen, you should use a big chart, and vice-versa. Or have two charts, one big and one small, and dynamically hide/show them based on the screen size?
If you use Apex 4.2, it has very interesting themes. For instance, I was surprised to see how fluid this page I created was:
http://apex.oracle.com/pls/apex/f?p=65861:3:0::NO::P3_ROWID:AAjQ4rAGlAAAADUAAB
If you make the browser window narrow enough, the order items region will move underneath the customer orders region... Cool! :)
(using CTRL+ to make the page bigger doesn't do the trick though...)
Luis

Auto adjust to screen resolution

I'm pretty new to Flash and am working on a background for my website (not online yet). i was wondering how others have designed applications, such as photo galleries, that automatically adjust to the resolution of the screen on which it's being viewed, as opposed to adding or removing scroll bars to view just a standard, presized bg image, as in HTML.
I assume this is a certain line of ActionScript, but like I said, I'm pretty new and am basically just guessing.
Thanks for your help.

Using 100% width and 100% height in the HTML Publish settings will get you started. You may want to review Flash "Scaling" and "aspect ratio" here:
Here are examples of different scaling parameters available in the Publish settings. You can also add these parameters directly in the html (<param name="scale" value="noscale"). All the examples replace the actual Flash dimensions with 100% for both width and height (width="100%" height="100%"). These examples use the old <object> and <embed> to illustrate the different ways to scale Flash. Once you understand how it works I’d recommend that you use swfobject to place the Flash in your final project.
View the source code for each page to see the full code.
http://www.cidigitalmedia.com/tutorials/scale/exact_fit.html
"exactFit" scales the file to fit exactly within the confines of the screen, irregardless if the movie becomes consequently distorted. The original aspect ratio is not maintained. So round things are not round and squares are not square.
http://www.cidigitalmedia.com/tutorials/scale/noScale.html
"noScale" is the default setting, and causes the movie to be displayed at the originally designed dimensions.
http://www.cidigitalmedia.com/tutorials/scale/no_border.html
"noBorder" causes the movie to be scaled to what ever dimensions are needed to have no border surrounding the movie within the player, which consequently could result in some of the movie being cut off from view. In other words, the movie will maintain the original aspect ratio and will fill the screen completely. But if the movie has to be streched wider to fill both sides of the screen, it will also stretch taller, but then some of the top and the bottom of the movie may be cut off from view.
http://www.cidigitalmedia.com/tutorials/scale/show_all.html
"showAll" scales the movie to the size of the screen (which could cause pixelation if the file contains raster information), the difference between showAll and exactFit is that showAll mantains initial movie size proportions. Because it maintains the original aspect ratio, there can be space to the sides or the top and bottom. But everything always shows and they are not distorted. But notice the photo in the center, it becomes pixilated at larger screen resolutions.
The trickiest part of trying to go full screen is that it’s difficult to make the Flash wider without making it taller also, that is, to maintain the correct proportions or aspect ratio of everything on the stage. These methods are just simple scaling accomplished with html. There are also methods to dynamically scale the stage and it’s elements using Actionscript… but that’s a much more complex undertaking.
Best wishes,
Eye for Video
www.cidigitalmedia.com
Best of luck!
Adninjastrator

Controlling Remote Session Screen Resolution

Is there a way to turn off dynamic resolution update for rdp connections (outside of the checkbox on the connection itself)?
It would be best if we could either disable the client system form sending the resolution info to the connections, or manually set the parameters that are being sent to the client.
Thank you,

Hi Daniel,
Thank you for posting in Windows Server Forum.
You can control the remote session screen resolution by two ways. When you connect you “Remote Desktop connection” in Display Tab you can adjust the screen resolution. And apart from that you can edit the .RDP file of server (with Notepad) which you need to
take remote session by “Desktop Height and width” setting. Please refer following article for more information.
RDP Settings for Remote Desktop Services in Windows Server 2008 R2
http://technet.microsoft.com/en-us/library/ff393699(v=ws.10).aspx
Hope it helps!
Thanks.
Dharmesh Solanki

Bridge - How to view image in full screen resolution

In Bridge - How to view an image in full screen resolution and not as a Preview (Space bar), like in Lightroom (F), Photoshop or ViewNX 2 ?

The size of the Bridge Preview window will always be the absolute limit of the image display in Bridge. Maybe I am not following you. Sorry

DB does not look the same in different screen resolutions

Hi All -
I have built my dashboards using the Windows screen resolution 1024 x 768, and exported the dashboard into powerpoint. With this resolution the dashboard looks normal. I then changed my Windows screen resolution to 1280 x 1024, opened the ppt slideshow and my X-axis labels are being cut off. The labels are written vertically (ex: 06/09/09).
Does anyone know why this could be happening?
Thanks!
Tracy

I am experiencing the exact same thing. The width of the tabs in the layout editor is varied depending on the length of the text. However, at run-time, the width of the tabs is fixed, causing the tabs to be wider than the window and a set of VCR buttons to appear in the upper right corner of the canvas. Personally, I think this is a Forms bug. Why would they intentionally let us set the width to variable at design-time only to force a fixed width at run-time?

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

Using Mini DisplayPort to VGA, screen resolution distorts. How do I fix?

When I use my Mini DisplayPort to VGA adapter, the resolution gets too big for my screen (mbpro 15") and the same thing appears on the projector I use. I'm not sure if I should change my screen resolution while I use the projector or what?
Also, the first (and only) time I used it, it seemed as if the signal wouldn't even send. After a while of fiddling around, the screen finally showed up on the projector (distorted) but we didn't do anything different to change that. It just kind of did it on it's own. Is this common for "first uses" or will this happen every time?
I plan on using this again Friday.

Welcome! If you have mini displayport, you should try the appropriate discussion group for your newer machine:
http://discussions.apple.com/category.jspa?categoryID=251
Although some things are very similar to the original Macbook Pro, many are not.

How to turn off "screen resolution" warning in iPhoto?

I am running OS X Yosemite 10.10.1 on a Mac mini (Late 2012), 2.3 GHz, 4 GB memory, iPhoto version 9.5.1 (902.17). I get the "screen resolution not optimal for iPhoto" warning repetitively about once every 15 minutes as long as iPhoto is running. I have set the resolution to my preference and I don't mind seeing this warning once when I start iPhoto, but it gets annoying. How can I set iPhoto to stop doing this?

I am running OS X Yosemite 10.10.1 on a Mac mini (Late 2012), 2.3 GHz, 4 GB memory, iPhoto version 9.5.1 (902.17). I get the "screen resolution not optimal for iPhoto" warning repetitively about once every 15 minutes as long as iPhoto is running.
Is there a reason, why you do not update to the Yosemite compatible version iPhoto 9.6? I never get the warning, you are reporting, if the iPhoto window can fit the screen, with MacOS X 10.10.2 and iPhoto 9.6.1.

Dynamic Screen Resolution

Similar Messages

Maybe you are looking for