Re: [Kicad-developers] A few run-time problems on kicad-git build on Slackware64-current Linux
Tom, did you create a new build dir when switching from gtk2 to gtk3? On Sat, 7 Nov 2020 at 16:32, Mark Roszko wrote: > The change wouldn't be in KiCad. It's the behavior of your window manager. > Apparently some Linux WMs send mouse events to windows and controls without > focus and others don't. KiCad traditionally assumed it wouldn't receive > mouse events without being activated. > > On Fri, Nov 6, 2020 at 11:33 PM Tom Crane > wrote: > >> Thanks for the explanation. I noticed these problems on moving from >> gtk2 to gtk3 builds. Is this where these changes were made? >> >> Are there likely to be any user selectable runtime options added to Kicad >> to ameliorate these problems? >> >> Tom Crane. >> >> On Thu, 5 Nov 2020, Mark Roszko wrote: >> >> > Your issues in (1) are by design. >> > >> > Whether that design is correct or not is another story. >> > >> > I actually removed that behavior on Windows because Microsoft has a >> stable api to determine top level window for focus. >> > Linux does not and GDK used to be but with the fragmented x11/wayland >> mess, they removed the api call support to determine top level window. >> > >> > And removing the focus calls instead are going to lead a rabbit hole of >> things not working like hotkeys. >> > >> > On Thu, Nov 5, 2020 at 9:14 PM Tom Crane >> wrote: >> > On Thu, 5 Nov 2020, Nick Østergaard wrote: >> > >> > Thanks again for the quick follow-up. >> > >> > > Did you install wxpython (phoenix) with pip? >> > No. >> > >> > > you have some python stuff in ~/.local. >> > >> > I have uploaded the modified SlackBuild scripts I used to build >> both the >> > Slackware wxGTK3 package (wxWidgets/Phoenix) and the wxPython4 >> package at >> > https://www.mklab.rhul.ac.uk/~tom/kicad/SlackBuild/ in case the >> problem >> > lies with either. >> > >> > > >> > > Maybe just try to clear that out completely, or explicitly >> set PYTHONPATH to the site-packages path of your install location? >> > >> > Just tried removing ~/.local and then, >> > >> > export PYTHONPATH=/usr/lib64/python3.8/site-packages/ >> > >> > In both cases the scripting console error remains the same. >> > >> > Thanks >> > Tom. >> > >> > >> > > >> > > On Thu, 5 Nov 2020 at 20:51, Tom Crane < >> tpcki...@mklab.ph.rhul.ac.uk> wrote: >> > > Thanks for the quick response. In the past I have been >> bitten by old >> > > libraries in non-standard places derailing other >> application builds but >> > > can't see anything obviously amiss here. >> > > >> > > My $LD_LIBRARY_PATH EV is empty. I checked where >> ldconfig looks and could >> > > not see anything incriminating outside the standard >> install locations for >> > > Slackware distros (/usr/lib64 & /lib64). See >> > > https://www.mklab.rhul.ac.uk/~tom/kicad/ldconfig-p.txt >> for the O/P of >> > > 'ldconfig -p'. >> > > >> > > I also tried stracing open* calls in pcbnew. See >> > > >> https://www.mklab.rhul.ac.uk/~tom/kicad/strace-pcbnew2.lis. Again >> nothing >> > > jumped out as problematic. All calls to Python related >> files seem to >> > > reference python v.3.8 ones as expected. >> > > >> > > The build scripts I am using are release version >> 'SlackBuild' scripts I've >> > > hacked to use the git development code. See >> > > https://www.mklab.rhul.ac.uk/~tom/kicad/SlackBuild/. >> The tom_build.sh >> > > script calls the main build script kicad-git.SlackBuild. >> > > >> > > Thanks >> > > Tom >> > > >> > > On Thu, 5 Nov 2020, Nick Østergaard wrote: >> > > >> > > > Are you using a build script? If so please link it. >> > > > Also check if you partially installed in multiple >> locations, sucha as where ldconfig looks and echo LD_LIBRARY_PATH from your >> runtime env. >> > > > >> > > > Nicl >> > > > >> > > > tor. 5. nov. 2020 16.26 skrev Tom Crane < >> tpcki...@mklab.ph.rhul.ac.uk>: >> > > > I have been using recent builds for the past few >> weeks. They are usable >> > > > but I have a couple of outstanding problems which >> I'm not sure how to >> > > > diagnose/fix. >> > > > >> > > > (1) I have strange behaviours with open Kicad >> application windows. For >> > > > example I have a Kicad project, eeschema and >> pcbnew windows open on a >> > > > single display. If I let the mouse pointer move >> from the project window to >> > > > the eeschema or pcbnew window then input focus >> immediately transfers to >> > > > the eeschema or pcbnew window. This is
Re: [Kicad-developers] A few run-time problems on kicad-git build on Slackware64-current Linux
The change wouldn't be in KiCad. It's the behavior of your window manager. Apparently some Linux WMs send mouse events to windows and controls without focus and others don't. KiCad traditionally assumed it wouldn't receive mouse events without being activated. On Fri, Nov 6, 2020 at 11:33 PM Tom Crane wrote: > Thanks for the explanation. I noticed these problems on moving from > gtk2 to gtk3 builds. Is this where these changes were made? > > Are there likely to be any user selectable runtime options added to Kicad > to ameliorate these problems? > > Tom Crane. > > On Thu, 5 Nov 2020, Mark Roszko wrote: > > > Your issues in (1) are by design. > > > > Whether that design is correct or not is another story. > > > > I actually removed that behavior on Windows because Microsoft has a > stable api to determine top level window for focus. > > Linux does not and GDK used to be but with the fragmented x11/wayland > mess, they removed the api call support to determine top level window. > > > > And removing the focus calls instead are going to lead a rabbit hole of > things not working like hotkeys. > > > > On Thu, Nov 5, 2020 at 9:14 PM Tom Crane > wrote: > > On Thu, 5 Nov 2020, Nick Østergaard wrote: > > > > Thanks again for the quick follow-up. > > > > > Did you install wxpython (phoenix) with pip? > > No. > > > > > you have some python stuff in ~/.local. > > > > I have uploaded the modified SlackBuild scripts I used to build > both the > > Slackware wxGTK3 package (wxWidgets/Phoenix) and the wxPython4 > package at > > https://www.mklab.rhul.ac.uk/~tom/kicad/SlackBuild/ in case the > problem > > lies with either. > > > > > > > > Maybe just try to clear that out completely, or explicitly > set PYTHONPATH to the site-packages path of your install location? > > > > Just tried removing ~/.local and then, > > > > export PYTHONPATH=/usr/lib64/python3.8/site-packages/ > > > > In both cases the scripting console error remains the same. > > > > Thanks > > Tom. > > > > > > > > > > On Thu, 5 Nov 2020 at 20:51, Tom Crane < > tpcki...@mklab.ph.rhul.ac.uk> wrote: > > > Thanks for the quick response. In the past I have been > bitten by old > > > libraries in non-standard places derailing other > application builds but > > > can't see anything obviously amiss here. > > > > > > My $LD_LIBRARY_PATH EV is empty. I checked where ldconfig > looks and could > > > not see anything incriminating outside the standard > install locations for > > > Slackware distros (/usr/lib64 & /lib64). See > > > https://www.mklab.rhul.ac.uk/~tom/kicad/ldconfig-p.txt > for the O/P of > > > 'ldconfig -p'. > > > > > > I also tried stracing open* calls in pcbnew. See > > > https://www.mklab.rhul.ac.uk/~tom/kicad/strace-pcbnew2.lis. > Again nothing > > > jumped out as problematic. All calls to Python related > files seem to > > > reference python v.3.8 ones as expected. > > > > > > The build scripts I am using are release version > 'SlackBuild' scripts I've > > > hacked to use the git development code. See > > > https://www.mklab.rhul.ac.uk/~tom/kicad/SlackBuild/. The > tom_build.sh > > > script calls the main build script kicad-git.SlackBuild. > > > > > > Thanks > > > Tom > > > > > > On Thu, 5 Nov 2020, Nick Østergaard wrote: > > > > > > > Are you using a build script? If so please link it. > > > > Also check if you partially installed in multiple > locations, sucha as where ldconfig looks and echo LD_LIBRARY_PATH from your > runtime env. > > > > > > > > Nicl > > > > > > > > tor. 5. nov. 2020 16.26 skrev Tom Crane < > tpcki...@mklab.ph.rhul.ac.uk>: > > > > I have been using recent builds for the past few > weeks. They are usable > > > > but I have a couple of outstanding problems which > I'm not sure how to > > > > diagnose/fix. > > > > > > > > (1) I have strange behaviours with open Kicad > application windows. For > > > > example I have a Kicad project, eeschema and > pcbnew windows open on a > > > > single display. If I let the mouse pointer move > from the project window to > > > > the eeschema or pcbnew window then input focus > immediately transfers to > > > > the eeschema or pcbnew window. This is without > touching any mouse > > > > buttons. > > > > > > > > Similarly moving the mouse pointer back to the > project window has no > > > > effect (as it should) but moving it between the
