Left thumbstick directional keypresses don't work with Shift (right trigger) pressed, whereas d-pad keypresses work.

Long labels crash MXM (e.g. DontDrawThisBox)

This one is not a big deal:
Pressing two keys 'at once, very quickly' registers only one keypress
Here's what I did:
Press down (d-pad)
Press A
Leave down
Leave A
Both keys registered if not done very quickly

Then I tried this:
Press down
Press A
Leave A
Leave down
Again, both keys registered

However, pressing both simultaneously for a short period causes only one to register. Weird.

This happens in actionscripts as well as the menu. Again, not a big deal, but occasionally causes missed keypresses in tetris, if playing very fast.

Well, the thumbstick issue is merely an omission in the keydef tables... but the label issue is a bit more puzzling. Theoretically, it shouldn't matter how long they are.

VIRTKEYBOARD command not implemented, but STRINGINPUT works.
And the flashing letters look pretty ugly, to be honest. Maybe a flashing or fading border would look better.

Yeah, VIRTKEYBOARD is in there, but I used "virtualkeyboard" instead. I'll shorten it up on the next build. It's not too important anyway, it just forces the keyboard as if you pressed the key combo to bring it up.

I will consider different ways to present the info on the highlighted key. Flashing was used because I needed to distinguish the CAPSLOCK and SHIFT keys when activated and highlighted.

New bug in latest wip: numerical comparisons are messed up. And I kept wondering why none of the lines in tetris were disappearing

CODE

IF# 5>7 GOTO BLAH1 GOTO unBlah :BLAH1 BeginDraw Messagebox "WTF?" EndDraw IqWaitMsg ANY :unBlah QUIT

EDIT: Well, can't do too much now, signing off.. first day back at university tomorrow

OK, I'll take a look at it....

BTW: I've been hashing out the details for handling the FileManager stuff. I'm finally moving forward with my complete UI (much easier with the new input system and VK in place).

Specifically, I'm gearing it to be able to use ActionScripting to control the dialogs. You'll be able to attach dialog definitions (in XML) to your plug-and-play ActionScript files (which as I said earlier, will be in XML format) and use them. Data access and controls configuration is all done in XML.

For example:

MyDialog.Controls.IDNICKNAME.Data.Text

would represent the text data from an edit box in a dialog... if you have any suggestions, get them to me now, as I'll be hammering on this tonight probably (and checking out the numeric comparison issue). I already have the framework in place for the controls, and will hopefully have some very simple dialogs running tonight.

BTW: is the line EXACTLY as you have it above:

CODE

IF# 5>7 GOTO BLAH1

because you need SPACES between tokens in ActionScript....

CODE

IF# 5 > 7 GOTO BLAH1

Double checked, and the comparisons work fine with the space.

The arrays were messing the program up, not the comparisons

SET blah[index] 1 doesn't work
SET blah%index% 1 works

QUOTE (geniusalz @ Jan 5 2004, 03:56 PM)

Double checked, and the comparisons work fine with the space. The arrays were messing the program up, not the comparisons SET blah[index] 1 doesn't work SET blah%index% 1 works

OK, I'll take a look.. of course, "technically" - it's an embedded variable. Hopefully a quick fix.


What do you think about the dialog stuff? Eventually, it will even be mousable (who needs WinCE?)

Hmm..
My suggestion on the new UI was skinlike elements allowed to be defined in actionscripts, with properties (pos, color, etc) allowed to be set through the script, or integrate actionscripts into skins. This sort of ties in with the 'permanent' objects drawing implementation.

Try looking at some Visual Basic .frm files in notepad. It's all text-based, and we should be looking for something similar, only in XML.

Sample vb form

Yes, my Dialog definitions will be in XML. Since Actionscripting can easily manipulate XML trees, it makes sense on many levels.

Annoyance: If the variable parameter for the StringInput command is not blank, the cursor appears at the beginning of the text, rather than appearing at the end of the text.

QUOTE (geniusalz @ Jan 5 2004, 10:02 PM)

Annoyance: If the variable parameter for the StringInput command is not blank, the cursor appears at the beginning of the text, rather than appearing at the end of the text.

Good catch... I'll try and hit that tomorrow.