TooltipText used with dual screen problem

Hi,
In my application I use a dual screen, so JComponent may be either on one screen or the other.
My problem is when the mouse rolls over a JComponent on the right screen, the Tooltiptext associated is displayed onto the left screen.
Any idea if I could display it automatically on the good screen or if I have to implement myself the display ?
Thx for advance

Did you get any resolution to your question? I have the Samsung monitor almost like yours, and I posted two seconds ago. I think I have a similar problem. I had been using my Samsung with my PC, and just switched to Mac. I loved my Samsung, but now ,for the first time using as a second. Hooked up to mini dvi to dvi, and reported a glow, or tinge coming around any window that I may place on the Samsung.Also, when Ilook at the background around the window I can see that the resolution is not perfect and is breaking up a little. Did you try VGA? and did it help? Curious to know

Similar Messages

  • Problem with dual screen (24" imac 2006 ver)

    hi
    i've got a 24" intel imac (2006 ver) and i've connected it using apple's mini-dvi => vga adapter to my 2nd 22" lcd monitor, a samsung 2232GW, which is set to 1680 x 1050.
    however, the samsung lcd displays (when i'm using as dual screen) is quite blur and double imaged. quality is readable but very irritating. i'm also using the same monitor for my ps3 (uses the DVI side) and have no problem with any visual aspect. I've tried playing around with the settings like resolution and calibration and tuning but didn't help at all.
    anyone might have any ideas and enlighten me on this issue?
    thanks
    Message was edited by: Treon

    Did you get any resolution to your question? I have the Samsung monitor almost like yours, and I posted two seconds ago. I think I have a similar problem. I had been using my Samsung with my PC, and just switched to Mac. I loved my Samsung, but now ,for the first time using as a second. Hooked up to mini dvi to dvi, and reported a glow, or tinge coming around any window that I may place on the Samsung.Also, when Ilook at the background around the window I can see that the resolution is not perfect and is breaking up a little. Did you try VGA? and did it help? Curious to know

  • I would like to know if there a way to use window (via bootcamp) and use a dual screen with the use of thunderbolt?

    I would like to know if there a way to use window (via bootcamp) and use a dual screen with the use of thunderbolt?

    There are very specific requirements for using an iMac as an external display.
    From Target Display Mode: Frequently Asked Questions (FAQ) - Apple Support
    What are the requirements for TDM?
    A Mac notebook or desktop with a Mini DisplayPort or Thunderbolt connection
    A Thunderbolt or Mini DisplayPort cable
    A supported iMac with OS X 10.6.1 or later. The table below shows iMac computers that support TDM, the required cables, and the port of the computer to which you are connecting the iMac.
    iMac Model
    Cable Supported
    Port on Source Computer
    iMac (27-inch Late 2009)
    Mini DisplayPort to Mini DisplayPort
    Mini DisplayPort or Thunderbolt
    iMac (27-inch Mid 2010)
    Mini DisplayPort to Mini DisplayPort
    Mini DisplayPort or Thunderbolt
    iMac (Mid 2011)
    Thunderbolt to Thunderbolt
    Thunderbolt
    iMac (Mid 2012 and later)
    Thunderbolt to Thunderbolt
    Thunderbolt
    Note that the iMac (Retina 5K, 27-inch, Late 2014) does not support Target Display Mode.

  • Dual screen problems after last updates

    Hello everyone,
         it was long time since our Arch gave me some problems, but then now I'm fighting furiously with dual screen configuration with new gnome. Let me explain.
    I upgraded the home PC that I hadn't update for months, so I updated more or less everything ... kernel, nvidia drivers, gnome, etc..
    The PC has always been dual screen (no twin view, without xinerama), two screens (one on a LCD monitor and one on a TV) where I could run separate applications independent.
    Now, after the update, when I launch any application in the second screen (the TV) it starts on the first (screen).
    Obviously I have't made any changes to xorg.conf before and after the upgrade. I also tried to recreate one with the nvidia-tools but nothing ...
    Can you help me? Someone had the same problem?
    I post my xorg.conf, I hope that someone has a hint. I can no longer watching movies on TV and it is very annoying!
    # nvidia-settings: X configuration file generated by nvidia-settings
    # nvidia-settings: version 1.0 (buildmeister@builder63) Wed Oct 1 15:10:25 PDT 2008
    # Auto-generated by Archie mkxcfg
    # Auto-generated by Archie mkxcfg
    #Section "DRI"
    # Mode 0666
    #EndSection
    Section "ServerLayout"
    # PS/2 Mouse not detected
    # Serial Mouse not detected
    Identifier "Xorg Configured"
    Screen 0 "Screen0" 1024 0
    Screen 1 "Screen1" LeftOf "Screen0"
    InputDevice "Keyboard0" "CoreKeyboard"
    InputDevice "USB Mouse" "CorePointer"
    EndSection
    Section "Files"
    # Additional fonts: Locale, Gimp, TTF...
    # FontPath "/usr/share/lib/X11/fonts/latin2/75dpi"
    # FontPath "/usr/share/lib/X11/fonts/latin2/100dpi"
    # True type and type1 fonts are also handled via xftlib, see /etc/X11/XftConfig!
    RgbPath "/usr/share/X11/rgb"
    ModulePath "/usr/lib/xorg/modules"
    FontPath "/usr/share/fonts/misc:unscaled"
    FontPath "/usr/share/fonts/misc"
    FontPath "/usr/share/fonts/75dpi:unscaled"
    FontPath "/usr/share/fonts/75dpi"
    FontPath "/usr/share/fonts/100dpi:unscaled"
    FontPath "/usr/share/fonts/100dpi"
    FontPath "/usr/share/fonts/PEX"
    FontPath "/usr/share/fonts/cyrillic"
    FontPath "/usr/share/fonts/Type1"
    FontPath "/usr/share/fonts/ttf/western"
    FontPath "/usr/share/fonts/ttf/decoratives"
    FontPath "/usr/share/fonts/truetype"
    FontPath "/usr/share/fonts/truetype/openoffice"
    FontPath "/usr/share/fonts/truetype/ttf-bitstream-vera"
    FontPath "/usr/share/fonts/latex-ttf-fonts"
    FontPath "/usr/share/fonts/defoma/CID"
    FontPath "/usr/share/fonts/defoma/TrueType"
    EndSection
    Section "Module"
    # Load "type1"
    Load "ddc" # ddc probing of monitor
    Load "dbe"
    # Load "dri"
    Load "extmod"
    Load "glx"
    Load "bitmap" # bitmap-fonts
    Load "freetype"
    Load "record"
    # Load "synaptics"
    EndSection
    Section "ServerFlags"
    Option "AllowMouseOpenFail" "true"
    Option "Xinerama" "0"
    EndSection
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "keyboard"
    Option "CoreKeyboard"
    Option "XkbRules" "xorg"
    Option "XkbModel" "pc105"
    Option "XkbLayout" "it"
    Option "XkbVariant" ""
    EndSection
    Section "InputDevice"
    Identifier "Serial Mouse"
    Driver "mouse"
    Option "Protocol" "Microsoft"
    Option "Device" "/dev/ttyS0"
    Option "Emulate3Buttons" "true"
    Option "Emulate3Timeout" "70"
    Option "SendCoreEvents" "true"
    EndSection
    Section "InputDevice"
    Identifier "PS/2 Mouse"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "ZAxisMapping" "4 5"
    Option "Device" "/dev/psaux"
    Option "Emulate3Buttons" "true"
    Option "Emulate3Timeout" "70"
    Option "SendCoreEvents" "true"
    EndSection
    Section "InputDevice"
    Identifier "USB Mouse"
    Driver "mouse"
    Option "Device" "/dev/input/mice"
    Option "SendCoreEvents" "true"
    Option "Protocol" "IMPS/2"
    Option "ZAxisMapping" "4 5"
    Option "Buttons" "5"
    EndSection
    Section "Monitor"
    # Warning: This may fry old Monitors
    # Very conservative. May flicker.
    # VertRefresh 50.0 - 62.0 # Extreme conservative. Will flicker. TFT default.
    # Default modes distilled from
    # "VESA and Industry Standards and Guide for Computer Display Monitor
    # Timing", version 1.0, revision 0.8, adopted September 17, 1998.
    # $XFree86: xc/programs/Xserver/hw/xfree86/etc/vesamodes,v 1.4 1999/11/18 16:52:17 tsi Exp $
    # 640x350 @ 85Hz (VESA) hsync: 37.9kHz
    Identifier "Monitor0"
    VendorName "Unknown"
    ModelName "Samsung SyncMaster"
    HorizSync 30.0 - 81.0
    VertRefresh 56.0 - 75.0
    ModeLine "640x350" 31.5 640 672 736 832 350 382 385 445 +hsync -vsync
    ModeLine "640x400" 31.5 640 672 736 832 400 401 404 445 -hsync +vsync
    ModeLine "720x400" 35.5 720 756 828 936 400 401 404 446 -hsync +vsync
    ModeLine "640x480" 25.2 640 656 752 800 480 490 492 525 -hsync -vsync
    ModeLine "640x480" 31.5 640 664 704 832 480 489 491 520 -hsync -vsync
    ModeLine "640x480" 31.5 640 656 720 840 480 481 484 500 -hsync -vsync
    ModeLine "640x480" 36.0 640 696 752 832 480 481 484 509 -hsync -vsync
    ModeLine "800x600" 36.0 800 824 896 1024 600 601 603 625 +hsync +vsync
    ModeLine "800x600" 40.0 800 840 968 1056 600 601 605 628 +hsync +vsync
    ModeLine "800x600" 50.0 800 856 976 1040 600 637 643 666 +hsync +vsync
    ModeLine "800x600" 49.5 800 816 896 1056 600 601 604 625 +hsync +vsync
    ModeLine "800x600" 56.3 800 832 896 1048 600 601 604 631 +hsync +vsync
    ModeLine "1024x768" 44.9 1024 1032 1208 1264 768 768 776 817 +hsync +vsync interlace
    ModeLine "1024x768" 65.0 1024 1048 1184 1344 768 771 777 806 -hsync -vsync
    ModeLine "1024x768" 75.0 1024 1048 1184 1328 768 771 777 806 -hsync -vsync
    ModeLine "1024x768" 78.8 1024 1040 1136 1312 768 769 772 800 +hsync +vsync
    ModeLine "1024x768" 94.5 1024 1072 1168 1376 768 769 772 808 +hsync +vsync
    ModeLine "1152x864" 108.0 1152 1216 1344 1600 864 865 868 900 +hsync +vsync
    ModeLine "1280x960" 108.0 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync
    ModeLine "1280x960" 148.5 1280 1344 1504 1728 960 961 964 1011 +hsync +vsync
    ModeLine "1280x1024" 108.0 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync
    ModeLine "1280x1024" 135.0 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync
    ModeLine "1280x1024" 157.5 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync
    ModeLine "1600x1200" 162.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    ModeLine "1600x1200" 175.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    ModeLine "1600x1200" 189.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    ModeLine "1600x1200" 202.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    ModeLine "1600x1200" 229.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
    ModeLine "1792x1344" 204.8 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync
    ModeLine "1792x1344" 261.0 1792 1888 2104 2456 1344 1345 1348 1417 -hsync +vsync
    ModeLine "1856x1392" 218.3 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync
    ModeLine "1856x1392" 288.0 1856 1984 2208 2560 1392 1393 1396 1500 -hsync +vsync
    ModeLine "1920x1440" 234.0 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync
    ModeLine "1920x1440" 297.0 1920 2064 2288 2640 1440 1441 1444 1500 -hsync +vsync
    ModeLine "1800x1440" 230.0 1800 1896 2088 2392 1440 1441 1444 1490 +hsync +vsync
    ModeLine "1800x1440" 250.0 1800 1896 2088 2392 1440 1441 1444 1490 +hsync +vsync
    ModeLine "640x480" 43.2 640 680 744 848 480 481 484 509 -hsync +vsync
    ModeLine "768x576" 35.0 768 792 872 976 576 577 580 597 -hsync +vsync
    ModeLine "768x576" 42.9 768 800 880 992 576 577 580 601 -hsync +vsync
    ModeLine "768x576" 45.5 768 808 888 1008 576 577 580 602 -hsync +vsync
    ModeLine "768x576" 51.8 768 808 888 1008 576 577 580 605 -hsync +vsync
    ModeLine "768x576" 62.6 768 816 896 1024 576 577 580 611 -hsync +vsync
    ModeLine "800x600" 68.2 800 848 936 1072 600 601 604 636 -hsync +vsync
    ModeLine "1024x768" 113.3 1024 1096 1208 1392 768 769 772 814 -hsync +vsync
    ModeLine "1152x864" 81.6 1152 1216 1336 1520 864 865 868 895 -hsync +vsync
    ModeLine "1152x864" 119.7 1152 1224 1352 1552 864 865 868 907 -hsync +vsync
    ModeLine "1152x864" 143.5 1152 1232 1360 1568 864 865 868 915 -hsync +vsync
    ModeLine "1280x960" 124.5 1280 1368 1504 1728 960 961 964 1001 -hsync +vsync
    ModeLine "1280x960" 129.9 1280 1368 1504 1728 960 961 964 1002 -hsync +vsync
    ModeLine "1280x960" 179.0 1280 1376 1520 1760 960 961 964 1017 -hsync +vsync
    ModeLine "1280x1024" 191.0 1280 1376 1520 1760 1024 1025 1028 1085 -hsync +vsync
    ModeLine "1400x1050" 122.6 1400 1488 1640 1880 1050 1051 1054 1087 -hsync +vsync
    ModeLine "1400x1050" 149.3 1400 1496 1648 1896 1050 1051 1054 1094 -hsync +vsync
    ModeLine "1400x1050" 155.8 1400 1496 1648 1896 1050 1051 1054 1096 -hsync +vsync
    ModeLine "1400x1050" 179.3 1400 1504 1656 1912 1050 1051 1054 1103 -hsync +vsync
    ModeLine "1400x1050" 214.4 1400 1512 1664 1928 1050 1051 1054 1112 -hsync +vsync
    ModeLine "1600x1200" 280.6 1600 1728 1904 2208 1200 1201 1204 1271 -hsync +vsync
    Option "DPMS" "true"
    # HorizSync 28.0 - 78.0 # Warning: This may fry very old Monitors
    EndSection
    Section "Monitor"
    Identifier "Monitor1"
    VendorName "Unknown"
    ModelName "TV-0"
    HorizSync 28.0 - 33.0
    VertRefresh 43.0 - 72.0
    EndSection
    Section "Device"
    Identifier "Card0"
    Driver "nvidia"
    VendorName "All"
    BoardName "All"
    EndSection
    Section "Device"
    Identifier "Videocard0"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce 7300 LE"
    BusID "PCI:4:0:0"
    Screen 0
    EndSection
    Section "Device"
    Identifier "Videocard1"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce 7300 LE"
    BusID "PCI:4:0:0"
    Screen 1
    EndSection
    Section "Device"
    Identifier "Device0"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce 7300 LE"
    BusID "PCI:4:0:0"
    Screen 0
    EndSection
    Section "Device"
    Identifier "Device1"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce 7300 LE"
    BusID "PCI:4:0:0"
    Screen 1
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Device0"
    Monitor "Monitor0"
    DefaultDepth 24
    Option "TwinView" "0"
    Option "TwinViewXineramaInfoOrder" "CRT-0"
    Option "metamodes" "CRT: 1280x1024 +0+0; CRT: 1024x768 +0+0; CRT: 800x600 +0+0; CRT: 640x480 +0+0"
    SubSection "Display"
    Depth 24
    EndSubSection
    EndSection
    Section "Screen"
    # Removed Option "metamodes" "TV: nvidia-auto-select +0+0"
    Identifier "Screen1"
    Device "Device1"
    Monitor "Monitor1"
    DefaultDepth 24
    Option "TwinView" "0"
    Option "TwinViewXineramaInfoOrder" "TV-0"
    Option "metamodes" "TV: 1024x768 +0+0"
    SubSection "Display"
    Depth 24
    EndSubSection
    EndSection
    Writing the post a tried to install fluxbox, and then... all ok. In fluxbox all works fine. I think this is a problem related to the new gnome screen configurer.
    I post an image of gnome screen configurer vs nvidia-tools.
    Googling around I found that new gnome screen configuration (using xrandr) is not compatible with nvidia drivers. Could be this the source of the problem?
    Help please
    Last edited by frullino (2008-10-25 13:17:29)

    Hi,
    Does your Mac go to the sleep status when you close the cover? If so, the remote session can be terminated due to time out and the time out value may be redesigned in the latest versions.
    Thanks.
    Jeremy Wu
    TechNet Community Support

  • Hd 6570 i gb dual screen problem

    Good day all. 
    i have a problem with dual screens to my one pc. i am using a AMD Radeon HD 6570 gfx card. dual core 2.77ghz cpu and windows 7 professional 32 bit. The one screen is connected via VGA cable and the other screen is connected via DVI cable (no adapters) but the screens will only display individually and not as extended desktops.
    i have updated the graphics driver to the latest as well as the CCC and still no sucess.
    I know this is set up is possible because i have other pcs that are using VGA and DVI.
    These are the specs of the pc
    Windows version: windows 7 professional
    64 or 32 bit : 32 bit
    Power supply watts : 300w 
    Memory type, model number and amount: apacer 2 gb unb pc2-6400 cl5
    VGA driver Version : 8.930.0.0   
    Chipset driver Version : 6.1.7600.16385
    CPU : Pentium ( R ) dual core  cpu E5400 @ 2.70 GHz
    Bios version : V02.61
    Gpu : hd 6570 1 gb
    Your assistance will be greatly appreciated

    Please have a look at the AMD configurator for two or more screens on a video card.
    http://www.amd.com/us/products/technologies/amd-eyefinity-technology/how-to/Pages/how-to.aspx
    and
    http://www.amd.com/us/products/technologies/amd-eyefinity-technology/how-to/Pages/set-up.aspx
    Quote
    To enable support for more than 2 monitors, “active” DisplayPort™ adapters/dongles are required (or monitors with direct DisplayPort™ connectivity must be used).

  • Is it possible to connect my mid 2010 Macbook Pro with my 21.5" iMac 11,2 so that I can work with dual screens?

    Is it possible to connect my mid 2010 Macbook Pro with my 21.5" iMac 11,2 so that I can work with dual screens?

    try xxx - may work
    _may_ work.

  • Xmonad with dual screen strange bug or feature !

    Hi,
    I am running xmonad with dual screen. The strange thing (bug or feature) I noticed that when I move a window to another screen and then try to change the workspace, the window moves along to the same workspace but lands on the other screen.
    Is there any way to switch off this feature. I googled a bit and replaced the greedyView parameter with view but it didn't help.
    regards,
    Hardik

    Here is my  xmonad.hs
    import XMonad
    import System.Exit
    import qualified XMonad.StackSet as W
    import qualified Data.Map as M
    import XMonad.Util.Run
    import XMonad.Hooks.DynamicLog
    import XMonad.Hooks.ManageDocks
    import XMonad.Layout.NoBorders
    import XMonad.Hooks.SetWMName
    import XMonad.Hooks.ManageHelpers (isFullscreen, doFullFloat, doCenterFloat)
    import XMonad.Layout.Tabbed
    import System.IO
    -- -xos4-terminus-medium-r-*-*-14-*-*-*-*-*-*-*
    myLauncher :: String
    myLauncher = "`dmenu_path | dmenu -fn '-xos4-terminus-medium-r-*-*-14-*-*-*-*-*-*-*' -nb '#303030' -nf '#959595' -sf '#FFFFFF' -sb '#606060'`"
    myKeys conf@(XConfig {XMonad.modMask = modMask}) = M.fromList $
    [ ((modMask .|. shiftMask, xK_Return), spawn $ XMonad.terminal conf)
    , ((modMask, xK_p ), spawn myLauncher)
    , ((modMask .|. shiftMask, xK_c ), kill)
    , ((mod4Mask .|. controlMask, xK_Down ), spawn "/home/hardik/bin/decrease-aumix-vol.sh")
    , ((0 , 0x1008ff11 ), spawn "/home/hardik/bin/decrease-aumix-vol.sh")
    , ((mod4Mask .|. controlMask, xK_Up ), spawn "/home/hardik/bin/increase-aumix-vol.sh")
    , ((0 , 0x1008ff13 ), spawn "/home/hardik/bin/increase-aumix-vol.sh")
    , ((mod4Mask .|. controlMask, xK_m ), spawn "/home/hardik/bin/toggle-aumix-mute.sh")
    , ((0 , 0x1008ff12 ), spawn "/home/hardik/bin/toggle-aumix-mute.sh")
    , ((modMask, xK_space ), sendMessage NextLayout)
    , ((modMask .|. shiftMask, xK_space ), setLayout $ XMonad.layoutHook conf)
    , ((modMask, xK_n ), refresh)
    , ((modMask, xK_Tab ), windows W.focusDown)
    , ((modMask, xK_j ), windows W.focusDown)
    , ((modMask, xK_k ), windows W.focusUp )
    , ((modMask, xK_m ), windows W.focusMaster )
    , ((modMask, xK_Return), windows W.swapMaster)
    , ((modMask .|. shiftMask, xK_j ), windows W.swapDown )
    , ((modMask .|. shiftMask, xK_k ), windows W.swapUp ) , ((modMask, xK_h ), sendMessage Shrink) , ((modMask, xK_l ), sendMessage Expand)
    , ((modMask, xK_t ), withFocused $ windows . W.sink)
    , ((modMask , xK_comma ), sendMessage (IncMasterN 1))
    , ((modMask , xK_period), sendMessage (IncMasterN (-1)))
    , ((modMask .|. shiftMask, xK_q ), io (exitWith ExitSuccess))
    -- , ((modMask , xK_q ), restart "xmonad" True)
    , ((modMask , xK_q ), spawn "killall conky dzen2 && xmonad --recompile && xmonad --restart")
    , ((modMask .|.shiftMask .|. controlMask , xK_c ), spawn "emacs ~/.xmonad/xmonad.hs")
    , ((modMask .|. controlMask , xK_l ), spawn "xscreensaver-command -lock")
    , ((modMask .|. controlMask , xK_k ), spawn "python ~/pythonScripts/SwitchKbLayoutDesk/src/setNextKbLayout.py")
    , ((modMask , xK_b ), sendMessage ToggleStruts)
    ++
    [((m .|. controlMask, k), windows $ f i)
    | (i, k) <- zip (XMonad.workspaces conf) [xK_F1 .. xK_F4]
    , (f, m) <- [(W.view, 0), (W.shift, shiftMask)]]
    -- , (f, m) <- [(W.greedyView, 0), (W.shift, shiftMask)]]
    ++
    -- mod-{w,e,r}, Switch to physical/Xinerama screens 1, 2, or 3
    -- mod-shift-{w,e,r}, Move client to screen 1, 2, or 3
    [((m .|. modMask, key), screenWorkspace sc >>= flip whenJust (windows . f))
    | (key, sc) <- zip [xK_w, xK_e] [0..]
    , (f, m) <- [(W.view, 0), (W.shift, shiftMask)]]
    myMouseBindings (XConfig {XMonad.modMask = modMask}) = M.fromList $
    [ ((modMask, button1), (\w -> focus w >> mouseMoveWindow w))
    , ((modMask, button2), (\w -> focus w >> windows W.swapMaster))
    , ((modMask, button3), (\w -> focus w >> mouseResizeWindow w))
    myLayouts = tiled ||| Mirror tiled ||| noBorders Full ||| simpleTabbedBottom
    where
    tiled = Tall 1 (2/100) (1/2)
    myManageHook = composeAll
    [ className =? "MPlayer" --> doFloat
    , className =? "Gimp" --> doFloat
    , className =? "Gimp" --> doFloat
    , className =? "IDEA" --> doFloat
    , resource =? "desktop_window" --> doIgnore
    , isFullscreen --> doFullFloat ]
    myStartupHook :: X ()
    myStartupHook = do
    setWMName "LG3D"
    spawn "xset -b"
    spawn "xrdb -load ~/.Xdafaults"
    spawn "xscreensaver -no-splash"
    spawn "numlockx on"
    spawn "eval `cat $HOME/.fehbg`"
    spawn "conky -c ~/.conkyrc_dzen | dzen2 -ta r -x 600 -bg '#303030' -fn '-*-lucida-*-*-normal-*-12-*-*-*-*-*-*-*' &"
    spawn "conky &"
    -- spawn "conky -c ~/.conkyrc_time &"
    shortened :: Int -> String -> String
    shortened n xs | length xs < n = xs
    | otherwise = (take ( n - length end) xs) ++ end
    where
    end = "..."
    main = do
    h <- spawnPipe "dzen2 -w 600 -ta l -fn ' -*-lucida-*-*-normal-*-12-*-*-*-*-*-*-*' -bg '#303030' -fg '#FFFFFF'"
    xmonad $ defaultConfig {
    terminal = "urxvt",
    focusFollowsMouse = True,
    borderWidth = 1,
    modMask = mod1Mask,
    workspaces = [" console "," dev "," misc "," browser "],
    normalBorderColor = "#303030",
    focusedBorderColor = "#55BBFF",
    keys = myKeys,
    mouseBindings = myMouseBindings,
    layoutHook = avoidStruts $ smartBorders myLayouts,
    manageHook = myManageHook <+> manageDocks,
    startupHook = myStartupHook,
    logHook = dynamicLogWithPP $ defaultPP {
    ppCurrent = wrap "^fg(#FFFFFF)^bg(#606060)" "^fg()^bg()"
    ,ppVisible = wrap "^fg(#FFFFFF)^bg()" "^fg()^bg()"
    ,ppHidden = wrap "^fg(#55BBFF)^bg()" "^fg()^bg()"
    ,ppHiddenNoWindows = wrap "^fg(#808080)^bg()" "^fg()^bg()"
    ,ppUrgent = wrap "^fg(#FF0000)^bg()" "^fg()^bg()"
    ,ppTitle = \x -> if null x
    then ""
    else "< ^fg(#FFFFFF)^bg()" ++ shortened 23 x ++ "^fg()^bg() >"
    ,ppLayout = \x -> "^fg(#FFBB00)^bg()"
    ++ case x of
    "Tall" -> "Tiled"
    "Full" -> "Full"
    "Mirror Tall" -> "Tiled Bottom"
    "Tabbed Bottom Simplest" -> "Tabbed"
    _ -> x
    ++ "^fg()^bg()"
    ,ppSep = " "
    ,ppWsSep = ""
    ,ppOutput = hPutStrLn h
    Last edited by rangalo (2010-04-22 14:52:13)

  • Problems with dual screens

    I am running an iMac 3.06 GHz, 4 GB RAM, 512 VRAM. I also use an external monitor connected via HDMI. When I run Color using dual screens the picture shows almost only black, and what isn't black is so saturated I can barely discern what the picture is. Does anyone know why this is happening and/or how I can fix it?

    I'm not sure Color works properly with monitors connected in that manner. Color isn't accurate without proper monitoring, and you can't get proper monitoring with an iMac. By proper monitoring I mean an HDTV or broadcast monitor being fed a VIDEO signal via a hardware capture card (AJA, Decklink, Matrox). You can't get capture cards to work on iMacs, therefore you cannot properly monitor a video signal.
    The display in the Color interface is not accurate at all. It is just a reference to see what frame you are on. It isn't designed to be used to judge the quality of the image. It has a much higher gamma (midrange) than is seen on the external monitor.
    I'm assuming the monitor you are using is being fed a converted HDMI signal...converted from the DVI or Mini Display port on the computer. Well, that is a computer signal...not a video one. There's a difference. So this setup will not work...not with Color.
    Sorry,
    Shane

  • Problems with dual screen in Lightroom 4

    I am getting very poor performance when using a secondary screen in Lightroom 4. I am using Lightroom 4 on a PC with  with Windows 7 64-bit on an Intel i7 860 @ 2.80 Ghz, 8 Mb RAM. Graphics card is a nVidia GE Force GTX 260 with updated drivers. Monitors are Samsung SyncMaster 226 and Asus ProArt 22". When in Develop module, the main screen, either on the Samsung or the Asus, goes randomly on and out. Sliders are quite sluggish, also, next to useless. Lightroom 3 works fine with the same catalog. Anybody knows a fix or a workaround?

    I'm seeing the same behaviour here with a dual-Xeon E5620 with 24GB of RAM and a decent video card running Win7 Pro x64. It's insanely annoying.
    This shouldn't be happening (it definitely wasn't happening with any of the other versions of LR I've owned), and renders LR4 completely unusable in that mode. It works again if I disable the second monitor, but that kind of defeats the purpose of having bought two identical monitors for photo editing...
    FWIW, I see lots of "Bezel" and "Shadow" items appearing and disappearing very quickly in the taskbar at the bottom of the screen, and regions of the display turn completely black for a few seconds, usually the top half of the photo being edited. The controls are unusable during that time and the entire application feels like it's frozen for a good 5-10 seconds before it unfreezes. Then the whole process repeats itself within a few seconds.

  • Any one help me with dual screen?

    I am trying to get my LCD monitor work, which is plugged in VGA.
    However, when i using "xrandr --output VGA --auto" to set it up, i get this failure "xrandr: cannot find crtc for output VGA"
    i am using intel graphic card, and the result of "xrandr -q --verbose" is as follows,
    Screen 0: minimum 320 x 200, current 1440 x 900, maximum 2960 x 1024
    VGA connected (normal left inverted right x axis y axis)
    Identifier: 0x3b
    Timestamp: 1278799
    Subpixel: unknown
    Clones:
    CRTCs: 0 1
    1360x768 (0x41) 84.8MHz -HSync +VSync
    h: width 1360 start 1432 end 1568 total 1776 skew 0 clock 47.7KHz
    v: height 768 start 771 end 781 total 798 clock 59.8Hz
    1152x864 (0x48) 81.6MHz -HSync +VSync
    h: width 1152 start 1216 end 1336 total 1520 skew 0 clock 53.7KHz
    v: height 864 start 865 end 868 total 895 clock 60.0Hz
    1024x768 (0x4c) 65.0MHz -HSync -VSync
    h: width 1024 start 1048 end 1184 total 1344 skew 0 clock 48.4KHz
    v: height 768 start 771 end 777 total 806 clock 60.0Hz
    800x600 (0x51) 40.0MHz +HSync +VSync
    h: width 800 start 840 end 968 total 1056 skew 0 clock 37.9KHz
    v: height 600 start 601 end 605 total 628 clock 60.3Hz
    640x480 (0x56) 25.2MHz -HSync -VSync
    h: width 640 start 656 end 752 total 800 skew 0 clock 31.5KHz
    v: height 480 start 490 end 492 total 525 clock 59.9Hz
    1440x900 (0x3f) 101.6MHz
    h: width 1440 start 1488 end 1520 total 1824 skew 0 clock 55.7KHz
    v: height 900 start 903 end 909 total 926 clock 60.2Hz
    LVDS connected 1440x900+0+0 (0x3f) normal (normal left inverted right x axis y axis) 0mm x 0mm
    Identifier: 0x3c
    Timestamp: 1278799
    Subpixel: horizontal rgb
    Clones:
    CRTC: 1
    CRTCs: 1
    PANEL_FITTING: full
    supported: center full_aspect full
    BACKLIGHT_CONTROL: kernel
    supported: native legacy combination kernel
    BACKLIGHT: 15 (0x0000000f) range: (0,15)
    1440x900 (0x3f) 101.6MHz *current +preferred
    h: width 1440 start 1488 end 1520 total 1824 skew 0 clock 55.7KHz
    v: height 900 start 903 end 909 total 926 clock 60.2Hz
    1440x900 (0x40) 106.5MHz -HSync +VSync
    h: width 1440 start 1520 end 1672 total 1904 skew 0 clock 55.9KHz
    v: height 900 start 903 end 909 total 934 clock 59.9Hz
    1360x768 (0x41) 84.8MHz -HSync +VSync
    h: width 1360 start 1432 end 1568 total 1776 skew 0 clock 47.7KHz
    v: height 768 start 771 end 781 total 798 clock 59.8Hz
    1152x864 (0x42) 143.5MHz -HSync +VSync
    h: width 1152 start 1232 end 1360 total 1568 skew 0 clock 91.5KHz
    v: height 864 start 865 end 868 total 915 clock 100.0Hz
    1152x864 (0x43) 121.5MHz +HSync -VSync
    h: width 1152 start 1216 end 1344 total 1568 skew 0 clock 77.5KHz
    v: height 864 start 865 end 868 total 911 clock 85.1Hz
    1152x864 (0x44) 119.7MHz -HSync +VSync
    h: width 1152 start 1224 end 1352 total 1552 skew 0 clock 77.1KHz
    v: height 864 start 865 end 868 total 907 clock 85.0Hz
    1152x864 (0x45) 108.0MHz +HSync +VSync
    h: width 1152 start 1216 end 1344 total 1600 skew 0 clock 67.5KHz
    v: height 864 start 865 end 868 total 900 clock 75.0Hz
    1152x864 (0x46) 105.0MHz -HSync +VSync
    h: width 1152 start 1224 end 1352 total 1552 skew 0 clock 67.6KHz
    v: height 864 start 865 end 868 total 902 clock 75.0Hz
    1152x864 (0x47) 96.8MHz -HSync +VSync
    h: width 1152 start 1224 end 1344 total 1536 skew 0 clock 63.0KHz
    v: height 864 start 865 end 868 total 900 clock 70.0Hz
    1152x864 (0x48) 81.6MHz -HSync +VSync
    h: width 1152 start 1216 end 1336 total 1520 skew 0 clock 53.7KHz
    v: height 864 start 865 end 868 total 895 clock 60.0Hz
    1024x768 (0x49) 94.5MHz +HSync +VSync
    h: width 1024 start 1072 end 1168 total 1376 skew 0 clock 68.7KHz
    v: height 768 start 769 end 772 total 808 clock 85.0Hz
    1024x768 (0x4a) 78.8MHz +HSync +VSync
    h: width 1024 start 1040 end 1136 total 1312 skew 0 clock 60.0KHz
    v: height 768 start 769 end 772 total 800 clock 75.0Hz
    1024x768 (0x4b) 75.0MHz -HSync -VSync
    h: width 1024 start 1048 end 1184 total 1328 skew 0 clock 56.5KHz
    v: height 768 start 771 end 777 total 806 clock 70.1Hz
    1024x768 (0x4c) 65.0MHz -HSync -VSync
    h: width 1024 start 1048 end 1184 total 1344 skew 0 clock 48.4KHz
    v: height 768 start 771 end 777 total 806 clock 60.0Hz
    832x624 (0x4d) 57.3MHz -HSync -VSync
    h: width 832 start 864 end 928 total 1152 skew 0 clock 49.7KHz
    v: height 624 start 625 end 628 total 667 clock 74.6Hz
    800x600 (0x4e) 56.3MHz +HSync +VSync
    h: width 800 start 832 end 896 total 1048 skew 0 clock 53.7KHz
    v: height 600 start 601 end 604 total 631 clock 85.1Hz
    800x600 (0x4f) 50.0MHz +HSync +VSync
    h: width 800 start 856 end 976 total 1040 skew 0 clock 48.1KHz
    v: height 600 start 637 end 643 total 666 clock 72.2Hz
    800x600 (0x50) 49.5MHz +HSync +VSync
    h: width 800 start 816 end 896 total 1056 skew 0 clock 46.9KHz
    v: height 600 start 601 end 604 total 625 clock 75.0Hz
    800x600 (0x51) 40.0MHz +HSync +VSync
    h: width 800 start 840 end 968 total 1056 skew 0 clock 37.9KHz
    v: height 600 start 601 end 605 total 628 clock 60.3Hz
    800x600 (0x52) 36.0MHz +HSync +VSync
    h: width 800 start 824 end 896 total 1024 skew 0 clock 35.2KHz
    v: height 600 start 601 end 603 total 625 clock 56.2Hz
    640x480 (0x53) 36.0MHz -HSync -VSync
    h: width 640 start 696 end 752 total 832 skew 0 clock 43.3KHz
    v: height 480 start 481 end 484 total 509 clock 85.0Hz
    640x480 (0x54) 31.5MHz -HSync -VSync
    h: width 640 start 664 end 704 total 832 skew 0 clock 37.9KHz
    v: height 480 start 489 end 492 total 520 clock 72.8Hz
    640x480 (0x55) 31.5MHz -HSync -VSync
    h: width 640 start 656 end 720 total 840 skew 0 clock 37.5KHz
    v: height 480 start 481 end 484 total 500 clock 75.0Hz
    640x480 (0x56) 25.2MHz -HSync -VSync
    h: width 640 start 656 end 752 total 800 skew 0 clock 31.5KHz
    v: height 480 start 490 end 492 total 525 clock 59.9Hz
    720x400 (0x57) 35.5MHz -HSync +VSync
    h: width 720 start 756 end 828 total 936 skew 0 clock 37.9KHz
    v: height 400 start 401 end 404 total 446 clock 85.0Hz
    640x400 (0x58) 31.5MHz -HSync +VSync
    h: width 640 start 672 end 736 total 832 skew 0 clock 37.9KHz
    v: height 400 start 401 end 404 total 445 clock 85.1Hz
    640x350 (0x59) 31.5MHz +HSync -VSync
    h: width 640 start 672 end 736 total 832 skew 0 clock 37.9KHz
    v: height 350 start 382 end 385 total 445 clock 85.1Hz
    HDMI-1 connected 1360x768+0+0 (0x41) normal (normal left inverted right x axis y axis) 0mm x 0mm
    Identifier: 0x3d
    Timestamp: 1278799
    Subpixel: unknown
    Clones: HDMI-2
    CRTC: 0
    CRTCs: 0 1
    1360x768 (0x41) 84.8MHz -HSync +VSync *current
    h: width 1360 start 1432 end 1568 total 1776 skew 0 clock 47.7KHz
    v: height 768 start 771 end 781 total 798 clock 59.8Hz
    1152x864 (0x48) 81.6MHz -HSync +VSync
    h: width 1152 start 1216 end 1336 total 1520 skew 0 clock 53.7KHz
    v: height 864 start 865 end 868 total 895 clock 60.0Hz
    1024x768 (0x4c) 65.0MHz -HSync -VSync
    h: width 1024 start 1048 end 1184 total 1344 skew 0 clock 48.4KHz
    v: height 768 start 771 end 777 total 806 clock 60.0Hz
    800x600 (0x51) 40.0MHz +HSync +VSync
    h: width 800 start 840 end 968 total 1056 skew 0 clock 37.9KHz
    v: height 600 start 601 end 605 total 628 clock 60.3Hz
    640x480 (0x56) 25.2MHz -HSync -VSync
    h: width 640 start 656 end 752 total 800 skew 0 clock 31.5KHz
    v: height 480 start 490 end 492 total 525 clock 59.9Hz
    HDMI-2 disconnected (normal left inverted right x axis y axis)
    Identifier: 0x3e
    Timestamp: 1278799
    Subpixel: unknown
    Clones: HDMI-1
    CRTCs: 0 1
    xorg.conf is here
    Section "ServerFlags"
    Option "AutoAddDevices" "false"
    EndSection
    Section "ServerLayout"
    Identifier "X.org Configured"
    Screen 0 "Screen0" 0 0
    InputDevice "Mouse0" "CorePointer"
    InputDevice "Keyboard0" "CoreKeyboard"
    InputDevice "Touchpad" "SendCoreEvents"
    Option "AIGLX" "true"
    EndSection
    Section "Files"
    # RgbPath "/usr/share/X11/rgb"
    ModulePath "/usr/lib/xorg/modules"
    FontPath "/usr/share/fonts/misc"
    FontPath "/usr/share/fonts/100dpi:unscaled"
    FontPath "/usr/share/fonts/75dpi:unscaled"
    FontPath "/usr/share/fonts/TTF"
    FontPath "/usr/share/fonts/Type1"
    EndSection
    Section "Module"
    Load "GLcore"
    Load "xtrap"
    Load "extmod"
    Load "glx"
    Load "dri"
    # Load "record"
    Load "dbe"
    Load "freetype"
    Load "synaptics"
    EndSection
    Section "InputDevice"
    Identifier "Keyboard0"
    Driver "kbd"
    Option "XkbRules" "xorg"
    Option "XkbModel" "thinkpad60"
    Option "XkbLayout" "us"
    EndSection
    Section "InputDevice"
    Identifier "Mouse0"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "Device" "/dev/input/mice"
    Option "ZAxisMapping" "4 5 6 7"
    EndSection
    Section "InputDevice"
    Identifier "Touchpad"
    Driver "synaptics"
    Option "SendCoreEvents" "true"
    Option "VertEdgeScroll" "true"
    Option "HorizEdgeScroll" "true"
    Option "Device" "/dev/psaux" #/dev/input/mouse0
    Option "Protocol" "auto-dev"
    # Option "TouchpadOff" "1" #Uncomment if you just want to disable the touchpad and use only the trackpoint
    # Option "HorizScrollDelta" "0" #Why is this in here by default. By Gods, it kill horizontal scrolling!
    Option "RightEdge" "5500" #This is a little bigger than the default narrowing the scroll region
    Option "BottomEdge" "4500" #This is a little bigger than the default narrowing the scroll region
    Option "RTCornerButton" "0" #disable Right Top corner "button"
    Option "RBCornerButton" "0" #disable Right Bottom corner "button"
    Option "SHMConfig" "on" #this allows configuration of the touchpad using qsynaptics, synclient, or what have you.
    EndSection
    Section "Monitor"
    DisplaySize 304.8 190.5 # 120 dpi @1440x900
    Identifier "Monitor0"
    Option "DPMS"
    EndSection
    Section "Device"
    Option "NoDDC" "true" # [<bool>]
    Identifier "Card0"
    Driver "intel"
    VendorName "Intel Corporation"
    BoardName "Mobile Integrated Graphics Controller"
    BusID "PCI:0:2:0"
    Option "AccelMethod" "xaa"
    Option "XAANoOffscreenPixmaps" "true"
    Option "DRI" "true"
    Option "FramebufferCompression" "false"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Card0"
    Monitor "Monitor0"
    SubSection "Display"
    Viewport 0 0
    Depth 24
    Modes "1440x900" "1280x800" "1024x768" "800x600"
    Virtual 2960 1024
    EndSubSection
    EndSection
    Section "DRI"
    Group "video"
    Mode 0666
    EndSection
    Section "Extensions"
    Option "Composite" "Enable"
    EndSection
    and now i am using awesome wm. any ideas? Thank you!!

    konni wrote:
    how many monitors do you want to plugin? three? like damjan said, not sure if that works at all.
    or are the hdmi outputs idle and you're just trying to plug in a second screen?
    whats the exact problem? no output on that screen at all? or mirroring the internal one? in that case, try
    xrandr --output VGA --right-of LVDS
    (or left-of...)
    can you plug that monitor in with hdmi? (adapter/etc) you might try that as well, maybe just the vga fails.
    wow.. thank you konni... and thank damjan
    i turned off HDMI-1, then I could get VGA work!
    now i have dual screens, pretty cool.

  • Dual screen problem in CS5

    I have been using dual screens with no problems until I installed PS CS5. Now when I drag an image onto the secondary screen the canvas goes black as soon as I relsease the mouse. I can see the rulers etc. and when dragging across the diaplay the image can be seen but as soon as I 'let go' it's blacked out. The really frustrating thing is that this doesn't happen in AI or Dreamweaver (or indeed any other program!).
    So far I have
    Reset the monitors
    when changed to show the same on both screens (clone) the image can be seen perfectly ok on both screens
    when the secondary monitor is made the primary the problem remains (i.e. the PS image is blacked out on that monitor)
    Checked for updates for the monitors (none needed)
    Checked CS5 up to date (no updates required)
    Checked for graphics card updates (none needed) - NVidia GeForce 8600 GTS
    Uninstalled and re installed PS
    Pointed in an annoyed manner at the useless window open on my secondary screen
    Is there something simple that I have mistakenly chosen that is preventing the use of my secondary screen?

    Check to see if nVidia has released an updated driver for your hardware.  Go to their web site to check.
    Unfortunately, from my observations nVidia may have neglected to keep their driver quality up with later releases for the 8600 GT.  I have reports from some of my own customers using my OpenGL software that the driver is troublesome, and have actually reported better results from an older driver version than the very latest release.
    Other things you can try to work around the problem:
    In Photoshop, Edit - Preferences - Performance, [Advanced...] and change to Basic mode.
    Try disabling OpenGL drawing entirely.  If that corrects the issue it's almost a certainty that the nVidia driver is at fault.
    -Noel

  • Full screen mode with dual screen

    I have a Macbook Pro and use a second screen. I do like the new full screen feature but the app (safari, chrome, opera, firefox etc...) will only full screen with the primary screen (macbook screen). Really defeats the point of having two screens and having the full screen feature combined.
    Any resolutions or is there a new update coming?
    In Summary:
    Full screen mode will only work on your primary monitor  and not a separate screen. Please help.

    Known issue.
    Hopefully, it'll be fixed in a future update.

  • Only raw video can be used with green screen background?  What?

    Latest of all software.
    I have played with green screen a lot trying to make it work. The instructions say, and the only way to make it work, is to drag the background only to main time line in project pane, then drag a raw video clip from the events viewer on top of it, and choose green screen. This makes the video clip an add on to the main time line which is the back drop (like a title is an add on to a video clip).
    As I have railed in other posts, this doesn't make much sense. But the real problem is you can only drag RAW video onto the back ground from events, and can not edit it any way afterwards (since it is treated as an add on, not the main time line). You can edit the back ground, since it is in the main time line.
    The bottom line is: you cannot drag a RAW video onto the project pane, edit it and get it the way you want, and then add a back ground via the green screen. This make no sense.
    Am I doing something wrong?
    Any ideas?
    bob

    Well, here is a convoluted method that seems to work...
    1) drag the raw video to the project pane, edit to your heart's content.
    2) save it as a .mov file (i.e. you are all done with it no more changes...ever).
    3) import that .mov file File, Import as a new event.
    4) drag the background(s) on to project pane, make it long enough for video
    5) drag RAV .mov file (which is really a finished edited file) on to background, choose green screen).
    You now have an edited .mov with a green screen background.
    Could green screen be implemented more poorly? It would be hard to see how.
    I still feel like I am missing something. Any ideas?
    bob

  • Dual Screening Problem

    I just bought a 24 inch external monitor so i could dual screen on my imac. When I put it on the best resolution (1920x1080) the picture is roughly 2 inches to one side. I tried auto config but it has no effect. Any ideas?

    just bought a dvi adaptor, fixed my problem

  • Using "with" Blocks: Any Problem?

    Is the use of with blocks frowned upon among InDesign scripters these days? I'm aware that they are often disfavored in the web world, but I see them used in some sample code I've seen, and being analogous to AppleScript tell blocks, it seems to cut out a lot of repetition or creating non-essential variables. Is there really a risk? Some of the reasoning I've seem mentioned to avoid it involve scoping of variables with the same name, but that could easily be avoided in a personal script, no?

    Hi Rc
    In my opinion there are 2 issues regarding the use of with.
    1) General issues which are the sources of the frowns and the reason why ECMA V5 strict mode bans it use see with - JavaScript | MDN I can not see why those reasons should not apply to Indesign.
    2) Specific InDesign issues.
    A quick intro for the wider audience.
    With can be as far as I know used in 3 ways 1) Method, 2) Property Set 3) Property Get.
    The following 2 scripts show how we can apply these 3 ways using and not using with,
    // With With
    var myRec = app.activeDocument.rectangles[0]; // Note script will crash here if you don't use your brains
    var s;
    with (myRec) {
        move ([],[10,30]); // method
        rotationAngle = 45; // property set
        shearAngle = 15; // property set
        strokeWeight = 3;// property set
        fillColor = app.activeDocument.colors.itemByName("Cyan");// property set
        strokeColor = app.activeDocument.colors.itemByName("Magenta");// property set
        s = shearAngle;// property Get
    // Without With
    var myRec = app.activeDocument.rectangles[0]; // Note script will crash here if you don't use your brains
    var s;
    myRec.move ([],[10,10]); // method
    myRec.properties = {
        rotationAngle: 45,// property set
        shearAngle: 15, // property set
        strokeWeight: 3,// property set
        fillColor: app.activeDocument.colors.itemByName("Cyan"),// property set
        strokeColor: app.activeDocument.colors.itemByName("Magenta"),// property set
    s = myRec.shearAngle // property get
    If you run both script you might think there's not much in it.
    Regarding the "method" and "get" usages besides the general "with" issues then I don't think there's much of a difference.
    However regarding the "set" usage there can be a very significant difference.  You can see this by running each script and undo the changes made to your rectangle by each script.
    Using with you have to undo each and every property setting as each one is applied in turn.
    Using properties all the properties are set at the same time and only one undo is needed. (Each property setting can result in a document redraw and a disk writing.
    Setting the properties in one go can have a very large difference to the run time of the script.  Although one can reduce this by using redraw = false and FAST_ENTIRE_UNDOMODE using these can sometime be problematic.
    However even when scripting Illustrator and the like where one cannot set properties on mass the general issues apply.
    My pennies worth,
    Trevor

Maybe you are looking for