The documentation for the OSC Address space is here:

http://charlie-roberts.com/Control/?page_id=297

Let me know if there are questions. - Charlie

Note that each widget has an object named props that stores the original values as generated by JSON (or by dynamic creation). The tricky part is that this object is not updated when properties are changed dynamically via scripting. So if you were moving widgets around on the screen, for example, you would have to make sure you were updating the props object appropriately. If you do this then you can just store the props object and you should be able to recreate widgets reliably from that.

As an example, if you sent:

/control/setBounds yourWidget 0 0 .5 .5

you should probably follow it up with:

/control/runScript "yourWidget.props.bounds = [0,0,.5,.5];"

You could also specify a custom OSC delegate that would do this automatically in Control so that you only had to send one OSC message.

Once you have the JSON of a widget, just call control.addWidget(yourJSON) to add it to an interface.

I would say a good first step would be to see if you can save / recall the props object of a button that hasn't been dynamically modified using HTML local storage. There's an easy to follow guide to local storage in the ebook found here:

http://mislav.uniqpath.com/2011/10/dive-into-html5/

Regards,

Scott

Regards,

Scott

When you first load an interface file, all the arrays for all the pages are produced and populated. But if you want to add a page afterwords you would need to do something like this:

control.pages[control.pages.length] = [];

The above line just adds a page to the end. It's the same as control.pages.push([]);

You could also make a specific page:

control.pages[yourPageNumber] = [];

All this could be done via OSC using the /control/runScript/ address. Hope this helps - Charlie

The nice thing about being able to include it in the interface file is that you can actually overwrite functionality on a per interface basis... - Charlie

Scott

Control.prototype.addWidget = function(widget, page) {
	this.pages[page].push(widget);
	if(page == control.currentPage) {
		if(widget.show != null)
			widget.show();

		if(widget.draw != null)
			widget.draw();

	}else{
		if(widget.hide != null)
			widget.hide();
	}
	eval(widget.oninit);
}

and

OSCManager.prototype.processOSCMessage = function() {
	var address = arguments[0];
	var typetags = arguments[1];
	var args = [];
	console.log(address + "::"+typetags+"::"+arguments[2]);
    switch(address){
        case "/control/runScript":
            eval(arguments[2]);
            return;
        break;
        case "/control/addWidget":
            eval("var w = " + arguments[2]);
            var _w = control.makeWidget(w);
            control.widgets.push(_w);
            eval("control.addWidget(" + w.name + ", " + arguments[3] + ");");
        return;
        break;
        case "/control/removeWidget":
            control.removeWidgetWithName(arguments[2]);
            return;
        break;
        case "/control/setBounds":
            var w = control.getWidgetWithName(arguments[2]);
            w.setBounds([arguments[3], arguments[4], arguments[5], arguments[6]]);
            return;
            break;
        case "/control/setColors":
            var w = control.getWidgetWithName(arguments[2]);
            w.setColors([arguments[3], arguments[4], arguments[5]]);
            return;
            break;
        case "/control/setRange":
            var w = control.getWidgetWithName(arguments[2]);
            w.setRange(arguments[3], arguments[4]);
            return;
            break;
        case "/control/setAddress":
            var w = control.getWidgetWithName(arguments[2]);
            w.address = arguments[3];
            return;
            break;
        case "/control/createBlankInterface":
            control.unloadWidgets();
            var _json = "loadedInterfaceName = '" + arguments[2] + "'; interfaceOrientation = '" + arguments[3] + "'; pages = [["
            if(typeof arguments[4] == "undefined" || arguments[4] == "true") {
                _json += '{\
                    "name": "menuButton",\
                    "type": "Button",\
                    "bounds": [.8,.8,.2,.1],\
                    "mode":"toggle",\
                    "colors": ["#000", "#444", "#aaa"],\
                    "ontouchstart": "if(this.value == this.max) { control.showToolbar();} else { control.hideToolbar(); }",\
                    "label": "menu",\
                },';
            }
            _json += "]];";

            interfaceManager.runInterface(_json);
            $.mobile.changePage('#SelectedInterfacePage');
            return;
            break;
    }

	for(var i = 2; i < arguments.length; i++) {
		args[i - 2] = arguments[i];
	}

	this.delegate.processOSC(address, typetags, args);
}

Regards,

Scott

Trying the addwidget code and having a bit of trouble. Problem seems to be with the eval("var w = " + arguments[2]) statement. Control renders nothing when I replace arguments[2] with my JSON variable. Chrome debugger gives me syntax error.

Regards,

Scott

Trying the addwidget code and having a bit of trouble. Problem seems to be with the eval("var w = " + arguments[2]) statement. Control renders nothing when I replace arguments[2] with my JSON variable. Chrome debugger gives me syntax error.

Regards,

Scott

Regards,

Scott

I'm really looking forward to trying the CCK functionality. Thanks Charlie (and Macciza).

Regards,

Scott

Cheers
MM

To be honest I'm not excited about spending time on receiving sysex but if you or someone has questions about implementing it I'm happy to help. Really just trying to get this update out the door now... - Charlie

Oh and another thought was whether we can get control to receive and save sysex messages sent to it, dumped from a device?
This would help automate the process of generating correct sysex packets . . . Just a thought . . .

Cheers
MM

I did not think it would take too much to get happening - hope some of my comments helped . . .
Unfortunately I understand the theory and logic behind coding it, but fall short on the practical/implementation side of it all - quite frustrating. Again it would have taken me far, far longer but hopefully look at your code will light my way a bit . . .

Any possibility of sending me a new compiled version? Not sure when I will be able to get the Dev membership to do it myself . . .

Glad that you have got it sorted - will see if there are any other ideas that I can contribute . . .

Cheers
MM

I wish I had known it was only going to take a couple of hours a few months back when I put it on the backburner... oh well. Glad it's in there now! - Charlie

Unfortunately it doesn't work in the Simulator, but it works on my iPad fine. One problem with implementing this is it's a pain to debug... you have to load the software on the iPad, disconnect the iPad from your computer, plugin the CCK / MIDI interface, test, unplug the CCK, plugin the iPad back in to your computer, load a new iteration etc.

But I'd like to see it happen at some point for sure. Just haven't been able to devote time to it... it will take more time than adding MIDI Sysex unfortunately... - Charlie

Unfortunately I don't have Dev Account - yet . . . So can only run in the simulator . . .

Would we be able to look at USB midi via the CCK as well before an AppStore update?
I had a bit of a look and the issue seems to be that only MIDINetwork stuff is implemented, but I think it needs stuff from MIDIServices to access USB midi devices. The selectHardwareMIDI method appears unimplemented . . .

It would be good if this was under a seperate title on the destinations page and also able to deal with multiple devices incase a hub is used. It should also be able to send to both IP and USB ports at the same time I guess.

Not sure where you may be up to in all this - will check the devbranch later

Thanks
MM

midiManager.send('sysex', [0xF0, 0x41, 0x10, 0x42, 0x12, 0x40, 0x00, 0x7F, 0x00, 0x41, 0xF7], 11);

... where 11 is the number of bytes in the sysex array.

I'm really trying hard to finish up an update for Control and hope to post this change (as well as a bunch of other changes) to the app store soon. - Charlie