UCI Programming

[Kizune]

Here you are: http://download.cowon.com/data/C08/C...5_20110303.pdf

I had to use google.co.kr to find it.

[jpgr]

the renamed mainmenu3 loads and plays ok when the j3 first starts up.
however, if you use the browser from it and select a track the firmware version of the music.swf loads and plays the song. pressing M in either case takes you back to the main menu selection screen.

[Kracko]

Having a bit of trouble figuring out how UCIs handle keyed input. Originally I was just attaching a onKeyDown function to my MovieClip but I was never receiving any triggers. After digging around the 2 official Cowon examples and swf sniffing the decompiled J3 code I found the RegisterKeyListener function inside the launcher.swf along with the virtual key codes. However, I still am not receiving any events. When I go to my music UCI I am testing an hit any of the physical buttons I get no response. Is there anything wrong with the below code?

class Application extends MovieClip {
    public function onLoad() : Void {
        _global.RegisterKeyListener(Application.HandleKey);
    }
    // omitted for brevity...
    private function HandleKey(code : Number) : Void {
        switch (code) {
            case _global.KEY_PLUS_SHORT:
                ext_fscommand2("KeyComPlus");
            break;
        }
    }
}

[el maco]

Originally Posted by Kracko

Having a bit of trouble figuring out how UCIs handle keyed input.

Mine looks like this:

function onLoad() {
    keyListener=new Object();
    keyListener.onKeyDown=onKeyDown;
    keyListener.onKeyUp=onKeyUp;
    Key.addListener(keyListener);
...

function onKeyDown() : Void {
    var code:Number=Key.getCode();
...

Dunno if this is considered good AS or not but at least it does the trick.

[Kracko]

Thanks el maco, that worked perfectly.

[Kracko]

Well, I'm very disappointed to say the least. I had the beginnings of a music uci with a small now playing queue function only to find out that when the screen goes off so does all functionality of the device. No way to wake the screen without user intervention, no firmware-to-flash hooks, nothing. Useless.

That's the only thing really keeping the J3 from being my favorite machine ever; an editable play queue which I miss so much from my now-dead Creative Zen.

[Kizune]

Sorry, I have a semi-offtopic question: Do you (or are you going to) use classes in your UCIs? If so, I recommend you to not go this route. I originally wanted to code Cheetah the OOP-way, but the result was way slower than expected. Thus, I re-coded Cheetah the old way: global objects which act as classes. It works very well and if you want, I can send you the framework I created.

[Kracko]

No, I was only using classes as namespaces (i.e. classes with only static functions) as mtasc does not allow the usage of the #import directive.

I agree that OOP should be avoided because you're essentially developing for an embedded device which requires different considerations when compared to a PC. Code as close to the metal as possible And thanks for the offer, but unfortunately I think this is it for me. I'm not really interested in building a UCI if all it amounts to is GUI shuffling.

Hopefully the J3 successor has a better setup, that isn't Android, or this may end up being my first and last Cowon product.

[el maco]

Originally Posted by Kracko

I had the beginnings of a music uci with a small now playing queue function only to find out that when the screen goes off so does all functionality of the device.

I guess Cowon really wanted to save battery life as much as possible so they decided that way... Anyway, I still think one could create an UCI with a basic editable (dynamic) playlist by using the favorites list as the queue. I haven't tried it but I don't see any reason why wouldn't it work.