[bus] objects are named in patch scope, not containing scope

[bgribble]

Creating a receive-via for a new name causes a [bus] or [bus~] object to be created as well. This is to allow multiple-send, multiple-receive message distribution.

I have observed that creating a receive via within a layer having a non-default scope creates the via itself in the correct (non-default) scope, but the [bus] (and the name associated with the via) are created in the default scope.

This can be seen from the console by calling app.resolve('name', <widget>) where is a widget in the non-default scope (like the via).

[bgribble]

This is an artifact of the load process. If the via is created interactively, the [bus] is in the correct scope. But if the patch is saved and loaded, the via object is initially created in the default scope and then bound to the new scope. The [bus] is not moved because it's not named explicitly in the save file.

[bgribble]

With the above commit, this issue is fixed but there's still an issue with changing the scope of a receive-via. If a bus was created , its scope won't change if you just send the @rescope method to the via object. You'd have to do it in the console for now. Created #201 for that work, closing this one.