4.6 Notifiers broken

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

4.6 Notifiers broken

timrowledge
Looks like some recent changes I saw float past relating to Warnings vs Errors vs whatever have broken the notifiers we get for problems. Instead of an actual useful window with a fragment of the stack and the ability to open a debugger by clicking on one of the contexts, we now get an almost useless window. It isn’t making my day any happier.

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Esc key to reboot Universe, or any other key to continue...



Reply | Threaded
Open this post in threaded view
|

Re: 4.6 Notifiers broken

timrowledge
Well there’s some extra confusion now; I had been trying to run the SocketTest tests from a doit in order to make a nice example of a bug we are having in Raspbian.

I was trying
SocketTest allTestSelectors do: [:sel|
        SocketTest run: sel]
which looked like it should work (whereas I really think something like SocketTest run ought to suffice) but that kept raising the new notifiers I am complaining about. Note that it opens *2* notifiers instead of stopping at the first one; that sound familiar from earlier discussions aboutWarning/Error/etc?

It turns out that running the SocketTest from the TestRunner does the same thing in an image at update 15079 but not 15039. So I suspect something got a bit borked in there.

tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Strange OpCodes: BNE: Buy Non-IBM Equipment




Reply | Threaded
Open this post in threaded view
|

Re: 4.6 Notifiers broken

Chris Muller-3
In reply to this post by timrowledge
Warnings were not working (see the thread, "Is this a bug with Step
Over?") and that was a showstopper for release, now its fixed, but the
current fix only gives us one chance to present application-formatted
messages to the user-audience of applications.

We'll be able to bring back the mini-stack for developers next release
but it will require a slight retooling of the debugger's API, so that
those cases where you want to see a mini-stack (developer) instead of
the formatted message (user), but we're out of time to do that for
this release.

On Mon, Jul 6, 2015 at 3:33 PM, tim Rowledge <[hidden email]> wrote:
> Looks like some recent changes I saw float past relating to Warnings vs Errors vs whatever have broken the notifiers we get for problems. Instead of an actual useful window with a fragment of the stack and the ability to open a debugger by clicking on one of the contexts, we now get an almost useless window. It isn’t making my day any happier.
>
> tim
> --
> tim Rowledge; [hidden email]; http://www.rowledge.org/tim
> Esc key to reboot Universe, or any other key to continue...
>
>
>

Reply | Threaded
Open this post in threaded view
|

Re: 4.6 Notifiers broken

timrowledge

On 06-07-2015, at 3:08 PM, Chris Muller <[hidden email]> wrote:

> Warnings were not working (see the thread, "Is this a bug with Step
> Over?") and that was a showstopper for release, now its fixed, but the
> current fix only gives us one chance to present application-formatted
> messages to the user-audience of applications.

Ah, rats. I didn’t notice the “can’t fix it now” part go by.


tim
--
tim Rowledge; [hidden email]; http://www.rowledge.org/tim
Strange OpCodes: SDP: Search and Destroy Pointer