kicad-developers team mailing list archive
Mailing list archive
Re: Something odd with Eeschema GAL
Le 15/10/2018 à 18:58, Seth Hillbrand a écrit :
> Hi Jeff/JP-
> I pushed a small patch to address this (bf164f7c4)
> The resize event triggered the compositor to change sizes. This needed
> to be locked to avoid the context writing into a bad size.
> Let me know if it still causes issues under W7 32.
Your patch fixes all issues I found when using opengl!
You are a genius.
> Am Mo., 15. Okt. 2018 um 08:39 Uhr schrieb Jeff Young <jeff@xxxxxxxxx
> That’s the same bug that was being triggered on OSX with grid
> settings (and originally resulted in a deadlock before I switched
> GAL to RAII context locking).
> I spent a couple of days on it but came up blank (other than that I
> suspected it was a result of drawing into a wrongly-sized buffer,
> which your case would support).
> > On 15 Oct 2018, at 16:32, jp charras <jp.charras@xxxxxxxxxx
> <mailto:jp.charras@xxxxxxxxxx>> wrote:
> > Le 14/10/2018 à 20:28, jp charras a écrit :
> >> Le 14/10/2018 à 20:02, Jeff Young a écrit :
> >>> Yeah, the AdvanceDepth() needs to go between the fill and the
> stroke, rather than between the component and its children. I’ll
> look into it.
> > I just found an other very serious issue, fully reproductible, at
> > on W7 32 bits.
> > It happens when both Eeschema and Pcbnew are in Opengl mode, and when
> > the frames have a overlapping area:
> > When trying to resize a frame (Pcbnew frame for instance), if the
> > overlapping area is modified (size of overlapping area changed when
> > resizing the frame) the screen of the frame behind the resized frame
> > becomes blank.
> > If I try to zoom inside the blank screen (Eeschema for instance),
> I have
> > the error:
> > Error: switching framebuffer: invalid framebuffer operation
> > and the fallback mode is set.
> > It looks to me the wxPaintEvents create an issue, by I need a
> Opengl guru.
> > However Kicad crashes on exit.
> > Is just on my install?
> > --
> > Jean-Pierre CHARRAS