Bug #830
jcom.namespace and Device Manager
| Status: | Closed | Start date: | 2011-07-15 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | % 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
Updated by Théo de la Hogue 10 months ago
- Status changed from New to Resolved
The application observation mechanism is now ok. I've tested with local and distant namespace creation/destruction.
Updated by Renaud Rubiano 10 months ago
- Status changed from Resolved to Closed
Bravissssiiiiimmmmoooooo !!