Re: [oss-devel] [PATCH] ossxmix minimize to tray

2008-02-03 Thread Hannu Savolainen
Hi, The problem was that the vmix driver didn't increment modify_counter. Best regards, Hannu --- Hannu Savolainen kirjoitti: > > This may be one reason. However it's also possible that the vmix core > doesn't update mixer_devs[]->modify_counter properly when the external > app changes the

Re: [oss-devel] [PATCH] ossxmix minimize to tray

2008-02-03 Thread Yair K.
(It appears the list didn't recieved my last e-mail, so I'm sending it again). On Sunday 03 February 2008 14:48:45 Yair K. wrote: > On Sunday 03 February 2008 14:06:11 you wrote: > > Slightly off topic, why does vmix0-vol mono-slider not get updated in > > ossxmix when its value gets changed as a

Re: [oss-devel] [PATCH] ossxmix minimize to tray

2008-02-03 Thread Hannu Savolainen
Clive Wright kirjoitti: > Yair K. wrote: > >> On Sunday 03 February 2008 03:58:56 Yair K. wrote: >> >>> On Sunday 03 February 2008 03:36:29 Clive Wright wrote: >>> Re. 4.B No need to create an extra variable (aval) just move set_value function call between val assignme

Re: [oss-devel] [PATCH] ossxmix minimize to tray

2008-02-03 Thread Yair K.
On Sunday 03 February 2008 14:48:45 Yair K. wrote: > On Sunday 03 February 2008 14:06:11 you wrote: > > Slightly off topic, why does vmix0-vol mono-slider not get updated in > > ossxmix when its value gets changed as a result of an external event? > > Is it because widgets that have their parent eq

Re: [oss-devel] [PATCH] ossxmix minimize to tray

2008-02-03 Thread Yair K.
On Sunday 03 February 2008 14:06:11 you wrote: > Slightly off topic, why does vmix0-vol mono-slider not get updated in > ossxmix when its value gets changed as a result of an external event? > Is it because widgets that have their parent equal to zero get handled > differently to other widgets? If

Re: [oss-devel] [PATCH] ossxmix minimize to tray

2008-02-03 Thread Clive Wright
Yair K. wrote: > On Sunday 03 February 2008 03:58:56 Yair K. wrote: >> On Sunday 03 February 2008 03:36:29 Clive Wright wrote: >>> Re. 4.B >>> No need to create an extra variable (aval) just move set_value function >>> call between val assignments. >> The problem is that set_values can detect a mix

Re: [oss-devel] [PATCH] ossxmix minimize to tray

2008-02-02 Thread Yair K.
On Sunday 03 February 2008 03:58:56 Yair K. wrote: > On Sunday 03 February 2008 03:36:29 Clive Wright wrote: > > Re. 4.B > > No need to create an extra variable (aval) just move set_value function > > call between val assignments. > > The problem is that set_values can detect a mixer structure chan

Re: [oss-devel] [PATCH] ossxmix minimize to tray

2008-02-02 Thread Yair K.
On Sunday 03 February 2008 03:36:29 Clive Wright wrote: > Re. 4.B > No need to create an extra variable (aval) just move set_value function > call between val assignments. > The problem is that set_values can detect a mixer structure change, so it calls reload_gui (). After that, we don't know th

Re: [oss-devel] [PATCH] ossxmix minimize to tray

2008-02-02 Thread Clive Wright
Yair K. wrote: Hi, Attached are two patches to ossxmix. The first patch (-cmerge) has some more cleanups: 1. update manpage to latest changes. 2. staticize all global variables. 3. check all mallocs for failure. 4. merge issues: A. Declare prototype for create_widgets. B. Is set

[oss-devel] [PATCH] ossxmix minimize to tray

2008-02-02 Thread Yair K.
Hi, Attached are two patches to ossxmix. The first patch (-cmerge) has some more cleanups: 1. update manpage to latest changes. 2. staticize all global variables. 3. check all mallocs for failure. 4. merge issues: A. Declare prototype for create_widgets. B. Is setting val twice in