pcbnew Bug: Hitting b while in pcb, flash's error message too fast to see

[Lachlan Audas]

KiCad Build 6326,

When no fill's are defined on a pcb, typing the b kill (fill ) flash's a error message so fast that, you don't know what it
was, no option to cancel.. etc.

Only applier's to the Default canvas F9, OPENGL, and Ciro work ok, with no error message. Just the b key is ignored.

     Linux version 3.16.0-4-amd64 (<email address hidden>) (gcc version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt11-1+deb8u6 (2015-11-09)

Lachlan

[Nick Østergaard (nickoe)]

That is no an error message. That is just the status message showing the filling progress. I don't think this is a bug as such.

[Lachlan Audas (laudas1)]

No, not a bug the cents the program dose not work, it's a bug in the
cents that if the user has a message flash up, they not sure
about depending on the speed of the computer, this is bad user interface
design. And my book that's a user interface bug.
In stead of flashing up a message box, you can put on the message on the
status line, "No fill area's defined".. etc.
At least give the user some usable indication of whats going on.

Lachlan

On Sat, Nov 28, 2015 at 1:15 AM, Nick Østergaard <<email address hidden>
> wrote:

> That is no an error message. That is just the status message showing the
> filling progress. I don't think this is a bug as such.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1518442
>
> Title:
> pcbnew Bug: Hitting b while in pcb, flash's error message too fast
> to see
>
> Status in KiCad:
> New
>
> Bug description:
> KiCad Build 6326,
>
> When no fill's are defined on a pcb, typing the b kill (fill )
> flash's a error message so fast that, you don't know what it
> was, no option to cancel.. etc.
>
> Only applier's to the Default canvas F9, OPENGL, and Ciro work ok,
> with no error message. Just the b key is ignored.
>
> Linux version 3.16.0-4-amd64 (<email address hidden>) (gcc
> version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt11-1+deb8u6
> (2015-11-09)
>
>
> Lachlan
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/kicad/+bug/1518442/+subscriptions
>

[Nick Østergaard (nickoe)]

But this does not seem to happen in GAL.
Den 28/11/2015 08.45 skrev "Lachlan Audas" <email address hidden>:

> No, not a bug the cents the program dose not work, it's a bug in the
> cents that if the user has a message flash up, they not sure
> about depending on the speed of the computer, this is bad user interface
> design. And my book that's a user interface bug.
> In stead of flashing up a message box, you can put on the message on the
> status line, "No fill area's defined".. etc.
> At least give the user some usable indication of whats going on.
>
> Lachlan
>
>
>
> On Sat, Nov 28, 2015 at 1:15 AM, Nick Østergaard <
> <email address hidden>
> > wrote:
>
> > That is no an error message. That is just the status message showing the
> > filling progress. I don't think this is a bug as such.
> >
> > --
> > You received this bug notification because you are subscribed to the bug
> > report.
> > https://bugs.launchpad.net/bugs/1518442
> >
> > Title:
> > pcbnew Bug: Hitting b while in pcb, flash's error message too fast
> > to see
> >
> > Status in KiCad:
> > New
> >
> > Bug description:
> > KiCad Build 6326,
> >
> > When no fill's are defined on a pcb, typing the b kill (fill )
> > flash's a error message so fast that, you don't know what it
> > was, no option to cancel.. etc.
> >
> > Only applier's to the Default canvas F9, OPENGL, and Ciro work ok,
> > with no error message. Just the b key is ignored.
> >
> > Linux version 3.16.0-4-amd64 (<email address hidden>)
> (gcc
> > version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt11-1+deb8u6
> > (2015-11-09)
> >
> >
> > Lachlan
> >
> > To manage notifications about this bug go to:
> > https://bugs.launchpad.net/kicad/+bug/1518442/+subscriptions
> >
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1518442
>
> Title:
> pcbnew Bug: Hitting b while in pcb, flash's error message too fast
> to see
>
> Status in KiCad:
> New
>
> Bug description:
> KiCad Build 6326,
>
> When no fill's are defined on a pcb, typing the b kill (fill )
> flash's a error message so fast that, you don't know what it
> was, no option to cancel.. etc.
>
> Only applier's to the Default canvas F9, OPENGL, and Ciro work ok,
> with no error message. Just the b key is ignored.
>
> Linux version 3.16.0-4-amd64 (<email address hidden>) (gcc
> version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt11-1+deb8u6
> (2015-11-09)
>
>
> Lachlan
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/kicad/+bug/1518442/+subscriptions
>

[Lachlan Audas (laudas1)]

Yes.. GAL is fine, I expect it might be, that old canvas mouse events
active the commands on mouse down, where as GAL is
on mouse up, which I think is much better as you can cancel/escape, the
mouse events in GAL where as you can't in old canvas
So there may be a mouse race event if the old code is looking at mouse
down, and mouse up, Just a SWAG there thou.
 Any way it's not really to worrying about... I just like to see version
4 to be polished release.
I would work on my self, but I'm fixing the eagle import in pcbnew for
REFACE and VALUE which is not correct.

Lachlan

On Sat, Nov 28, 2015 at 3:16 PM, Nick Østergaard <<email address hidden>
> wrote:

> But this does not seem to happen in GAL.
> Den 28/11/2015 08.45 skrev "Lachlan Audas" <email address hidden>:
>
> > No, not a bug the cents the program dose not work, it's a bug in the
> > cents that if the user has a message flash up, they not sure
> > about depending on the speed of the computer, this is bad user interface
> > design. And my book that's a user interface bug.
> > In stead of flashing up a message box, you can put on the message on the
> > status line, "No fill area's defined".. etc.
> > At least give the user some usable indication of whats going on.
> >
> > Lachlan
> >
> >
> >
> > On Sat, Nov 28, 2015 at 1:15 AM, Nick Østergaard <
> > <email address hidden>
> > > wrote:
> >
> > > That is no an error message. That is just the status message showing
> the
> > > filling progress. I don't think this is a bug as such.
> > >
> > > --
> > > You received this bug notification because you are subscribed to the
> bug
> > > report.
> > > https://bugs.launchpad.net/bugs/1518442
> > >
> > > Title:
> > > pcbnew Bug: Hitting b while in pcb, flash's error message too fast
> > > to see
> > >
> > > Status in KiCad:
> > > New
> > >
> > > Bug description:
> > > KiCad Build 6326,
> > >
> > > When no fill's are defined on a pcb, typing the b kill (fill )
> > > flash's a error message so fast that, you don't know what it
> > > was, no option to cancel.. etc.
> > >
> > > Only applier's to the Default canvas F9, OPENGL, and Ciro work ok,
> > > with no error message. Just the b key is ignored.
> > >
> > > Linux version 3.16.0-4-amd64 (<email address hidden>)
> > (gcc
> > > version 4.8.4 (Debian 4.8.4-1) ) #1 SMP Debian 3.16.7-ckt11-1+deb8u6
> > > (2015-11-09)
> > >
> > >
> > > Lachlan
> > >
> > > To manage notifications about this bug go to:
> > > https://bugs.launchpad.net/kicad/+bug/1518442/+subscriptions
> > >
> >
> > --
> > You received this bug notification because you are subscribed to the bug
> > report.
> > https://bugs.launchpad.net/bugs/1518442
> >
> > Title:
> > pcbnew Bug: Hitting b while in pcb, flash's error message too fast
> > to see
> >
> > Status in KiCad:
> > New
> >
> > Bug description:
> > KiCad Build 6326,
> >
> > When no fill's are defined on a pcb, typing the b kill (fill )
> > flash's a error message so fast that, you don't know what it
> > was, no option to cancel.. etc.
> >
> > Only applier's to the Default canvas F9, OPENGL, and Ciro work ok,
> > with no error message. Just the b ke...

[Nick Østergaard (nickoe)]

Progress dialog works seems to work fine in recent nightlies in both GAL and legacy.