Dual Screen and VLC

I use the HDMI out to contect my Mac Mini to my HDTv, since the Mavericks update I now get a grey bar at the top of the screen (where the menu bar is) durin full screen playback. Is there a way to get rid of this?
Also why does the screen switch everytime you exit full screen in VLC or close VLC? Is it something to do with the app opening in a seperate space? What's the point of this and how do I stop it from happening? The other day VLC crashed and I had to force quit, which left me stuck in the grey inbetween screen with no menu bar or dock.

I found what's wrong.
In KDE window settings:
Right click at window bar -> "More actions" ->  "Windows Manage Settings" -> left side "KWin Scripts" -> right side "Video Wall"
KDE default has activated Video Wall Script (Spans fullscreen video player over all attached screens to create a Video Wall), I didn't notice it.

Similar Messages

  • Microsoft Word consistently becomes active window when clicking between dual screens and programs

    13" MBP
    2.3 ghz i5
    8GB Ram
    Running 10.9.2
    Microsoft Word 2011
    Dual screens with amazon Mini Display to VGA adapter
    When I am running word between an external monitor and my MBP, Microsoft word always interrupts any clicks between programs and between screens to become the active window. This is especially annoying when I am trying to navigate between MacMail and Chrome, or any other programs.
    The problem doesn't exist when I click between programs on the MBP, but only when I select windows between the two screens. Or programs on the external monitor.
    Word is up to date, as is my MBP.
    Please don't punt me to Microsoft, they're the worst!
    Thanks!

    There is a workaround for this problem, which was posted by Highestwater on the Microsoft Community thread for this bug and worked for me as well:
    Go to
    System Preferences > Mission Control >
    and UN-check the box labeled "Displays have separate Spaces" (see image below)
    The original poster on this thread may already be aware of this workaround, because he/she mentioned that the "separate Spaces" option is checked. But if you can live without the extra Mavericks dual display features (like going full screen in 1 display only, switching spaces independently on each display, and having a menu bar on each display), then uncheck this option and the "stealing focus" bug seems to disappear. For me the bug is so annoying that it's worth it to lose the extra features. Just yesterday I closed a Word document I was working on by mistake because I clicked on a Finder window on my other display and immediately pressed command-w to close it, without realizing that the focus had switched to my word document which closed instead. It was saved, but this sort of stuff interrupted my work enough to be both an annoyance and a time drain.

  • Dual screen and the survey mode

    just uploaded LR3, and have hit a huge snag -
    on the second screen, the star ratings, the basis of my cull process, do not show up.
    Is there a setting to make them appear and work, or has adobe big-brothered us into ONLY have accept and reject as options for culling?
    gmw

    guaranteed its different.
    Let me see if I can explain this more thoroughly.
    Before:
    import all images with a two star tag.
    in Library, set attributes to show ONLY two stars
    call up (say) six images on the main (say, left) screen
    Click on Monitor 2, images selected show up on screen #2.
    Ratings showed up, and were changeable on either screen,
    but on the main screen, ALL selected images were affected
    when ANY change was made to the selected images. ,
    on the second screen. however, ratings could be changed on
    INDIVIDUAL images, changed to (say three stars or NO stars,
    making them disappear from BOTH screens.
    This made culling and selecting images VERY quick,
    and looking at focus was much better since the images were much larger
    on the second screen.
    Now:
    Since there is no rating possible on the second screen,
    I tried to import them all with a 'rejected' flag, then show that ONLY,
    and go thru and mark the accepted ones. That would NEARLY serve as
    well as my previous scheme.
    No go, no way to tag all imports as rejected or accepted. Crap.
    So.
    Now, call up six images on the main screen.
    They show up on the secondary screen, with no star ratings.
    Clicking on the reject button does NOTHING.
    All six images still there.
    instead, I tried using the P and X keys -
    with only ONE image highlighted on the secondary screen, ( you can do
    that, you can see it's the one focused on: it has a white border
    around it.)
    clicking P will make ALL of the images disappear from the secondary
    screen, BUT, NO ACTUAL change has been made to any status.
    The images are still showing on the main screen. If you change the
    selected flag status to ACCEPT. or flag, they do NOT show up on the
    main screen.
    If you change it to show rejected images, they DO show up.
    It seems there is no actual communication between the main screen and
    the secondary screen. Nothing done on the secondary screen, where the
    images
    can be seen MUCH better and larger, is sent to the program.
    In short, EVERY possible way to continue working more or less the same
    way I did before has  been closed off to me.
    No way to shoot 6000 images in a weekend, and cull them in less than 5
    or 6 hours, now. Something I could do in less than two hours before.
    Yeah, i'd say this was important to me.
    Since I got the program (less than two weeks), I've shot more than
    10,000 images, and spent WAY too much time culling the output.
    Dysfunctional I said, and that's what I meant: It DONT WORK!
    at the end of culling the set,
    Never messed with Rej/Acc flags, since the logic did not work for what
    I needed to do.
    on the main screen,

  • Best driver for dual-screen and 3D with Radeon Xpress 200M [solved]

    I need a good graphic driver for double screen and gaming, open source or old Ati one ?
    How I do install it correctly ???
    Note : catalyst could perform better for gamers ...
    Last edited by spiky25 (2009-11-22 23:53:01)

    Sorry for the mild thread necromancy.
    At what resolution do you run the external display? According to AMD/ATI, the radeon xpress 200m supports only up to 1600x1200, but I think I've used bigger displays with no problems.

  • Dual screening and clustering at the same time

    i got a new imac 2010 and i want to know if i can cluster it with my old apple g4 imac and still be apple to use the screen. 

    A device can be connected to only one network at a time.
    I will tell you what works for me.
    Connect your TC to your modem. All you need to do is set up a dedicated n network on 5ghz freq (i used wpa2 wireless security) with with your TC and use that with all of your other n capable stuff like ATV, macbook air etc. Then connect your old AEBS using an ethernet cable to the ethernet AEBS connection to the TC ethernet. Then using Airport Utility find your AEBS, and set up a b/g network 2.4ghz freq (i used wep 128bit). While setting up the AEBS, click on the internet tab on the top and then go the bottom, where you will see connection sharing and select off (bridge mode). This will allow your AEBS to use the TC as a bridge to your cable modem. Now you have two wireless networks using one modem using essentially 2 base stations, TC and AEBS. My old AXs, old b/g imacs and iphone join the b/g network, and I can stream music from my n capable computer and old b/g imacs to my ATV and AX hooked to different stereos around my home. And log in to different music libraries and control the music from my iphone. My computer are all networked wirelessly. The higher encryption you use on the b/g network the slower it will be. Do not combine b/g/n network as it will be slow, and more so using any wireless security. Keep in mind you can also use an old AX instead of and old AEBS for the b/g network as well in bridge mode. Give different names for each network. Any neighbor on the same frequency using the same channel will interfere and slow your network done. There are cool widgets you can download that tell you what channels your neighbors are using and can select a different channel from them. It's complicated and takes patience, good luck.

  • Dual display and VRAM usage.

    Hi, back in the days I wanted a 12" iBook but couldn't afford one, last autumn thought I decided to get a Macbook Pro, the update came and...
    .. it had 128MB vram.
    I want to use dual screen and maybe even occasional gaming, I couldn't decide if this where sufficient for my needs or not so I waited for the june update.
    The mid-07 MBP arrived and, it had 128MB vram AGAIN!
    Why oh why Apple? Oh, don't answer that, it's because you're in bed with Intel and want to force feed us useless highest end CPUs. But all I care for is the VRAM, why do I have to pay a ****-of-a-lot for a 1/11th faster CPU?
    Anyway, I tried to decide if I should "bit the sour Apple" and get the mid modell or just get the low one because that one is much more price worthy. A few days ago I ordered the low end one.
    But then I've seen on barefeats that he says that a 30" ACD display would use 128MB vram of the 256MB vram modell, are vram always splitted between displays in OS X?
    You see, if the extra 20" 1680x1050 display only use 1680x1050x(3 or 4) bytes that is ok, maybe even if it's double buffered (is it?), because then I will probably have like 100MB vram left for all my windows and for desktop usage that is probably ok. But if the vram is shared between displays and my 20" which I will use most only get 64MB vram that's quite low.
    I know I can turn of the sleeping capabilities of the MBP and shut the lid and only use one screen but that's a quite lame solution.
    I hate how Apple does this, and it seems to worry a lot of people. Some get the more expensive modell and hate that they had to do it, some doesn't, and some don't buy a machine at all .. I would probably have stayed in the last crowd.
    256MB vram can't have cost them many tens of dollars, why not have that in all modells? Why is the middle one even needed? Just make 2.4GHz CPU and option in that case.
    Anyway, does anyone know how much vram my screen will have available? Will 128MB work for me with all the regular desktop apps I will have running? Or should I really go with the 256MB one? The tricky part is that my MBP might be shipped today or similair.
    I've called Apple support three times but noone of them knows how this works so they aren't for much help.
    (Dell vostro 1500 sells here in Sweden for less than half the price of the mid MBP and comes way more balanced, you can even get a 1680x1050 screen. Sure it has 2.0GHz CPUs or whatever but I don't care about that. Where is the old "omg MHz myth"-Apple? Please understand CPU speed isn't everything. Instead of leading the MHz myth fight it ;D, start calling the CPUs T7300 and so on aswell ;D)

    Hi Johan, actually the VRAM used by OS X is likely to be quite a bit more than just your screen resolution multiplied by 3 or 4, since each open window is composited offscreen for the shadow effects and for things like zooming (Ctrl-Mousewheel) and the "Genie effect".
    I'm pretty sure the total VRAM isn't divided in half for each of the two displays though, as it will be allocated from the video driver on an as-needed basis. In practice, with both displays active and a few windows open, you should still have maybe 80-90% of your VRAM available for applications.
    Games and other VRAM-heavy applications are a special case as these will typically use as much VRAM as you can give them, and swap out to system RAM via the PCI-X bus when they need more (and unlike swapping to disk, swapping into VRAM from system RAM is still pretty fast).

  • New window opens in main monitor when using dual screen

    I am using dual screens and my "main screen" is on the left. Ever since Firefox updated to 32.0.1 on Monday I've been having this issue. Before the update, I would have my main Firefox window opened on the left and, when I click on a link to open a new window, it would open on the right screen. Now, it will only open on the left screen, where the other window is. If I drag the original window to the right monitor and open a link, the new window will open on the right monitor. But once I drag the original window back to the left, new links will open in the left again.
    Before if I had this problem, I would simply drag the new window to the right monitor, then back to the left and close it. Then click the link again and it would open in the right. Kind of a work around I guess. But since the update, even this will not work. Any suggestions? Or is this a new function of the updated version? Is there a way for me to go back to the previous version? Any help is appreciated!

    Hi hollytotheg,
    I understand that links opening in new windows are opening in the active screen, not on the right, second monitor.
    This may be helpful: [https://addons.mozilla.org/en-US/firefox/addon/monitor-master/] the search recommends this.
    However I would also recommend suggesting an enhancement in input about dual monitor new window restriction.

  • Mountain Lion Dual screen window Full screen problem?

    I could not upgrade from Snow Leopard to Lion on my iMac because dual screen operation was broken when a window on one screen was set to full screen. Has this been fixed in Mountain Lion?

    CuckooPint wrote:
    I could not upgrade from Snow Leopard to Lion on my iMac because dual screen operation was broken when a window on one screen was set to full screen. Has this been fixed in Mountain Lion?
    Hey Cuckoo
    i Use an iMac with 2 dual screens and the problem you are describing is fixed in the final build release of ML.
    i have not seen the breaking of activity when switching too full screen on even all 3 monitors.  so looking good in the multiscreen support.
    cheers

  • Looks to be interference when dual screen

    just bought this 21.5" intel mac, got the Mini DisplayPort to DVI Adapter to dual screen and the second screen sits there flickering like theres some sort of interference from somewhere..
    checked both monitor and cable and both are in working order.
    think i could possibly be the connector.. any other ideas?
    help appreciated very much

    this is what happens to the screen... works perfect for first 5-10 mins then starts

  • Dual screen development

    I would like to develop an application that runs dual screen,
    and I can set
    the presentation window to 2560 x 800 but then on my single
    monitor system I
    can't scroll around the design window. Is this possible? Am I
    heading for a
    fall?
    Thanks for any pointers
    Dave

    Cheers Steve thought that might be the only route.
    Oh well!
    "Steve Howard **Community Expert** - eLearning + Mobile and
    Devices"
    <[email protected]> wrote in message
    news:funps8$n34$[email protected]..
    > >I would like to develop an application that runs
    dual screen, and I can
    > >set the presentation window to 2560 x 800 but then
    on my single monitor
    > >system I can't scroll around the design window. Is
    this possible? Am I
    > >heading for a fall?
    >>
    >
    >
    > Authorware does not have any real knowledge of dual
    screen, and it
    > certainly has no native way to scroll around when the
    application window
    > is bigger than your screen.
    >
    > Best you can do is if you are targeting dual screen then
    *develop* on dual
    > screen.
    >
    > Steve
    >
    >
    > --
    > Adobe Community Expert: eLearning, Mobile and Devices
    > European eLearning Summit - EeLS
    > Adobe-sponsored eLearning conference.
    >
    http://www.elearningsummit.eu

  • I'd like to see next generation of Touchsmart PC with Touchsmart keyboard and dual screen

    Where you have a monitor as the display and a seperate keyboard, but the keyboard is another monitor which operates as a keyboard, for example something like this... 
    This ultimately would mean that the keyboard could be application driven, that is it could be specifically configured anyway that the application requires it.  I'd also like to see a dual screen option for touchsmart PC - a screen that is built in and can be slid out from the rear of the monitor to act as dual screen, extended screen...
    HP ENVY 17-j005tx Notebook, HP ENVY Recline 27-k001a, HP ProLiant MicroServer Gen8 G2020T, HP MediaSmart EX495 Server, HP MediaVault 2020, HP ENVY 120 AiO Printer

    Jim,
    You may want to check out this community for developers. I'm pretty sure HP is aware of the goings-on in these forums:
    http://www.touchsmartcommunity.com/forums
    ... an HP employee expressing his own opinion.
    Please post rather than send me a Message. It's good for the community and I might not be able to get back quickly. - Thank you.

  • I can't play a bought video in iTunes, and VLC only plays it but no screen. And I have to athourize all the time but it does not help. What's wrong?

    Hi all.
    Just bought my first video from iTunes Store and should watch it with my son. I had to authorize, this and that for some time, but finally I got the video in my iTunes, but it was just a black screen. Nothing playing and no sound (of course). So I tried VLC and it was at least runing there, but no screen and no sound. Quick time said I had to authorize my iTunes acount first (which I had done several times before) and did it again with just the same result, nothing happening. What's wrong? I'm no geek so please help me out with this, I thought it should be easy piecy with a iMac and iTunes, well, hope it was a one in a million problem.
    Thanks

    Could be a corrupt Download.
    If you live in a Region that allows re-downloading Music...
    Delete the Song(s) and re-download...
    See Here  >  Download Past Purchases  >  http://support.apple.com/kb/HT2519
    If not... Contact iTunes Customer Service  >  Apple  Support  iTunes Store  Contact Us

  • [SOLVED] dual-screen problem with awesome3.2 and firefox/gedit

    Hi,
    my problem is that firefox/gedit (+maybe other apps, i don't know yet) are starting in awesome like they are fullscreen apps. Firefox covers the wibox at the top of the screen, and even overlaps a bit to the seconds screen. So the keyboard-shortcuts doenst work well, because awesome then changes the tags in bots screens when on one tag firefox is opened.
    I dont know why this happens, here is my rc.lua:
    -- Load libraries
    require("awful")
    require("beautiful")
    require("wicked")
    -- {{{ Variable definitions
    -- User styles for windows, statusbars, titlebars and widgets
    theme_path = os.getenv("HOME") .. "/.config/awesome/themes/zenburn"
    beautiful.init(theme_path)
    -- Modifier keys
    modkey = "Mod4" -- Super_L
    -- Window titlebars
    use_titlebar = true
    -- Window management layouts
    layouts = {
    awful.layout.suit.tile, -- 1
    awful.layout.suit.tile.left, -- 2
    awful.layout.suit.tile.bottom, -- 3
    awful.layout.suit.tile.top, -- 4
    awful.layout.suit.fair, -- 5
    awful.layout.suit.fair.horizontal, -- 6
    awful.layout.suit.max, -- 7
    -- awful.layout.suit.max.fullscreen, -- /
    awful.layout.suit.magnifier, -- 8
    awful.layout.suit.floating -- 9
    -- Application specific behaviour
    apprules = {
    -- Class Instance Name Screen Tag Floating
    { "Firefox", nil, nil, nil, 2, false },
    { "Firefox", "Download", nil, nil, nil, true },
    { "Firefox", "Places", nil, nil, nil, true },
    { "Firefox", "Extension", nil, nil, nil, true },
    { "MPlayer", nil, nil, nil, nil, true },
    { nil, nil, "VLC media player", nil, nil, true },
    { "Gimp", nil, nil, nil, nil, true },
    { "Xmessage", "xmessage", nil, nil, nil, true },
    { "Skype", nil, nil, nil, 1, true },
    { "Pidgin", nil, nil, nil, 1, true },
    -- {{{ Tags
    -- Define tags table
    tags = {}
    tags.settings = {
    { name = "im", layout = layouts[9] },
    { name = "www", layout = layouts[1] },
    { name = "terms", layout = layouts[3] },
    { name = "dev", layout = layouts[3] },
    { name = "other", layout = layouts[5] },
    -- Initialize tags
    for s = 1, screen.count() do
    tags[s] = {}
    for i, v in ipairs(tags.settings) do
    tags[s][i] = tag(v.name)
    tags[s][i].screen = s
    awful.tag.setproperty(tags[s][i], "layout", v.layout)
    awful.tag.setproperty(tags[s][i], "setslave", v.setslave)
    end
    tags[s][1].selected = true
    end
    -- {{{ Wibox
    -- Widgets configuration
    -- Reusable separators
    myspace = widget({ type = "textbox", name = "myspace", align = "right" })
    myseparator = widget({ type = "textbox", name = "myseparator", align = "right" })
    myspace.text = " "
    myseparator.text = "|"
    -- Date, time and...
    mydateicon = widget({ type = "imagebox", name = "mydateicon", align = "right" })
    mydateicon.image = image(beautiful.widget_date)
    mydatewidget = widget({ type = "textbox", name = "mydatewidget", align = "right" })
    wicked.register(mydatewidget, wicked.widgets.date, "%b %e, %R", 60)
    -- a Calendar
    function calendar_select(offset)
    local datespec = os.date("*t")
    datespec = datespec.year * 12 + datespec.month - 1 + offset
    awful.util.spawn("cal -m " .. (datespec % 12 + 1) .. " " .. math.floor(datespec / 12) .. " | xmessage -geometry +1135+17 -file -")
    end
    mydatewidget:buttons({
    button({ }, 1, function () calendar_select(0) end),
    button({ }, 4, function () calendar_select(1) end),
    button({ }, 5, function () calendar_select(-1) end)
    -- System tray
    mysystray = widget({ type = "systray", align = "right" })
    -- Create a wibox and...
    mywibox = {}
    mypromptbox = {}
    mylayoutbox = {}
    mytaglist = {}
    mytaglist.buttons = { button({ }, 1, awful.tag.viewonly),
    button({ modkey }, 1, awful.client.movetotag),
    button({ }, 3, function (tag) tag.selected = not tag.selected end),
    button({ modkey }, 3, awful.client.toggletag),
    button({ }, 4, awful.tag.viewnext),
    button({ }, 5, awful.tag.viewprev) }
    -- ...add it to each screen
    for s = 1, screen.count() do
    -- Create a promptbox
    mypromptbox[s] = widget({ type = "textbox", align = "left" })
    -- Create an imagebox widget with icons indicating active layout
    mylayoutbox[s] = widget({ type = "imagebox", align = "left" })
    mylayoutbox[s]:buttons({ button({ }, 1, function () awful.layout.inc(layouts, 1) end),
    button({ }, 3, function () awful.layout.inc(layouts, -1) end),
    button({ }, 4, function () awful.layout.inc(layouts, 1) end),
    button({ }, 5, function () awful.layout.inc(layouts, -1) end) })
    -- Create the taglist
    mytaglist[s] = awful.widget.taglist.new(s, awful.widget.taglist.label.all, mytaglist.buttons)
    -- Create the wibox
    mywibox[s] = wibox({ position = "top", height = "14", fg = beautiful.fg_normal, bg = beautiful.bg_normal })
    -- Add widgets to the wibox (order matters)
    mywibox[s].widgets = { mylayoutbox[s],
    mytaglist[s],
    mypromptbox[s],
    myspace,
    mydateicon, mydatewidget,
    myspace,
    s == screen.count() and mysystray or nil
    mywibox[s].screen = s
    end
    -- {{{ Mouse bindings
    root.buttons({
    button({ }, 4, awful.tag.viewnext),
    button({ }, 5, awful.tag.viewprev)
    -- {{{ Key bindings
    globalkeys = {
    -- Applications
    key({ modkey }, "Return",function () awful.util.spawn("uxterm") end),
    -- Prompt menus
    key({ modkey }, "F2", function () awful.prompt.run({ prompt = "Run: " }, mypromptbox[mouse.screen],
    awful.util.spawn, awful.completion.shell, awful.util.getdir("cache") .. "/history")
    end),
    -- Awesome controls
    key({ modkey, "Shift" }, "q", awesome.quit),
    key({ modkey, "Shift" }, "r", function () mypromptbox[mouse.screen].text = awful.util.escape(awful.util.restart()) end),
    -- Layout manipulation
    key({ modkey, "Shift" }, "Plus", function () awful.client.incwfact(-0.05) end),
    key({ modkey, "Shift" }, "Minus", function () awful.client.incwfact(0.05) end),
    key({ modkey }, "space", function () awful.layout.inc(layouts, 1) end),
    key({ modkey, "Shift" }, "space", function () awful.layout.inc(layouts, -1) end),
    -- Focus controls
    key({ modkey }, "Tab", function () awful.client.focus.history.previous(); if client.focus then client.focus:raise() end end),
    key({ modkey }, "Down", function () awful.client.focus.bydirection("down"); if client.focus then client.focus:raise() end end),
    key({ modkey }, "Up", function () awful.client.focus.bydirection("up"); if client.focus then client.focus:raise() end end),
    key({ modkey }, "Left", function () awful.client.focus.bydirection("left"); if client.focus then client.focus:raise() end end),
    key({ modkey }, "Right", function () awful.client.focus.bydirection("right");if client.focus then client.focus:raise() end end),
    key({ modkey, "Shift" }, "Down", function () awful.client.swap.bydirection("down") end),
    key({ modkey, "Shift" }, "Up", function () awful.client.swap.bydirection("up") end),
    key({ modkey, "Shift" }, "Left", function () awful.client.swap.bydirection("left") end),
    key({ modkey, "Shift" }, "Right", function () awful.client.swap.bydirection("right") end),
    -- Client manipulation
    clientkeys = {
    key({ modkey, "Control" }, "space", awful.client.floating.toggle),
    -- Bind keyboard digits
    keynumber = 0
    for s = 1, screen.count() do
    keynumber = math.min(9, math.max(#tags[s], keynumber));
    end
    -- Tag controls
    for i = 1, keynumber do
    table.insert(globalkeys,
    key({ modkey }, i,
    function ()
    local screen = mouse.screen
    if tags[screen][i] then
    awful.tag.viewonly(tags[screen][i])
    end
    end))
    table.insert(globalkeys,
    key({ modkey, "Shift" }, i,
    function ()
    if client.focus and tags[client.focus.screen][i] then
    awful.client.movetotag(tags[client.focus.screen][i])
    end
    end))
    end
    -- Set keys
    root.keys(globalkeys)
    -- {{{ Hooks
    -- Hook function to execute when focusing a client
    awful.hooks.focus.register(function (c)
    if not awful.client.ismarked(c) then
    c.border_color = beautiful.border_focus
    end
    end)
    -- Hook function to execute when unfocusing a client
    awful.hooks.unfocus.register(function (c)
    if not awful.client.ismarked(c) then
    c.border_color = beautiful.border_normal
    end
    end)
    -- Hook function to execute when marking a client
    awful.hooks.marked.register(function (c)
    c.border_color = beautiful.border_marked
    end)
    -- Hook function to execute when unmarking a client
    awful.hooks.unmarked.register(function (c)
    c.border_color = beautiful.border_focus
    end)
    -- Hook function to execute when the mouse enters a client
    awful.hooks.mouse_enter.register(function (c)
    -- Sloppy focus (but disabled for magnifier layout)
    if awful.layout.get(c.screen) ~= awful.layout.suit.magnifier
    and awful.client.focus.filter(c) then
    client.focus = c
    end
    end)
    -- Hook function to execute when a new client appears
    awful.hooks.manage.register(function (c)
    -- If we are not managing this application at startup, move it to the screen where the mouse is
    if not startup and awful.client.focus.filter(c) then
    c.screen = mouse.screen
    end
    -- Add a titlebar to each client
    if use_titlebar then
    awful.titlebar.add(c, { modkey = modkey })
    end
    -- Set client mouse bindings
    c:buttons({
    button({ }, 1, function (c) client.focus = c; c:raise() end),
    button({ modkey }, 1, awful.mouse.client.move),
    button({ modkey }, 3, awful.mouse.client.resize)
    -- New clients may not receive focus if they're not focusable, so set the border anyway
    c.border_width = beautiful.border_width
    c.border_color = beautiful.border_normal
    -- Check application->screen/tag mappings and floating state
    local target_screen
    local target_tag
    local target_float
    for index, rule in pairs(apprules) do
    if (((rule[1] == nil) or (c.class and c.class == rule[1]))
    and ((rule[2] == nil) or (c.instance and c.instance == rule[2]))
    and ((rule[3] == nil) or (c.name and string.find(c.name, rule[3], 1, true)))) then
    target_screen = rule[4]
    target_tag = rule[5]
    target_float = rule[6]
    end
    end
    -- Apply mappings, if any
    if target_float then
    awful.client.floating.set(c, target_float)
    end
    if target_screen then
    c.screen = target_screen
    awful.client.movetotag(tags[target_screen][target_tag], c)
    end
    -- Focus after tag mapping
    client.focus = c
    -- Set client key bindings
    c:keys(clientkeys)
    -- Put windows at the end of others instead of setting them as a master
    --awful.client.setslave(c)
    -- ...or do it selectively for certain tags
    if awful.tag.getproperty(awful.tag.selected(mouse.screen), "setslave") then
    awful.client.setslave(c)
    end
    -- New floating windows don't cover the wibox and don't overlap until it's unavoidable
    awful.placement.no_offscreen(c)
    --awful.placement.no_overlap(c)
    -- Honoring size hints: false to remove gaps between windows
    c.size_hints_honor = false
    end)
    -- Hook function to execute when arranging the screen
    awful.hooks.arrange.register(function (screen)
    -- Update layout imagebox widget with an icon indicating active layout
    local layout = awful.layout.getname(awful.layout.get(screen))
    if layout and beautiful["layout_" ..layout] then
    mylayoutbox[screen].image = image(beautiful["layout_" .. layout])
    else
    mylayoutbox[screen].image = nil
    end
    -- Give focus to the latest client in history if no window has focus
    -- or if the current window is a desktop or a dock one
    if not client.focus then
    local c = awful.client.focus.history.get(screen, 0)
    if c then client.focus = c end
    end
    -- Fine grained border controls
    local visible_clients = awful.client.visible(screen)
    if #visible_clients > 0 then
    for unused, current in pairs(visible_clients) do
    -- Floating clients always have borders
    if awful.client.floating.get(current) or (layout == 'floating') then
    current.border_width = beautiful.border_width
    -- Floating clients always on top
    if not current.fullscreen then
    current.ontop = true
    end
    -- Don't draw the border if there is only one tiled client visible
    elseif (#visible_clients == 1) or (layout == 'max') then
    visible_clients[1].border_width = 0
    else
    current.border_width = beautiful.border_width
    end
    end
    end
    end)
    I added "xrandr --output DVI-1 -- right-of DVI-0" to the .xinitrc to get the extended desktop i want.
    Any suggestions?
    Last edited by Wishes (2009-03-29 10:52:00)

    Still the same
    Edit: i deleted my ~/.mozilla folder. Now firefox starts not overlapping with the wibox, but still a bit overlapping to the other screen, so hat my keystrokes toggle both screens. it seems that it start in floating mode, because i can move it with the mouse. When i move it a bit towarts the wibox and a bit right, it seems to get stuck in the chosen tile-layout and everything is fine... until i quit firefox and start it again.
    Edit2: Hmmm, ok, i think i found it... or at least something:
    -- New floating windows don't cover the wibox and don't overlap until it's unavoidable
        --awful.placement.no_offscreen(c)  //THIS was first uncommented
        awful.placement.no_overlap(c)  //THIS was first commented
    So now with no_overlap it seems to work finde (although i cannot move gedit between the screens with the mouse, but i dont know if this isn't normal. Firefox is moveable between the screens.), no overlapping anymore with the wibox or to the other screen.
    When i uncomment both lines, firefox and gedit are starting both on the 2nd screen (the left one), and gedit cannot be moved to the right one (although firefox can be moved.).
    Last edited by Wishes (2009-03-28 20:24:52)

  • Using Keynote with Podcast Capture and Dual Screens

    Hi everyone,
    We are trying to use a dual screen setup to record some Keynote presentations using Podcast Capture (i.e Dual mode, with the Keynote presentation in one screen and the presenter in the other).
    The problem we are having is that when in full screen mode, Keynote takes control of both displays, thus stopping the Podcast application from being displayed. Even if we switch off the Presenter Display on the second screen, the second screen turns black.
    I know we can start and stop recording with hotkeys, but we would prefer to be able to see the Capture app in one window with the presentation full screen in the other.
    Perhaps this is just an oversight on Apple's part, but I'm finding it hard to believe its not possible. If anyone else has a workaround then please share.
    Thanks.

    Other applications are not visible when Keynote is playing back.  Keynote takes over control of the graphics system when playing back presentations to enable Keynote to display properly.
    When I play back Keynote and I want to look at a second application, I use a second Mac.

  • WINE and my Dual-screens

    I have looked around, quite a bit, haven't found a answer that i've been really looking for...
    I'm a big gamer, and I run two 17" flatpanel monitors at 1280x1024 on a NVIDIA GeForce GTS250.
    When I run apps in WINE, it tries pushing each app out in 2560x1024, such as World of Warcraft... now, for WoW, it doesn't bother me. because my UI scales to 1280x1024 for some reason anyway.
    As for games, like PoRTaL and Left4Dead.... it's trying to squeeze 2560x1024 into one monitor, making them pretty much unable to play..
    I have tried emulating the app in a virtual environment, at 1280x1024... and I really don't wanna disable my other monitor every time.... Because I use them for Cheats, or a guide, whatever I tend to use it for...
    Is there a way to push these apps into 1280x1024 instead of my dual-screen resolution?
    It's one of the main issues for me keeping Winblows 7 on my computer... pretty sure once I figure this out, i can get rid of it.
    Sorry if this has been answered elsewhere, probably wasn't searching the right terms and what not.

    o1911 wrote:
    Perhaps, if you are interested, you could setup a new xorg.conf which has separate X sessions for each window (rather than TwinView), such that you could open up what you want on one window, then play your game on the other.  Even if that is beyond what you want, you could check out ways to dynamically turn off screens:
    https://bbs.archlinux.org/viewtopic.php?id=81310
    For a while there I would launch games via scripts, which called xrandr first to turn off my second screen, but these days I launch everything with xinit to avoid turning off/on compiz for max performance.
    I'm interested to see what you decide on, post back here
    I have thought about both options, and I'm not sure if I wanna do either of them,
    I mean, I want WINE apps to go into 1280x1024 which makes sense that I won't be able to unless I disable a monitor or run two separate X sessions, which I'll probably set it up to run two separate X sessions.
    Still doing some research and making my decision.

Maybe you are looking for