[FusionDev] ccsm int/float options

[Patrick Niklaus]

Hey,

on the other hand I have quite a few users which are complaining
"changing settings is slow".
The focus-out changes are obviously a real performance increase for
those people.
Using the 'changed' signal instead of all that combinations of
'focus-out' / 'button-press-up' / 'activate' signal is of course
cleaner, code-wise.
However if someone could point me out how to catch mouse-wheel events
for those settings widgets, that might solve the problem as well.

Regards,
Patrick

2007/8/16, Erkin Bahceci <erkinbah at gmail.com>:
> Hi guys,
>
> How is it going?
>
> I thought this bug was fixed, but looks like it's still a problem with
> the git version. I'm no expert in gtk api, but if there is no way to
> capture mouse wheel with this new version, can we revert to the old
> state where mouse wheel worked? Because that looked much less buggy.
> As it is now, I change many options and they all seemingly change on
> the interface, but the changes are not actually applied. This (having
> no changes applied) is much worse (and annoying) than having changes
> applied a little more frequently. Don't you think so?
>
> This is quite important because mouse wheel is much more convenient
> and faster to use than click-drag-release (or possibly
> click-release-move-click-release for selection lists). So, many people
> (including myself) will prefer using the mouse wheel. And this is not
> only for sliders. Selection lists are also affected by this bug. I
> think we should revert that "apply on focus-out" commit(s?) until a
> better solution (that won't break mouse wheel functionality) is found.
>
> Cheers,
> Erkin
>
>
> On 8/3/07, Patrick Niklaus <patrick.niklaus at googlemail.com> wrote:
> > Hi,
> > I'm a bit unsure how to fix this properly. Some users reported that
> > changing int/float settings on their system would be really slow. So I
> > changed the method of updating from using the 'value-changed' signal
> > to using 'button-release-event' and 'activate' (triggered by pressing
> > enter).
> > I have no idea how I could combine this methods to provide a mouse
> > wheel support. Anyone an idea?
> > However typing the value should work.
> >
> > Regards,
> > Patrick
> >
> > 2007/8/3, Erkin Bahceci <erkinbah at gmail.com>:
> > > Oh, it was the recent focus change. Currently changing an option with
> > > mouse wheel or by typing the value doesn't work. Does it work there?
> > >
> > > Thanks,
> > > Erkin
> > >
> > > On 8/3/07, Erkin Bahceci <erkinbah at gmail.com> wrote:
> > > > Hi guys,
> > > >
> > > > Am I doing something wrong or is ccsm not setting int & float options
> > > > anymore? (other options work fine) Do you have this issue?
> > > >
> > > > - Erkin
> > > >
> > >
> >
>