Re: [Kicad-developers] Spate of bugs in global fields editor (aka BOM editor)

Got you a fresh batch https://bugs.launchpad.net/kicad/+bug/1765443 <- this one helped me lose a few hours of work https://bugs.launchpad.net/kicad/+bug/1765446 https://bugs.launchpad.net/kicad/+bug/1765447 On Tue, Apr 17, 2018 at 5:59 AM, Jeff Young wrote: > Turned out to either be not as bad

Re: [Kicad-developers] Spate of bugs in global fields editor (aka BOM editor)

Turned out to either be not as bad as I thought, or most of the work will be in fixing my 6.0 tree. Either way, I merged it into master. Should fix: https://bugs.launchpad.net/kicad/+bug/1749287 https://bugs.launchpad.net/kicad/+bug/1737361 https://bugs.launchpad.net/kicad/+bug/1759756 https://

Re: [Kicad-developers] Spate of bugs in global fields editor (aka BOM editor)

Please let me know how much effort is involved on your part and we can make a decision from there. Thanks, Wayne On 4/16/2018 1:18 PM, Jeff Young wrote: > Can I? Certainly. > > Without tearing my hair out? Much more questionable. ;) > > I’ll look into it…. > >> On 16 Apr 2018, at 18:10, Way

Re: [Kicad-developers] Spate of bugs in global fields editor (aka BOM editor)

Can I? Certainly. Without tearing my hair out? Much more questionable. ;) I’ll look into it…. > On 16 Apr 2018, at 18:10, Wayne Stambaugh wrote: > > Is there any way you could do this without dragging in all of the other > changes? If we cannot fix the current table editor, I'm OK with > up

Re: [Kicad-developers] Spate of bugs in global fields editor (aka BOM editor)

Is there any way you could do this without dragging in all of the other changes? If we cannot fix the current table editor, I'm OK with updating to the wxGrid based design but I would prefer to keep the changes to just the table editor. On 4/16/2018 6:02 AM, Jeff Young wrote: > Given the spate of

Re: [Kicad-developers] Spate of bugs in global fields editor (aka BOM editor)

Hi Martin, We’re currently talking about the “BOM editor” rather than the “Fields editor”. (Click the spreadsheet icon in the eeschema’s top toolbar to get the “BOM editor”. That being said, I have also wxGrid-ized the Fields editor, which can be seen here: https://git.launchpad.net/~jeyjey/

Re: [Kicad-developers] Spate of bugs in global fields editor (aka BOM editor)

There is also: https://bugs.launchpad.net/kicad/+bug/1729373 and some of these also apply to the global fields editor: https://bugs.launchpad.net/kicad/+bug/1764053 My 6.0 commit can be found here:

Re: [Kicad-developers] Spate of bugs in global fields editor (aka BOM editor)

Hi Jeff, Are you referring to lp:#1761378 [1] and lp:#1763223 [2] or there are more bugs? If you have the commits already published somewhere, would you give links to them? It is easier to evaluate an approach while looking at related code. Cheers, Orson 1. https://bugs.launchpad.net/kicad/+bug/

[Kicad-developers] Spate of bugs in global fields editor (aka BOM editor)

Given the spate of bug reports recently on the global fields editor (the spreadsheet icon in eeschema), I’m thinking perhaps I should back-port my 6.0 rewrite which moves it to wxGrid. The implementation itself seems pretty sound, but does drag one other change list along with it (for dialog co