← Back to team overview

kicad-developers team mailing list archive

Re: Assertion trip due to out-of-order dialog close

 

On Wed, 19 Aug 2015 21:12:10 +0200,
Wayne Stambaugh wrote:
> The problem is replace it with what?  Kiway tries to straddle the
> difference between the all windows in one process behavior versus the
> each application in it's own process behavior.  It does it about as well
> as could be expected unless you switch to entirely modeless dialogs
> which opens an entirely new set of issues.  I'm wondering if we should
> just use a multiple document interface (MDI) based on wxAui.  This way

Still in favour of discrete processes with IPC (of some kind, there are
around cross-platform toolkits for that). In-core data access is cute
but gives other problems. Also it's quite evident that wx is not
designed for that.

BTW Open/LibreOffice simply 'ignores' the problem, if there's a modal
open, nothing else works. And you *can't* open another process. Bad OO!
(and it keeps searching for CUPS even when you don't have it and you
told it that you don't have and have to wait it for time out every time
you open a print dialog...)

Be careful with MDI, it would probably break 99% of the multi monitor
setups.

Anyway, I already expressed my point on kiway so until I couldn't work confortably (i.e. without fearing a massive crash:P) I'll keep launching eeschema and pcbnew separately. Who cares if I lose cross probing :D 

> I actually was considering this myself.  I don't like launching a dialog
> from a dialog.  I would rather remove the "Change Footprint(s)" and
> "Footprint Editor" launch buttons from the footprint properties dialog.
>  The footprint editor can already be opened directly from the footprint
> context menu or the Ctrl+E hot key.  There is no reason we couldn't add
> a context menu entry and a hot key to directly open the change footprint
> dialog.  It seem like being able to directly open the change footprints
> dialog would be an improvement over having to open the footprint
> properties dialog first.

eeschema works that way. Properties and open in module editor are
separate entries in the object menu. Also I concur that there is no need
to pass thru the property dialog for that.

-- 
Lorenzo Marcantonio
Logos Srl


References