[solved]screen borders and full sized window emerald compiz

hellos archers! i'm using XFCE and i have i little issue, when i maximize a windows in the bottom left and right sides the window borders disappear, (il also make hard to see the scroll bar) is there a way to set that when i maximize a window the borders does stay in the screen?
Last edited by kandros (2011-10-06 22:29:14)

alphaniner wrote:In Settings -> Window Manager Tweaks -> Accessibility tab there's an option 'Hide frame of windows when maximized'. Uncheck it.
thank you but i use compiz as window manager instead of xfwm4
EDIT: because of your tip i finally remember that there is an option like this in emerald settings... shame on me that i didnt check it
Last edited by kandros (2011-10-06 22:27:49)

Similar Messages

Using Apple TV/Airplay for a full screen movie and opening new window on laptop

When I have a full screen movie playing on my TV in AirPlay dual screen mode, and I open a new Safari window or my Mail, the window appears seemingly by default on top of the movie rather than coming up on my laptop monitor. Is there a spot I can reset the default for new Safari windows and Mail windows to my laptop monitor, so they don't interrupt the movie on my TV?
Background: my girls love Downton Abbey and Call the Midwife which I find terribly boring, and need to find something to do while the movies are playing rather than fall asleep! And you know what happens if Safari shows up over top of their beloved Downton!

it being mirror and many tv's being widescreen 16:9 and the screen of ios device not being widescreen this happen
most tv's support having top and button chopped or streghed to fill the tv this is something one does with the tv's remote

Full screen images and full screen color background boxes are cropping horizontally.

Full screen images aren't loading and full screen color background boxes are cropping horizontally. I'm forced to make my images a full screen slide show (of 1 image) to make it work, but then I lose the option to pin the image. Am I alone in this?

Hello,
I would request you to share the a url or few screenshot so that i can get better idea about the issue.
To create a temporry url you can go to File > publish in muse.
Regards
Vivek

How to I get a pop-up window to not be full sized window? I accidentally maximized and can't undo it.

I accidentally clicked "maximize" icon on a Salesforce.com pop-up reminder (the pop-up appeared right when I was going to click something else on the page). Now pop-up reminders come up as full-size web pages and I want them to go back to being the smaller. I can't seem to find a way to do this.

Are you using IOS 7.0.4 on your iPad; if not update your software.

Indesign CC when I open it the screen is not full sized and the boarders on the pages aren't showing up correctly. It is also extremely slow and lagging a lot. I have tried un installing and re installing but it hasn't helped. Its making the program extre

Some screen shots of some of the issues I have been having

Try two things: (1) Click on the Workspace menu (you screen shot shows it is set on Essentials) and choose Reset Essentials. If that doesn't work, try (2) restoring your InDesign preferences. Here's how:
Trash, Replace, Reset, or Restore the application Preferences

[solved] Ran Bleachbit and now my window borders are gone

Yeah, I'm using Mate. I just need to know what the names of the packages are so I can get them back...
Last edited by Mr_ED-horsey (2011-11-19 00:45:13)

Solved. I logged out. Hot ctrl+alt+f2 and ended up completely reinstalling mate & mate-extras... Then deleted bleachbit permanently... Cleaning my system via the command line has never given me any problems... Bleachbit, used it once, several problems...

Screen shots and full list of 2.0 features

I just learned on internal board that you can now do screen shots of your window (hit power and home button at the same time - clip is saved in camera roll).
Is there a full list somewhere of all new features? This was news to me and is a very cool feature. I'm wondering what else I might be missing.

read this
http://www.theiphoneblog.com/2008/07/14/review-iphone-20-software/
it should help out alot

Set screen resolution, and full screen view mode (F11)

Hi,
I have a jsp page which only looks right in 1280x1024. Can I write some kind of code to set the browser to always be 1280x1024 and the view mode to be full screen regardless of the client's setting?
I would like to thank all for responding to my previous questions/problems.

Hi,
after all, try <body onload="window.resizeTo(width,height);">. It works for me. You can also turn off navigation bars etc. See http://forums.devarticles.com/javascript-development-22/change-window-size-and-nav-bar-status-on-page-load-2091.html for example - or google "javascript resize window".
However, I don't know of a method to set the window to an F11-like fullscreen mode.
Regards,
Patrik

Imac screen dims and two browser windows flicker.

Not sure how to explain this, but when I have two browser windows open, at random, they start to flicker and the whole screen gets dim.
What can I do?
Thanks

I just noticed that when it happens, the mouse pointer stays with the hand icon.
Then when I move it to a window, that window goes dim.
Can someone explain this?
Thanks

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

[Solved] Conky, Borders and AwesomeWM

Just wondering if it possible to remove the outline border of Conky on AwesomeWM. I got rid of the shadowing around it due to compton by doing the following:
compton --config ~/.compton.conf --shadow-exclude 'n:a:Conky' -b &
But no matter what I did I still get the border around Conky.
Here is compton configuration file.
http://pastebin.com/rwCn3gNn
And here is my conky config file.
http://pastebin.com/Kewtxm1x
Still struggling to get it removed. Here is a screenshot also.
Last edited by z1lt0id (2014-07-20 22:06:02)

