Bug #830

jcom.namespace and Device Manager

Added by Renaud Rubiano about 8 years ago. Updated about 8 years ago.

Status:ClosedStart date:2011-07-15
Priority:NormalDue date:
Assignee:Théo de la Hogue% Done:

0%

Category:-Spent time:-
Target version:MVC for 0.6
Branch: OS:

Description

It appears that if you load a namespace through jcom.modular, you need to re-create the jcom.namespace object to be able to found distant applications.

*make a patcher with a jcom.namespace
*load a namespace with jcom.modular
*explore the just-loaded namespace with jcom.namespace, it doesn't appear.
*recreate the jcom.namespace (delete the object and re-create it)

History

#1 Updated by Théo de la Hogue about 8 years ago

  • Status changed from New to Resolved

The application observation mechanism is now ok. I've tested with local and distant namespace creation/destruction.

#2 Updated by Renaud Rubiano about 8 years ago

  • Status changed from Resolved to Closed

Bravissssiiiiimmmmoooooo !!

Also available in: Atom PDF