Re: [Bino-list] Dual screen not working on windows

[Martin Lambers]

Hi Pedro,

another possibility is that multi-screen handling is handled
differently on different desktop environments. Which Windows version
are you using? I never got feedback for anything newer than Windows 7.
And which desktop are you using on Ubuntu? It may have something to do
with that, but I'm not sure.

Regards,
Martin

On Fri, 29 Dec 2017 01:19:42 +0000, Pedro Silva Pinto wrote:
> Hi Martin,
> 
> Glad to read back from you.
> My working 1.6.0 version uses Qt 4.8.5.
> 
> I compiled again Bino 1.6.5 in Ubuntu and get same results whether I
> use Qt 4 or 5: fullscreen works in single screen, despite having set
> dual screen mode.
> 
> I also compiled Bino 1.6.5 for windows (in Ubuntu 17.10 with MXE)
> following your README.WINDOWS file, but using Qt version 5 instead of
> 4. It compiles OK, installs on windows, but upon launching I get this
> error:
> 
> bino: [err] This application failed to start because it could not
> find or load the Qt platform plugin "windows"?in "".??Reinstalling
> the application may fix this problem.
> 
> Still, getting the same behavior on Ubuntu both with Qt 4 and 5 baybe
> an indication that the problem isn't related to the Qt version. I can
> make further tests, but need some guidance. :) Cheers!
> 
> Pedro
> 
> -----Original Message-----
> From: Martin Lambers [mailto:address@hidden 
> Sent: 27 de dezembro de 2017 20:26
> To: address@hidden
> Cc: Pedro Silva Pinto <address@hidden>
> Subject: Re: [Bino-list] Dual screen not working on windows
> 
> Hi Pedro,
> 
> the project is not abandoned, but needs more developer time.
> 
> I do not use Windows and currently don't even have access to a
> multi-screen system, so I cannot really track this problem down.
> 
> However, there were no relevant source code changes between 1.6.0 and
> 1.6.1. In fact, the enter_fullscreen() function has not been changed
> in years. So my guess is it depends on the Qt version used. Maybe
> look into Help->About->Libraries to find out which Qt version your
> working 1.6.0 binary uses, and/or try to build with the latest Qt
> version.
> 
> Best,
> Martin
> 
> 
> On Tue, 26 Dec 2017 15:37:47 +0000, Pedro Silva Pinto wrote:
> > No reply after a month; was the project abandoned by their
> > developers? :(
> > 
> > 
> > From: Bino-list
> > [mailto:address@hidden On
> > Behalf Of Pedro Silva Pinto Sent: 24 de novembro de 2017 13:12 To:
> > address@hidden Subject: Re: [Bino-list] Dual screen not
> > working on windows
> > 
> > Hi all,
> > 
> > I wanted to dig a little deeper and I tried Bino dual screen mode
> > in Ubuntu. I tested on Ubuntu 17.10, on different hardware from my 
> > previous tests. Compiled Bino 1.6.5 from source code myself (no 
> > equalizer and with qt4). Input was left/right, half width; output
> > was left/right. Same result: full screen displays only in the
> > screen where the main window is. I also tried the Bino version
> > included in the Ubuntu release, but it crashes when playback
> > starts. So, dual screen mode isn’t working both in Windows and
> > Ubuntu. Trying earlier versions (on windows), it does work on
> > version 1.6.0.
> > 
> > Pedro
> > 
> > From: Bino-list
> > [mailto:address@hidden On
> > Behalf Of Pedro Silva Pinto Sent: 19 de novembro de 2017 12:19 To:
> > address@hidden<mailto:address@hidden> Subject:
> > [Bino-list] Dual screen not working on windows
> > 
> > Hi,
> > 
> > It’s been a long time since I last used Bino and last weekend I
> > needed to present a 3D movie. I’ve always used it on Windows and
> > now am using version 1.6.5. I set up my rig and when I tried to set
> > up the dual screen mode, I just couldn’t. Sure enough, the
> > interface detects the screens, and the selection menu works OK;
> > it’s just that the full screen always shows on the screen where the
> > main window is. No image goes to the screens I selected on the
> > menu. As I was sure Bino could do it, I tried older versions, which
> > I had kept. Version 1.6.1, same problem. On version 1.6.0,
> > everything worked! Is there some bug inserted into the code between
> > versions 1.6.0 and 1.6.1?
> > 
> > Cheers!
> > 
> > Pedro  
>