It's been a really long time since I used conky so this is a bit of a shot in the dark, but you could try:
1. Set own_window_type to either "desktop" or "override" in your .conkyrc
2. Create a rule for conky in awesome's rc.lua that sets the property, border_width = 0

How to make the finder window expand to full height AND width of my screen, but not "full screen mode".

The new green button on the finder window makes the screen go into full screen takeover mode - alt clicking this makes it 100% height of the screen.
How can I make this 100% width and height (just like it used to be in Mavericks)?
I have 2 x 27" monitors, so the "full screen takeover" mode is not right as I only want the finder window to be on one monitor whilst I work on another.
Any ideas?! Thank you!

Was about to post the same question.
Ever since I upgraded to Yosemite (about a month ago), this odd behavior has irked me.
Could it be that it only plagues those of us running dual displays? And therefore nobody else cares?

What determines a window's/programs preference when switching between a full screen app and the desktop

Example: I have multiple programs/windows open but am currently working in Firefox. I switch to itunes to change a song, switch back to the original desktop and now iCal is comes up as the focused program. Is there any way to make the current window/program your working on take preference over the others?

That is strange, seems like a different problem. I find that I can access either screen ok (ie either share the screen of the currently-logged in user, or open a virtual desktop of a different user), but it goes haywire if I try and switch between the two once a remote desktop is open. If I want to switch from the virtual desktop to the actual desktop, the only way to do it is to close screen sharing and open it again, selecting the different option.
Regarding your problem - is it just the virtual display that is unresponsive or also the sharing of the logged-in user? It is probably best you create a new thread dedicated to your problem.

MISSION CONTROL, LAUNCHPAD, and FULL SCREEN APPS (one month later)

I'm pretty good embracing a new thing when it comes along. I downloaded LION the day it come out, which was over a month ago at this point. On that day, I immediately found MISSION CONTROL and LAUNCHPAD both uninituitve and pointless. Unhandy iCandy. And of FULL SCREEN APPS? Not necessary on an iMac anyway.
So I quickly sought out quick solutions to 'fix' these new features. Launchpad and full screen apps have the advantage that they can be simply ignored. This is a good thing. Mission Control, on the other hand, got in the way of a beloved feature for me: what was once SPACES and EXPOSE. That is, I couldn't simply ignore MC because I still needed the previous helpful features in Snow Leopard.
My solution was kind of surprising and eye-opening. It's complicated to explain but I thought I'd share. This conclusion is likely best suited for someone not using a small screened Mac. It turns out that most users (with big enough screens) don't really need Mission Control, Launchpad, Spaces, or Full Screen apps.
At all.
Let's go through that conclusion, one by one:
FULL SCREEN APPS
If you have a relatively big screen (20 iMac for instance), why do you need Safari full screen? Unless you intend to sit across the room from the computer, no reason. And there's lots of bright empty space when you do this. Do you need the Mail app full screen? If you need reading glasses, maybe, but otherwise, nope. I find it's easier just to stretch out an app pretty big and leave it at that.
Full screen apps DO offer a nice feature which is making your desktop, menubar, and dock go BYE BYE. I can see where sometimes this is a useful feature, but typically -- NOPE. Typically I want access to my dock (to switch between open apps without the added step of cancelling full screen first), and typically I want access to my menubar so that I can glance up and see what time it is or find an app menu quickly.
The only feature I find worthy of praise with full screen apps is that they hide the clutter on your desktop. But there's an app in the Mac App Store which makes your desktop icons vanish with the touch of a button (CAMOUFLAGE). I mean, what's the point of a wallpaper if you bury it with desktop clutter or eliminate it with full screen apps? If it's a busy and distracting wallpaper, umm... you picked bad wallpaper.
LAUNCH PAD
LAUNCH PAD offers an iOS experience inside OS X. At first I thought it was completely silly. After a month now, I kinda get why it's there. Kinda.
You see, before LP, to duplicate it's functionality, you'd have to organize folders yourself. Put folders of various apps together. Place them somewhere in the finder heirarchy. Then drag those folders into the part of the dock with the trashcan. Then you could click them open and have access to similarly themed folders of apps. The problem here, of course, is that unless you're a power user, you'll never do this.
So Apple thought, AH-HA, we'll just drag into OS X a paradigm that users already get from iOS. Clumping apps together any way you like them. The misfire, if you ask me, is not allowing users to drag the new iOS folders straight into the dock when finished. That is to say: copies of said organized folders. It's as if Apple's software people have complete contempt for the dock -- and are desperate to have users abandon it.
My problem is that I like having folders in my dock of stuff I need. It just works, as Steve says. Going to the same EXACT place every time I need anything is more intuitive and graceful than ADDING an app called Launchpad that launches you into a different finder altogether. Makes zero sense and THIS is why I say, like FULL SCREEN APPS, LP can basically be abandoned.
By the way: need proof that Apple has complete contempt for the Dock?
MISSION CONTROL/SPACES
A month has passed since MC was introduced and SPACES was eliminated. I dare anyone to tell me why either is needed at all. Before you get iMiffed, humor me for a moment and hear me out.
The notion of SPACES was that it's a neat way to keep like minded open apps together. I totally bought into this, back in the day. So much so that I was iMiffed when it was gone in Lion. But let's look at this closer.
The REASON why we needed SPACES was that we could have WAY too many windows open at once on a Mac. Right? A big mess of windows covering each other up. Suppose you're surfing in Safari but need iTunes? But iTunes is hidden. So what did you do? You went to Spaces as step one, moused over to your iTunes space as move two, and then clicked it as move three. Seems like a great solution until the day you discover that you could simply click on iTunes in the dock as move one and arrive at iTunes. As one step. Period. Really simple, right?
Why have Spaces and apps dance around when you can just click the app you want and be done with it? That's the critical observation to make in order to follow my entire line of reasoning. Sure, it may look really cool and make Windows machines look like junk, but at the end of the day, why add two steps to something you might do 100 times a day -- switching between apps.
So why OH why did Apple add Spaces? Simple: because too many apps were visible at once in one 'desktop' window. So if you can build many new desktops, there might only be one or two in each. Great solution. Right?
Wrong, as it turns out. Because we still have the two extra steps. It's a weak solution. And it's in complete contempt of the Dock, which as it turns out, offers the strongest solution.
The strong solution would be that only one app is visible in your Mac's window at all times. Say you're in Safari. Despite having 12 other apps open, you only see Safari. Your dock tells you that you have other apps open, but nothing else sits in your window BUT the app you're using. So you want to go to iTunes? So click on it in the dock and Safari vanishes and iTunes emerges by itself. No other windows. What could be simpler? (This app is freeware known as ISOLATOR.)
If you download and try ISOLATOR, you'll say, umm, okay, but wait: sometimes I do want more than one window in view. Okay, fine, turn it off then. From the handy menu bar menu. I find that 98% of the time I need ISOLATOR on. Mileage may vary.
So let's recap. One third party software removes distracting desktop clutter, the other removes distracting app windows. Both can be toggled on and off from the menu bar. One is free, one costs $2. These two solutions remove the only real feature of FULL SCREEN APPS and make SPACES and it's newfangled cousin MISSION CONTROL pointless.
Need that last one explained? Well, what's Mission Control but a variant of spaces? To invoke MC and switch to the needed window are those same two annoying steps Spaces added into the mix. Nothing was fixed. Plus, like spaces, you must invest time and energy organizing such spaces.
Why bother? And so I ask again: can somebody who's read and tried the above carefully explain to me why Mission Control, Launchpad, and Full Screen Apps are really needed at all? (Outside of small screened Macs.) Doesn't the dock and these two sharewares together solve most problems?
Am I missing something?

