Unexpected behaviour when subscribing to properties about bacon.js HOT 5 CLOSED

Please refer to #47

What's happening here is that your Property won't get updated when there are no listeners. Before you add an actual listener using onValue, the Property is not active; it's not listening to the underlying Bus. It ignores input until someone's interested. So it all boils down to the "laziness" of all Bacon streams and properties. This is a key feature too: the streams automatically "plug in" to their sources when a listner is added, and "unplug" when there are no more listeners.

Is there something specific you're trying to achieve here, or are you just experimenting? Maybe I could help you with your actual application?

from bacon.js.

This is definitely a FAQ.I feel we need to ad a FAQ section in the Wiki :)

from bacon.js.

If you based your Property on, for instance, jQuery events, would you expect it to be updated while there are no listeners? If so, what would be the cost? With a Bus, there obviously wouldn't be a substantial cost to updating the Property, but from the the Property's point of view, the Bus is just an EventStream that the Property listens to when it has listeners.

So, this is in fact the desired behaviour, even though it at first doesn't make sense. It would be possible to make an exception for the Bus class only, but that would be introducing an inconsistency into the way Properties work.

I hope this clarifies things.

from bacon.js.

Okay, I guess that makes sense, or at least, isn't a bug :)

I am just experimenting at the moment really, so we'll see how I go with a manual .onValue() call for now.

from bacon.js.

Ok :)

And really, I'll be glad to help you with the design of your actual application (to some extent...). I suggest you use the Bacon.js Google Group for support.

https://groups.google.com/forum/?fromgroups#!forum/baconjs

from bacon.js.