Bug #491

Chained derived channels does not work after setCurrentModel

Added by Espen Solbu about 5 years ago. Updated about 5 years ago.

Status:ClosedStart date:06/21/2012
Priority:HighDue date:
Assignee:Android Dashboard Developers% Done:

100%

Category:-Spent time:-
Target version:2.0 Multiple models

Description

I suspect that setCurrentModel will cause sourcechannel on derived channels that have another derived channel as source, to None (-1). Investigate if this is so

Update:
- This is so. Verified that after restart of the application, channels deriving from a derived channel does not update.

Test used:
RSSIRX->rssirx->rssirx derived
=> RSSIRX and rssirx updates. rssirx derived stays at -1

Associated revisions

Revision 469
Added by Espen Solbu about 5 years ago

closes #491, refs #488 Channels deriving from another derived channel should now "re-register" itself properly. This should also partially fix #488, but i suspect that issue is deeper, as i often "crash" hub derived channels, while all the other channels still run properly. Deploying as 2.0B8

History

#1 Updated by Espen Solbu about 5 years ago

  • Tracker changed from Task to Bug
  • Subject changed from Verify that chained derived channels still work after setCurrentModel to Chained derived channels does not work after setCurrentModel
  • Description updated (diff)
  • Priority changed from Normal to High

#2 Updated by Espen Solbu about 5 years ago

  • Status changed from New to Closed
  • % Done changed from 0 to 100

Applied in changeset r469.

Also available in: Atom PDF