I agree with everything you said about full screen apps, mission control and launchpad. For apps that made sense to run full screen, they already could under SL. Launchpad is totally unnecessary and Mission Control is a mere shadow of Expose and Spaces.
However, I feel you have not given due credit to Spaces. The point of Spaces is to let one organise logical desktops for different tasks, not just a way to reduce the number of windows on display. For example, I have a Space for software development where I run Xcode and the iPhone simulator, a Firefox window showing perhaps documentation or some other websites pertaining to software development, a Finder window that is opened in the folder with my design docs. I have another Space where I have the remote login sessions, yet another Space with another Firefox window where I do general surfing and emailing. I can switch between these spaces using a keyboard shortcut, which is much quicker than having to lift my hand off the keyboard, move it over to the mouse, move the mouse pointer over the Dock, find the app and click on it, only to find that it has switched to the wrong window of the app.
Without Spaces, organisation of my desktop is disrupted each time I want to switch task, whereas Spaces allows me to drop everything I am doing, go and do something completely different for a while and go back to my exact previous environment. I have a 27" iMac so am not short of screen space but I use Spaces extensively. BTW, switching Spaces using a keyboard shortcut is a lot faster on SL than the equivalent on Lion, thanks to the gratuitous screen animation of the latter.

Extreme poor quality in full screen preview and exported movie

I have spend evenings and evenings to create the content of a project.
After dealing with error -108 and extreme poor quality in full screen preview and in exported movies (extreme stuttering) I decided to install my iMac new again.
The error -108 disappeared, but the extreme stuttering still remained in full screen preview and in exported movies.
If I make the preview screen in the iMovie browser as big as possible there is nothing to see of any stuttering.
Now I am getting pretty annoyed and have no clue what to do anymore (how to solve this problem) .....
Anyone any suggestion ?
The orginal video was recorded with a Panasonic HD camcorder.
I do have a mid 2011 iMac with 16GB ram and 256GB SSD and 1TB HD with a complete clean installation
of OS X Lion and iLife. This configuration should be enough to create a proper movie :-(

mantralightroom wrote:
why is it this option disabled? do the generate monitor sized previews increase a lot the cache a lot!
Potentially, yes. The standard Preview is 1024 pixels, longest size. Some people (like Omke) have displays 2560 pixels longest side, potentially increasing file size by over 500%.

[solved]screen borders and full sized window emerald compiz

Similar Messages

Maybe you are looking for