fixed custom-buttons in group chat and made sure cmds are sent to assistant by default

Author: fquirin

www/scripts/sepiaFW.ui.customButtons.js

@@ -165,7 +165,7 @@ function sepiaFW_build_ui_custom_buttons(){
         SepiaFW.ui.actions.openCMD(newAction);
         */
         SepiaFW.debug.info("CustomButtons - sending button-text: " + buttonData.text);
-        SepiaFW.client.sendInputText(buttonData.text);
+        SepiaFW.client.sendInputText("@" + SepiaFW.assistant.id + " " + buttonData.text);
     }
 
     return CustomButtons;

www/scripts/sepiaFW.webSocket.js

@@ -1741,7 +1741,10 @@ function sepiaFW_build_webSocket_client(){
 		var cmd = dataset.cmd;
 		//the sender becomes the receiver - This workds because dataset is usually an 
 		//action received from the assistant ... but it is kind of inconsistent with the rest :-(
-		var receiver = dataset.newReceiver || dataset.sender || ''; 	//we use newReceiver to fix the inconsistency (a bit)
+		var receiver = dataset.newReceiver || dataset.sender || SepiaFW.assistant.id; 	//we use newReceiver to fix the inconsistency (a bit)
+		if (receiver == "<all>"){
+			receiver = "";
+		}
 		//TODO: handle options in dataset?
 		if (dataset.options){
 			$.each(options, function(key, value){