You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
i noticed in the patchbay /network page, when migrating to use mutant observables we stopped using our peerListSort function. so when browsing the page, the peers i want to see (the ones i'm connected to) are randomly scattered about.
i attempted to write a function to sort a collection observable like so:
but the problem is that this "flattens" the collection of nested observables into a collection of values, which would lead to changes in our render functions with h.
any advice on how to do this properly? and should this be something included in mutant?
chur!
The text was updated successfully, but these errors were encountered:
mmckegg
added a commit
to ssbc/patchbay
that referenced
this issue
Feb 6, 2017
Hey @ahdinosaur! Yes, I think you are right that it should be a mutant transform. I think it should work like map but instead of changing the output, changes the order.
Here's how i would implement sorting in patchbay (without a special mutant transform):
hey @mmckegg @mixmix,
i noticed in the patchbay /network page, when migrating to use
mutant
observables we stopped using ourpeerListSort
function. so when browsing the page, the peers i want to see (the ones i'm connected to) are randomly scattered about.i attempted to write a function to sort a collection observable like so:
but the problem is that this "flattens" the collection of nested observables into a collection of values, which would lead to changes in our render functions with
h
.any advice on how to do this properly? and should this be something included in
mutant
?chur!
The text was updated successfully, but these errors were encountered: