On 8 December 2012 09:57, Brad Smith <b...@comstyle.com> wrote: > On Thu, Dec 06, 2012 at 12:27:59PM +0100, Mike Belopuhov wrote: >> On 6 December 2012 11:35, Mike Belopuhov <m...@belopuhov.com> wrote: >> > On 6 December 2012 07:44, Brad Smith <b...@comstyle.com> wrote: >> >> On Wed, Dec 05, 2012 at 06:36:27PM +0100, Mike Belopuhov wrote: >> >>> On 5 December 2012 02:25, Brad Smith <b...@comstyle.com> wrote: >> >>> > On Wed, Dec 05, 2012 at 01:46:43AM +0100, Mike Belopuhov wrote: >> >>> >> On 5 December 2012 01:40, Brad Smith <b...@comstyle.com> wrote: >> >>> >> > >> >>> >> > Although the build infrastructure allows for building >> >>> >> > both the Gtk+2 and Gtk+3 support the resulting package >> >>> >> > does not actually work properly trying to use both toolkits. >> >>> >> > So do what actually makes sense and just build with one >> >>> >> > of them. I have also improved the way plugins are handled. >> >>> >> > >> >>> >> >> >>> >> err, the whole point to bring deadbeef was not to use gtk3 >> >>> >> with audacious. i suggest not to convert deadbeef for this >> >>> >> update. do it the next time. >> >>> > >> >>> > What do you mean by next time >> >>> >> >>> next time around if they will fix gtk3. >> >>> >> >>> > If by that you mean next >> >>> > release what difference does it make? >> >>> > >> >>> >> >>> gtk3 apps don't work well in fvwm2. menus get detached and >> >>> start floating around. i've just tested you diff and it makes >> >>> deadbeef unusable. >> >> >> >> To make sure we're on the same page you mean by simply clicking >> >> on the menus at the top where it says File / Edit / View / Playback / Help >> >> and they "detach"? >> >> >> > >> > yup. and besides gtk3 looks like crap. so would you be so kind >> > to stop wasting my time with this and use gtk2 for deadbeef for >> > the time being. >> > >> > cheers >> >> managed to get some screenshots: > > I don't see anything like that. But the most important question first.. > is your system fully up to date with packages, especially gtk+3 being > at version 3.6.2? >
system was updated prior to testing. and it's been like that since forever or do you mean 3.6.2 fixes this issue?
