That's excellent; very happy to hear it. You're most welcome. I see that HTML uses the name="" field for the same thing, but I had chosen to use something a little less (to me) confusing.

Ok, here's what I'm on about...

I want to be able to have a string that contains a username. Such that the string can be displayed with a GUIR routine and that I can edit with the GUIRTextLineIn.

Edit: Forgot to ask...you were discussing making more than one hub in the other post. How would you make a hub?

Blah

Regarding virtual hubs and metahubs. The "metahub" is the whole gCn hub process running on one of my servers that moderates all current gCn traffic. There's currently only one of these, but in the future, if it gets overloaded, there could be other ones added. Anyway, the metahub contains lots of virtual hubs, named things like "IRCHub" and "WebHub" etc, but, and I cannot stress this enough, connecting to a hub with any name creates a hub with that name. When all the users of a particular hub leave, it disappears. So there's no need to expressly reserve or create hubs.

Ok. I understand. What about my GUI issue? How would I do that?

Haha, I was supposed to fill in the answer to that in the "Blah" part before I posted the post, but clearly I completely forgot to do so. Anyway.

All you need to do is construct the text input element(s) in some scratch memory area, then push them onto the stack. By constructing them in scratch RAM, you can just copy the string you want the element to be initialized with into it, then push it, without having to worry about manipulating the stack live or something. And of course, once you regain control, you can use GUIFindFirst, GUIFindThis, and GUIFindNext to get the strings out again.

Ah, I think I understand. Now, let me ask you.

GUIFindFirst locates the first non-groupmaster element.
GUIFindThis and ...FindNext seem to both just find the next element.
But, if "FindFirst" starts at the first non-gm, then the others move down the stack, how do you just up to the next gm?

Basically, you want to either use GUIFindFirst + GUIFindNext to wander through the stack, or just use GUIFindThis to go exactly to where you want to be. The first two are if you need to look at a few different elements on the stack, and save clock cycles for advancing to other items. The latter is better if you have a single item on the stack in which you're interested.

Well, I would only be interested in one element, the one I'm pushing. How would I use GUIFindThis to find it?

Say you push a GUIRSmallWindow, then a GUIRWinButtons, then a GUIRText, then a GUIRTextInput. Since the groupmaster (the small window) isn't accessible or anything, you'd GUIFindThis to 0 for the WinButtons, to 1 for the Text, and to 2 for the TextInput.

Ok, that I get. Now one final question. When, in the SingleLineTextIn, you say "current offset to start of data string", what does that mean? Edit: And is "zero terminated string" what to display above the input box, or the initial string in the box? That confuses me a bit. Could we mod the DCS wiki to be a bit more specific about that?

That's relevant to the side-to-side scrolling. When you scroll far to the right, the first character visible is not the first character of the string, but a character later in the string. That number is the offset of that character.

Oh, so I can just make that .dw 0? And what about the text sting. I edited the above post with that.

It's the string inside the box. If you want a string above the box, you use a GUIRText item.

Ah. Would you mind editing the DCS wiki at ur convenience, to make that specification?

I'm a bit busy; do you have an account there so you can make the clarifications?

Code:


Currently, this code should push the items from RAM into the stack. After use, the items are popped. Am I on the right track with this? Or did you mean something else?

Edit: Now I can just ldir the data from the Username/password locations into these elements and then back into their locations from the stack, right?

Bump^^.

That's exactly correct! Let me help you out with an example that I use in Sandpaper:


Code:


Notice the copying from MyUsername into the GUI, and the later copying of MyUsername out of the GUI. The GUI itself is this:


Code:

Oh, I remember. I don't think it's a travesty if this doesn't get done, but it would be kool. I want to do this on both the username and password prompts. If the username and password are both null (9 bytes of 0's), then the cancel button is not shown. It is only shown if there is valid data there (this will force a username and password the first time). And I want to show the submit button only if the data has changed, but not if the data is the same or has been completely erased. Would this require


Code:

??

You could probably do that, yeah, but the only problem is that mousehooks don't trigger while the user is typing into a text field, only when the mouse is active. It's something I've regretted again and again.