similar to: Desktop behaviour - click to raise

Hi. I am using latest wine but i got prob here... when i run game in virtual desktop, it will apear in nice window with borders...etc which i want to disable of course. Using Gnome with Metacity window manager. On KDE i can disable borders fine, but here only close button is enable others like minimize example are disabled. And i can't full screen it with shortcut. Cedega works fine on this

With raise_on_click disabled, I wanted to be able to raise a window with a button click sometimes. It seemed logical to do something like the lower window key binding. So I did it. It was quite simple, but here is the patch anyway. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/octet-stream Size: 3680 bytes Desc: not available

Hi, I have a strange problem with gtk-window-decorator. I've tried 0.3.6 & the latest from git, but with either I don't get any window borders when running gwd. I hope its not something simple I've missed but I've searched around and not found anything. gwd never segfaults or even displays any warnings or anything for that matter. It just doesn't draw the borders. I've

Hello, I just tried a gnome login with an empty home directory on a samba mounted directory, and this resulted in several files with strange characters in the filenames in the end. (as created by the initial gnome login) I cannot reproduce this by hand, and it certainly does not happen when I do the login on a local directory, or when I copy that local directory to the samba directory. I use

Hello, I'm developing a fancy screenshot application for the GNOME-desktop using GTK and GDK libraries (and some Xlib stuff too). When taking a screenshot of a window, my code first finds out in which desktop the window lies (resides) and then moves to that desktop and takes a screenshot. This is quite easy to do under the Metacity window manager, but I cannot make this work right in Compiz

It seems it's not possible to monitor kvm virtual image network interfaces via SNMP. MRTG's cfgmaker says ### The following interface is commented out because: ### * has no ifSpeed property and other monitors are consistently reporting that vm's interfaces are exceeding traffic thresholds (even on lo ...). Which is no surprise if the threshold is zero. I found a hint on some

Hi Everyone, I'm going to make some big structural cleanups to core which is likely to affect everyone here, but I believe is for the better, so I am posting this mail now to get some feedback and make sure that we don't tread on anyone's toes when I merge all of this stuff. 1st Change: Decorators are going in their own repo ========================================= The decorators

hi, I made a small a patch for gtk-window-decorator which define default border alpha to zero when it use metacity theme. That allows while playing with the alpha attributes of the metacity themes to have transparent borders. here too the modified ?Human Ubuntu? theme and a screenshot to show the result. ps: sorry for my bad english -------------- next part -------------- A non-text attachment

I just pushed some code into the compiz repository for initial metacity theme support. It's not complete, left and right borders are not rendered correctly, button decorations doesn't always match event window locations, maximized and shaded windows are not rendered as when running metacity, button locations are not configurable as with metacity... but it still seem to look OK with most

Changes since 0.3.2: * Core Support for multiple desktops (workspaces). Much better multi-head support. The workarea is calculated per output and windows are now maximized properly. Edge button option has been added to action options. It can be used to require a button press for edge actions to be triggered. Basic support from internal

I have configured compiz to use 1 workspace and 4 viewports and metacity to use 4 workspaces. When I start compiz while metacity was running it uses 4 workspaces and 4 viewports (ignoring the gconf settings). When I restart X so that compiz is started before metacity this does not happen (it uses what its configured for). bug or feature? if feature can it be disabled? switching

I'm trying to define my long time keyboard shortcuts in compiz on a new FC6 system with gnome. I want <Alt>n to run a shell and <Shift><Alt>p for pan. In metacity I could set the shell shortcut from System->Preferences->keyboard shortcuts, and for something like pan (which was not in the menu) I could do it in gconf-editor (apps->metacity, etc.). Since neither the

Hello. I'm using compiz-vanilla, and I have noticed that it makes Nautilus act extremely slow on my desktop; for example, if I select several icons quickly the selection box becomes quite choppy, and if I try to move them there is a huge "lag". I noticed that Nautilus behaves completely normal on non-desktop windows, though, and if I replace compiz with metacity (metacity --replace)

This is a problem I've had on and off under CentOS5 and CentOS6, with both xen and kvm. Currently, it happens consistently with kvm on 6.5, e.g. with every kernel update. I *think* it generally worked fine with the 6.4 kernels. There are 7 VMs running on a 6.5, x86_64, 8GB RAM host, each with 512MB RAM and using the e1000 NIC. I picked this specific NIC because the default does not allow

I pushed out some changes to gwd that makes it possible to properly set an overall opacity value for any metacity theme. Making the complete decorations translucent can look bad with some themes. However, I've made it possible to have the opacity fade from opaque to the selected opacity value in a similar way to how the built-in decorations look. This usually looks a lot better. I'll add

On Sat, Dec 20, 2014 at 4:15 PM, Tim <rintimtim at gmx.net> wrote: > Then I would do it with a group policy. Have a look right here: > http://technet.microsoft.com/en-us/library/ee791928(v=WS.10).aspx > > Remind that you leave the default policies untouched. Create a new GPo and > link it to your desired OU. > After put domain users in the remote destop group in the DC,

I noticed there have been some older posts about a work in progress patch which never made it to the ML due to some issues. I am attaching three patches here in an effort to bring the button_layout support into gtk-window-decorator which allows you to define the titlebar button placements with a string (e.g. "menu:minimize,maximize,close") in /apps/metacity/general/button_layout. #

I've added a working KDE window decorator (kwd) to head. It's pretty much written from scratch however it borrows some trivial code from aquamarine which I didn't feel re-implementing. So why did I write a new one from scratch instead of improving aquamarine? I started out by trying to improve aquamarine but as I looked at the code and figured out what had to change to make it work

On Sat, Nov 20, 2010 at 3:25 PM, Lars Hecking <lhecking at users.sourceforge.net> wrote: > ?Possibly. Or possibly not. On a closely related topic, can you comment on > ?whether or not it's a good idea to install the nspluginwrapper rpms on x86_64? > ?They seem to be fundamentally broken. > I don't think you need it anymore with FF 3.6.

Processing commands for control at bugs.debian.org: > severity 565026 serious Bug #565026 [libfreebob] libfreebob: ftbfs with gcc-4.5 Severity set to 'serious' from 'important' > severity 564845 serious Bug #564845 [acl2] acl2: ftbfs with gcc-4.5 Severity set to 'serious' from 'important' > severity 564862 serious Bug #564862 [asymptote] amsymptote: