Thanks for your time Aaron. I managed to get the situation stabilized ( I am not quite sure how though ). I guess it wasn't helping to have multiple Chrome windows open whilst debugging - I guess it was difficult to keep track of the events on my logging window.
Lesson learned: use a simpler setup whilst debugging NPAPI plugins ;-) On Nov 3, 11:12 am, Aaron Boodman <a...@chromium.org> wrote: > +mpcomplete, who should be along later today, and will know more about this. > > Are you getting NP_Destroy? > > - a > > On Tue, Nov 3, 2009 at 8:02 AM, Jean-Lou Dupont > > > > <jeanlou.dup...@gmail.com> wrote: > > > For one, the NP_Initialize of my plugin doesn't get called. > > > 1- Press "reload" button next to extension hosting the plugin > > 2- Press "reload" on the test page embedding the plugin > > > I need to force the plugin to crash in order to get things reloaded. > > > On Nov 3, 10:57 am, Aaron Boodman <a...@chromium.org> wrote: > >> On Tue, Nov 3, 2009 at 7:27 AM, Jean-Lou Dupont > > >> <jeanlou.dup...@gmail.com> wrote: > > >> > I am writing a plugin and it appears that using the "Reload" facility > >> > associated with an extension hosting a plugin (the button in > >> > chrome://extensions/ > >> > ) does not work (at least not what I had expected). > > >> > Is this the intended behavior? > > >> It should work. Can you describe the problem in more detail? > > >> - a --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to chromium-extensions@googlegroups.com To unsubscribe from this group, send email to chromium-extensions+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en -~----------~----~----~----~------~----~------~--~---
