Le 20/08/2014 15:12, Brian Sidebotham a écrit :
Hi Yann,
There's nothing wrong with the source, see:
http://bazaar.launchpad.net/~kicad-product-committers/kicad/product/view/head:/pcbnew/dialogs/dialog_edit_module_for_BoardEditor.cpp
You have a locally unresolved conflict because you've had s
On 08/20/2014 08:14 AM, Brian Sidebotham wrote:
>> Hi guys,
>>
>> Sorry for asking dumb questions, but what is this whole QuasiModal stuff
>> for?
>>
>> Tom
>
> Hi Tom,
>
> No question is dumb.
>
> See Yann's description (from earlier in this thread) of the problem
> below, to which Quaimodal is
> Hi guys,
>
> Sorry for asking dumb questions, but what is this whole QuasiModal stuff
> for?
>
> Tom
Hi Tom,
No question is dumb.
See Yann's description (from earlier in this thread) of the problem
below, to which Quaimodal is a good solution.
Best Regards,
Brian.
---
Hi Dick, and all the
On 20 August 2014 13:44, yann jautard wrote:
> just FYI, 5084 does not compile any more.
>
> /home/yann/kicad_sources/kicad.bzr/pcbnew/dialogs/dialog_edit_module_for_BoardEditor.cpp:
> In member function ‘virtual void
> DIALOG_MODULE_BOARD_EDITOR::OnCancelClick(wxCommandEvent&)’:
> /home/yann/kica
On 20.08.2014 14:44, yann jautard wrote:
just FYI, 5084 does not compile any more.
void DIALOG_MODULE_BOARD_EDITOR::OnCancelClick( wxCommandEvent& event )
{
<<< TREE
EndQuasiModal( -1 );
===
ENDQUASIMODAL( -1 );
>>> MERGE-SOURCE
}
Hi guys,
Sorry for asking dumb questions
just FYI, 5084 does not compile any more.
/home/yann/kicad_sources/kicad.bzr/pcbnew/dialogs/dialog_edit_module_for_BoardEditor.cpp:
In member function ‘virtual void
DIALOG_MODULE_BOARD_EDITOR::OnCancelClick(wxCommandEvent&)’:
/home/yann/kicad_sources/kicad.bzr/pcbnew/dialogs/dialog_edit_module_
On 4 August 2014 17:05, Dick Hollenbeck wrote:
>
> I pushed an early branch of this work to milestoneB.
>
> See the commit log for some of the details.
>
> The shared_ptr turned out to be a can of worms. No, several cans of worms,
> all stacked
> like a 2 miles of dominos.
>
> So I used a single
2014-08-18 19:39 GMT+02:00 Dick Hollenbeck :
> On 08/18/2014 05:37 AM, Nick Østergaard wrote:
>> Hello Dick
>>
>> I see a bug in your commit 5072 (also present in latest commit 5079).
>> In that commit; when opening a schematic, then all connections are
>> showed as not connected (with the square g
On 08/18/2014 05:37 AM, Nick Østergaard wrote:
> Hello Dick
>
> I see a bug in your commit 5072 (also present in latest commit 5079).
> In that commit; when opening a schematic, then all connections are
> showed as not connected (with the square green box around the end
> nodes). When drawing a ne
>>
> Good news !
>
> thanks Dick !
>
> but where is that 5089 version ? I just ran the install script and it
> updated to 5081. May be it was 5079 ?
Yes.
___
Mailing list: https://launchpad.net/~kicad-developers
Post to : kicad-developers@lists.
Le 18/08/2014 01:04, Dick Hollenbeck a écrit :
Patch solved the issue, seemed to work like a charm... But induced another
issue. Step to
reproduce :
1 - open kicad, then open eeschema and pcbnew
2 - in pcbnew, open the module properties dialog on any part you want.
3 - go back to eeschema, wic
Hello Dick
I see a bug in your commit 5072 (also present in latest commit 5079).
In that commit; when opening a schematic, then all connections are
showed as not connected (with the square green box around the end
nodes). When drawing a new wire they all look connected again. See the
attached imag
Dick,
Did you mean BZR5079? I cannot find 5089.
Jean-Paul
AC9GH
On Aug 17, 2014, at 7:04 PM, Dick Hollenbeck wrote:
>>>
>>> Patch solved the issue, seemed to work like a charm... But induced another
>>> issue. Step to
>>
>> Achieving platform independent and wx version independent results
>> Patch solved the issue, seemed to work like a charm... But induced another
>> issue. Step to
>> reproduce :
>>
>> 1 - open kicad, then open eeschema and pcbnew
>> 2 - in pcbnew, open the module properties dialog on any part you want.
>> 3 - go back to eeschema, wich is now responding normally,
Dick Hollenbeck:
I don't see this bug when I use: A) new code from last night + B) wx3.x. I
see bug with
wx2.8.
I'm built kicad with wx3 (from ubuntu's repository) and this bug is gone.
Dick Hollenbeck:
I don't know for sure whether using wx3.x alone will fix this, but you could
try. If
Understood. I actually just found an unofficial wx 3.0 package for
Debian stable, so I may end up switching over to that as well just for
crazy_imp's antialiasing fix.
On Fri, 2014-08-15 at 15:42 -0500, Dick Hollenbeck wrote:
> On 08/15/2014 02:05 PM, Andrew Zonenberg wrote:
> > As a user of wx 2.
On 08/15/2014 02:05 PM, Andrew Zonenberg wrote:
> As a user of wx 2.8 on Debian I would like to ensure that, as a minimum,
> kicad continues to build on it until the next stable Debian version
> (presumably shipping wx 3.0) is released.
You have that capability. Probably I will uninstall wx2.8 to
On 08/15/2014 02:16 PM, Wayne Stambaugh wrote:
> On 8/15/2014 3:00 PM, Dick Hollenbeck wrote:
>> On 08/15/2014 10:00 AM, Wayne Stambaugh wrote:
>>> On 8/15/2014 8:47 AM, Dick Hollenbeck wrote:
On 08/14/2014 07:31 PM, yann jautard wrote:
>
> Le 14/08/2014 16:21, Dick Hollenbeck a écrit
On 08/15/2014 10:26 AM, Барановский Константин wrote:
> I'm catched the bug where the window of the eeschema freezes.
>
> To reproduce do the next:
> 1) start kicad and opens some project (with existing schematic);
> 2) from kicad's panel start eeschema;
> 3) for some component in context menu (ri
On 8/15/2014 3:00 PM, Dick Hollenbeck wrote:
> On 08/15/2014 10:00 AM, Wayne Stambaugh wrote:
>> On 8/15/2014 8:47 AM, Dick Hollenbeck wrote:
>>> On 08/14/2014 07:31 PM, yann jautard wrote:
Le 14/08/2014 16:21, Dick Hollenbeck a écrit :
>> I don't know if it is technically possible to
As a user of wx 2.8 on Debian I would like to ensure that, as a minimum,
kicad continues to build on it until the next stable Debian version
(presumably shipping wx 3.0) is released.
If new features can't be easily made to work on wx2.8 that's
understandable as long as there's some graceful downgr
On 08/15/2014 10:00 AM, Wayne Stambaugh wrote:
> On 8/15/2014 8:47 AM, Dick Hollenbeck wrote:
>> On 08/14/2014 07:31 PM, yann jautard wrote:
>>>
>>> Le 14/08/2014 16:21, Dick Hollenbeck a écrit :
> I don't know if it is technically possible to change this behaviour, but
> I think it could
I'm catched the bug where the window of the eeschema freezes.
To reproduce do the next:
1) start kicad and opens some project (with existing schematic);
2) from kicad's panel start eeschema;
3) for some component in context menu (right click) select "Edit
component -> Edit";
After this step ope
On 8/15/2014 8:47 AM, Dick Hollenbeck wrote:
> On 08/14/2014 07:31 PM, yann jautard wrote:
>>
>> Le 14/08/2014 16:21, Dick Hollenbeck a écrit :
I don't know if it is technically possible to change this behaviour, but
I think it could be a great improvement.
>>> :
yann
>>>
On 08/14/2014 07:31 PM, yann jautard wrote:
>
> Le 14/08/2014 16:21, Dick Hollenbeck a écrit :
>>> I don't know if it is technically possible to change this behaviour, but
>>> I think it could be a great improvement.
>>>
>> :
>>> yann
>>>
>> Hopefully QuasiModal is not a monster.
>>
>> For signif
Le 15/08/2014 02:31, yann jautard a écrit :
I updated my source tree to latest bzr to test with that revision, but
I did a mistake and I need to recompile the whole stuff. As I have
only my netbook now, it will take one hour or more, so I will test
that tomorow
Exact same thing with
Le 14/08/2014 16:21, Dick Hollenbeck a écrit :
I don't know if it is technically possible to change this behaviour, but
I think it could be a great improvement.
:
yann
Hopefully QuasiModal is not a monster.
For significant dialogs (ones which tend to be open for a while) using the
QuasiMo
On 08/13/2014 06:40 PM, Wayne Stambaugh wrote:
> On 8/13/2014 6:23 PM, Dick Hollenbeck wrote:
>> On 08/13/2014 03:43 PM, Wayne Stambaugh wrote:
>>> On 8/13/2014 4:37 PM, Dick Hollenbeck wrote:
Many changes were introduced in revision 5072.
If you are happy with your current bina
> I don't know if it is technically possible to change this behaviour, but
> I think it could be a great improvement.
>
:
> yann
>
Hopefully QuasiModal is not a monster.
For significant dialogs (ones which tend to be open for a while) using the
QuasiModal
support in DIALOG_SHIM might be a sol
Hi Dick, and all the others involved in the modular design.
I noticed something regarding the modular kicad apps :
When you have some modal window opened in one of the app, eg the module
properties window in pcbnew, all the kicad modules are frozen until you
close that window.
It's not a big
On 8/13/2014 6:23 PM, Dick Hollenbeck wrote:
> On 08/13/2014 03:43 PM, Wayne Stambaugh wrote:
>> On 8/13/2014 4:37 PM, Dick Hollenbeck wrote:
>>>
>>> Many changes were introduced in revision 5072.
>>>
>>> If you are happy with your current binaries, stay where you are until the
>>> pond settles.
>
- Original Message -
> From: Dick Hollenbeck
> To: kicad-developers@lists.launchpad.net
> Cc:
> Sent: Thursday, August 14, 2014 6:37 AM
> Subject: Re: [Kicad-developers] eeschema modular kicad work
>
>
> Many changes were introduced in revision 5072.
>
&
On 08/13/2014 03:43 PM, Wayne Stambaugh wrote:
> On 8/13/2014 4:37 PM, Dick Hollenbeck wrote:
>>
>> Many changes were introduced in revision 5072.
>>
>> If you are happy with your current binaries, stay where you are until the
>> pond settles.
>>
>> If you want to see if your known bugs are fixed,
On 8/13/2014 4:37 PM, Dick Hollenbeck wrote:
>
> Many changes were introduced in revision 5072.
>
> If you are happy with your current binaries, stay where you are until the
> pond settles.
>
> If you want to see if your known bugs are fixed, then take a look at it and
> that testing
> will be
Many changes were introduced in revision 5072.
If you are happy with your current binaries, stay where you are until the pond
settles.
If you want to see if your known bugs are fixed, then take a look at it and
that testing
will be appreciated.
Thanks,
Dick
__
On 07/29/2014 02:02 PM, Wayne Stambaugh wrote:
> On 7/27/2014 1:33 PM, Dick Hollenbeck wrote:
>> Gentlemen:
>>
>> In the course of trying to load the schematic editor directly under
>> kicad.exe, by-passing
>> eeschema top frame itself, I was exposed to a range of issues in the design
>> of eesch
36 matches
Mail list logo
