On 3/29/07, David Reveman <[EMAIL PROTECTED]> wrote:
On Wed, 2007-03-28 at 22:09 -0400, Kristian Høgsberg wrote:
> Hi,
>
> We still carry this patch in our RPM which really should be upstream.
> What it does is terminate a keyboard initiated move when a mouse
> button is clicked. Try Alt-F7, mov
On 3/29/07, David Reveman <[EMAIL PROTECTED]> wrote:
On Wed, 2007-03-28 at 21:08 -0400, Kristian Høgsberg wrote:
> On 3/28/07, dragoran <[EMAIL PROTECTED]> wrote:
> > Hello,
> > After trying to solve a issue with desktop-effects in fedora (compiz
> > does not let itself to be replaced by metacity
On Thu, 2007-03-29 at 19:54 +0100, Mike Dransfield wrote:
> David Reveman wrote:
> > On Wed, 2007-03-21 at 16:02 +, Mike Dransfield wrote:
> >
> >> I got this whilst changing to the laptop theme.
> >>
> >> It happens both with changing to laptop and starting with it enabled.
> >>
> > >F
David Reveman wrote:
I'd like to get a 0.4 release out sometime soon.
Is this still planed to be out soon?
head looks quite stable now and works fine for me (except the bug I
submitted(window on all workspaces); which seems like a libwnck bug)
___
co
On Wed, 2007-03-28 at 22:09 -0400, Kristian Høgsberg wrote:
> Hi,
>
> We still carry this patch in our RPM which really should be upstream.
> What it does is terminate a keyboard initiated move when a mouse
> button is clicked. Try Alt-F7, move the window with the mouse, and
> then click a mouse
On Wed, 2007-03-28 at 21:08 -0400, Kristian Høgsberg wrote:
> On 3/28/07, dragoran <[EMAIL PROTECTED]> wrote:
> > Hello,
> > After trying to solve a issue with desktop-effects in fedora (compiz
> > does not let itself to be replaced by metacity).
> > We come to the conclusion that the compiz sessio
On Wed, 2007-03-28 at 20:38 +0200, dragoran wrote:
> Hello,
> After trying to solve a issue with desktop-effects in fedora (compiz
> does not let itself to be replaced by metacity).
> We come to the conclusion that the compiz session management code is broken.
> When unmanaging the screen compiz s
David Reveman wrote:
On Wed, 2007-03-21 at 16:02 +, Mike Dransfield wrote:
I got this whilst changing to the laptop theme.
It happens both with changing to laptop and starting with it enabled.
>From the back-trace it looks like it's related to the code between line
1382 and line 14
I think it makes sense to allow code execution before and after the change.
Regards,
Erkin
On 3/29/07, David Reveman <[EMAIL PROTECTED]> wrote:
I've been thinking about removing all existing notification functions in
favor of just having functions that apply changes. This is better as it
allow
On Sun, 2007-03-25 at 20:56 +0200, Bellegarde Cedric wrote:
> Here a patch to enable Vertical/Horizontal maximization in
> gtk-window-decorator.
You would prefer if you avoid duplicating
if (d->button_states[BUTTON_MAX] == BUTTON_EVENT_ACTION_STATE)
{
and
d->button_states[BUTTON_MAX] &= ~PRESS
This particular notification is not necessary for the animation plugin
anymore (in Animation, I just had to add a few simple lines on
ConfigureNotify to reach the notification point I wanted in
restackWindow()).
Looking forward to your new drawing framework.
Regards,
Erkin
On 3/29/07, David Rev
On Wed, 2007-03-28 at 21:37 -0500, Erkin Bahceci wrote:
> Hi,
>
> Here is the latest animation plugin. I got rid of the need for the
> "window restacking notification" patch by handling the ConfigureNotify
> event (as done for restackWindow()). Btw, _NET_CLIENT_LIST_STACKING
> change notification
On Sat, 2007-03-24 at 12:32 -0500, Erkin Bahceci wrote:
> Hi,
>
> This patch adds notification on window restacking. Plugins may need to
> do something when that happens. For example, it is used in the new
> version of animation plugin to perform a fade effect when a window
> moves above or below
I've been thinking about removing all existing notification functions in
favor of just having functions that apply changes. This is better as it
allow each plugin to execute something both before and after the change
has been applied. Example:
Instead of wrapping a windowStateChangeNotify function
On 3/28/07, David Reveman <[EMAIL PROTECTED]> wrote:
> I think there's a common misunderstanding here. I don't think anyone
> really wants a person who doesn't contribute a significant amount of
> code to lead the project. But at the same time, we're (at least I am)
> a bit afraid of letting a si
On Wed, 2007-03-21 at 16:02 +, Mike Dransfield wrote:
> I got this whilst changing to the laptop theme.
>
> It happens both with changing to laptop and starting with it enabled.
>
> Starting program: /usr/bin/kde-window-decorator --sync --replace
> [Thread debugging using libthread_db enabled
On Mon, 2007-03-19 at 07:29 -0500, Travis Watkins wrote:
> As the subject says, moveWindowToViewportPosition only takes an x
> argument. Shouldn't it have a y argument too for vertical viewports?
Yes
- David
___
compiz mailing list
compiz@lists.freedes
On Sat, 2007-03-17 at 08:20 +0200, Pyry Haulos wrote:
> Hi,
>
> I've been experiencing serious tearing in compiz when screen is painted only
> partly. Either "Sync To Vblank" option in compiz doesn't work or copying
> repainted parts from backbuffer to frontbuffer is too slow. And since many
>
We could set up bcop to generate the code for a library for each
plugin that just contains the functions required to get the settings.
Furthermore these settings could be represented through some
hypothetical CompOptionMetadata struct which could contain all the
useful metadata we want.
With some
On Thu, 2007-03-15 at 02:54 +0100, Dennis Kasprzyk wrote:
> Am Montag, 5. März 2007 12:12 schrieb David Reveman:
> > I've added a simple plugin to compiz that provides a way to render video
> > efficiently on a composited desktop.
> >
> > A video playback client basically copies video data to a pix
Danny Baumann wrote:
I disagree. There are different usage models, reflected best by having
different settings managers. Beginner users may want an
as-simple-as-possible settings manager (such as desktop-effects),
average users may want a settings manager which provides some more
settings (such a
Dennis Kasprzyk wrote:
The problem is that we already have additional data in the plugins. So we
should be consistent here and remove also the long/short decriptions of the
option struct and or the plugin vtable and move it to an additional file or
have everything in the plugin. A mixture of
Hi,
> I think in the long term, the autogenerated settings managers
> will be replaced with hard coded user friendly ones, this will
> leave all of these extra attributes with nowhere to go.
I disagree. There are different usage models, reflected best by having
different settings managers. Beginn
Travis Watkins wrote:
On 3/29/07, Mike Dransfield <[EMAIL PROTECTED]> wrote:
> 2. No convenient way to get the initial value of an option once it's
> been modified.
>
No, this was my problem when writing ini.
The way I see it is that gconf should be able to revert to
the default easily, ini mi
Fixed schema file.
On 3/28/07, Erkin Bahceci <[EMAIL PROTECTED]> wrote:
Hi,
Here is the latest animation plugin. I got rid of the need for the
"window restacking notification" patch by handling the ConfigureNotify
event (as done for restackWindow()). Btw, _NET_CLIENT_LIST_STACKING
change notifi
Am Donnerstag, 29. März 2007 17:54 schrieb Bellegarde Cedric:
> Le jeudi 29 mars 2007, Dennis Kasprzyk a écrit :
> > Currently there are two types of configuration tools. Some with fixed
> > functionality and some autogenerated. To improve the quality of the
> > autogenerated tools I would like to
On 3/29/07, Mike Dransfield <[EMAIL PROTECTED]> wrote:
> 2. No convenient way to get the initial value of an option once it's
> been modified.
>
No, this was my problem when writing ini.
The way I see it is that gconf should be able to revert to
the default easily, ini might need some work.
I
Le jeudi 29 mars 2007, Dennis Kasprzyk a écrit :
> Currently there are two types of configuration tools. Some with fixed
> functionality and some autogenerated. To improve the quality of the
> autogenerated tools I would like to make this proposal about additional
> values in the CompOption struct
David Reveman wrote:
Dennis Kasprzyk and I have been discussing some changes to how options
are initialized.
Problems with how options are currently initialized.
1. Helper functions are not used to initialize options, which means that
if we make a change to the option structure, all option init
Dennis Kasprzyk wrote:
Additions to the CompOption struct:
char * group/char * subgroup : Ability to group sets of options and to give
this sets a name.
I think that subgroup (and probably group) are excessive
and they lead to the plugin writer designing the UI which
is not right. From wha
Am Donnerstag, 29. März 2007 11:02 schrieb David Reveman:
> Dennis Kasprzyk and I have been discussing some changes to how options
> are initialized.
>
> Problems with how options are currently initialized.
>
> 1. Helper functions are not used to initialize options, which means that
> if we make a
Dennis Kasprzyk and I have been discussing some changes to how options
are initialized.
Problems with how options are currently initialized.
1. Helper functions are not used to initialize options, which means that
if we make a change to the option structure, all option initialization
code needs t
32 matches
Mail list logo
