What's the scoop on watchdog.

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

What's the scoop on watchdog.

derek riemer

Can someone explain when I need to notify the watch dog?


--

Derek Riemer

  • Department of computer science, third year undergraduate student.
  • Proud user of the NVDA screen reader.
  • Open source enthusiast.
  • Member of Bridge Cu
  • Avid skiier.

Websites:
Honors portfolio
Awesome little hand built weather app!

[hidden email]
Phone: (303) 906-2194


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: What's the scoop on watchdog.

Brian's Mail list account BY
I'd be rather interested in a lay persons explanation to this one as it
looks to me that certain parts of nvda  are monitored and one supposes if
you call these routines from your app module add on etc, then watchdog is
active.
 It seems to pop up all over the place in any session  in anything that uses
the kernal in some way. That one supposes is why nvda is a lot harder to
crash nowadays, as you basically need to crash windows or at least the
process running nvda to do that.
 Brian

[hidden email]
Sent via blueyonder.
Please address personal email to:-
[hidden email], putting 'Brian Gaff'
in the display name field.
----- Original Message -----
From: "derek riemer" <[hidden email]>
To: "NVDA screen reader development" <[hidden email]>
Sent: Friday, December 16, 2016 8:26 AM
Subject: [Nvda-devel] What's the scoop on watchdog.


> Can someone explain when I need to notify the watch dog?
>
>
> --
> ------------------------------------------------------------------------
>
>
>    Derek Riemer
>
>  * Department of computer science, third year undergraduate student.
>  * Proud user of the NVDA screen reader.
>  * Open source enthusiast.
>  * Member of Bridge Cu
>  * Avid skiier.
>
> Websites:
> Honors portfolio <http://derekriemer.com>
> Awesome little hand built weather app!
> <http://django.derekriemer.com/weather/>
>
> email me at [hidden email] <mailto:[hidden email]>
> Phone: (303) 906-2194
>
>


--------------------------------------------------------------------------------


> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot


--------------------------------------------------------------------------------


> _______________________________________________
> Nvda-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/nvda-devel
>


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: What's the scoop on watchdog.

James Teh
In reply to this post by derek riemer
Normally, the core does this for you as long as it knows about whatever you're using to trigger a call. So, scripts, events, queueHandler.queueFunction, core.callLater, etc. all do the right thing. As a counter-example, wx.CallAfter doesn't notify the watchdog because it's not an NVDA function. Of course, anything you do in scripts, events, etc. shouldn't block for very long, since that would block the UI (which is exactly what watchdog tries to catch and kill).

Jamie


On Fri, Dec 16, 2016 at 6:26 PM, derek riemer <[hidden email]> wrote:

Can someone explain when I need to notify the watch dog?


--

Derek Riemer

  • Department of computer science, third year undergraduate student.
  • Proud user of the NVDA screen reader.
  • Open source enthusiast.
  • Member of Bridge Cu
  • Avid skiier.

Websites:
Honors portfolio
Awesome little hand built weather app!

[hidden email]
Phone: <a href="tel:(303)%20906-2194" value="+13039062194" target="_blank">(303) 906-2194


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: What's the scoop on watchdog.

derek riemer

So, If I'm calling into ctypes, when should I be calling the watchdog? Let's say I'm querying scintilla for bookmarks, or calling into the dictationbridge code.


On 12/18/2016 3:58 PM, James Teh wrote:
Normally, the core does this for you as long as it knows about whatever you're using to trigger a call. So, scripts, events, queueHandler.queueFunction, core.callLater, etc. all do the right thing. As a counter-example, wx.CallAfter doesn't notify the watchdog because it's not an NVDA function. Of course, anything you do in scripts, events, etc. shouldn't block for very long, since that would block the UI (which is exactly what watchdog tries to catch and kill).

Jamie


On Fri, Dec 16, 2016 at 6:26 PM, derek riemer <[hidden email]> wrote:

Can someone explain when I need to notify the watch dog?


--

Derek Riemer

  • Department of computer science, third year undergraduate student.
  • Proud user of the NVDA screen reader.
  • Open source enthusiast.
  • Member of Bridge Cu
  • Avid skiier.

Websites:
Honors portfolio
Awesome little hand built weather app!

[hidden email]
Phone: <a moz-do-not-send="true" href="tel:%28303%29%20906-2194" value="+13039062194" target="_blank">(303) 906-2194


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel




------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot


_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel

--

Derek Riemer

  • Department of computer science, third year undergraduate student.
  • Proud user of the NVDA screen reader.
  • Open source enthusiast.
  • Member of Bridge Cu
  • Avid skiier.

Websites:
Honors portfolio
Awesome little hand built weather app!

[hidden email]
Phone: (303) 906-2194


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: What's the scoop on watchdog.

James Teh
You shouldn't. In that case, you should be calling from some core script or event, in which case watchdog already knows the core is doing stuff.

On Mon, Dec 19, 2016 at 10:25 AM, derek riemer <[hidden email]> wrote:

So, If I'm calling into ctypes, when should I be calling the watchdog? Let's say I'm querying scintilla for bookmarks, or calling into the dictationbridge code.


On 12/18/2016 3:58 PM, James Teh wrote:
Normally, the core does this for you as long as it knows about whatever you're using to trigger a call. So, scripts, events, queueHandler.queueFunction, core.callLater, etc. all do the right thing. As a counter-example, wx.CallAfter doesn't notify the watchdog because it's not an NVDA function. Of course, anything you do in scripts, events, etc. shouldn't block for very long, since that would block the UI (which is exactly what watchdog tries to catch and kill).

Jamie


On Fri, Dec 16, 2016 at 6:26 PM, derek riemer <[hidden email]> wrote:

Can someone explain when I need to notify the watch dog?


--

Derek Riemer

  • Department of computer science, third year undergraduate student.
  • Proud user of the NVDA screen reader.
  • Open source enthusiast.
  • Member of Bridge Cu
  • Avid skiier.

Websites:
Honors portfolio
Awesome little hand built weather app!

[hidden email]
Phone: <a href="tel:%28303%29%20906-2194" value="+13039062194" target="_blank">(303) 906-2194


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel




------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot


_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel

--

Derek Riemer

  • Department of computer science, third year undergraduate student.
  • Proud user of the NVDA screen reader.
  • Open source enthusiast.
  • Member of Bridge Cu
  • Avid skiier.

Websites:
Honors portfolio
Awesome little hand built weather app!

[hidden email]
Phone: <a href="tel:(303)%20906-2194" value="+13039062194" target="_blank">(303) 906-2194


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Nvda-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/nvda-devel
Loading...