Zugg Software :: View topic

Apprentice Joined: 14 Sep 2005 Posts: 121

I've recently found out the beaty of making little GUIs using string lists to get certain lines just right and not have to sort through all of the crap to get to the line that's messed up (becuase most of my GUIs have been formed in the realms of substitute). But here's the code i usually use to construct my GUIs.

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

You had to create that from your prompt, which means you were handling the information part-by-part. You can build the stringlist there in your prompt trigger using the %additem() function (it allows duplicates).

Prompt = %additem(%1,@Prompt)

Apprentice Joined: 14 Sep 2005 Posts: 121

the variables aren't what i'm worried about, what i'm worried about is putting say this line into the stringlist, cuz when i use the code that turns my string list into the layed out gui it would mess with the |'s that i use and turn those into %cr's and that'd severely jack the layout up.

line:

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

You aren't having problems getting it into the stringlist, right? Try using %expandlist(). Not sure if that will work with carriage returns or not, but if not you can just loop the stringlist using #FORALL and #SAY/#ECHO/#SHOW %i.

Apprentice Joined: 14 Sep 2005 Posts: 121

%expandlist doesn't work, it just sows all the lines on one line, and the forall doesn't work cuz it tries to execute each line and i end up with all kinds of weird stuff.

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

#forall doesn't execute anything. All it does is loop through the condition string, helpfully isolating each element in the stringlist so that the user can do awful things to it (like sending it off to the MUD). Post the code you got, and we'll hammer it out.

SubAdmin Joined: 18 Nov 2001 Posts: 5182

Make the triggers that use #SUBSTITUTE more specific. You are already rebuilding your prompt and then #SUBbing it one set of triggers. Why do you have another set even detecting the recently #SUBbed text?! I am at a loss to even understand how you have this sort of conflict.

On a second note it sounds like you are trying apply a newer priciple to an older script. If the script is working, and you are not improving it; then it makes no sense to change it. Of course you always build your original #SUBbing prompt stuff with '│' instead of '|'. In most fonts the former will display as a solid line, but it is different from the zMud list seperator character.

Apprentice Joined: 14 Sep 2005 Posts: 121

You've misread what I'm trying to do. I've got other triggers that sub text the one way, and uses a stringlist so that I can more easily work on just one line of the output gui to get it exactly as i need. The problem is that I want to do the same with my prompt trigger because it looks like this currently:

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

I should have suggested this earlier, but I really think you should use a datarecord variable. It allows for easy access to specific keys, so if you order the keys by line you should be able to call up just the line you are having trouble with. To make it a tad more fancy, you could simply store the plain data in the datarecord (each key would contain a stringlist of the items that appear on that line) and then draw it out using the stringlist functions. This will allow you to make the data available for other scripts which probably won't need the GUI stuff, while still making it easy to create the GUI.

Your GUI alias would be something like this:

#alias display {#show %format("the format string", %ansi(some color)%item(@Prompt.line1,1), %item(@Prompt.line1,2)%ansi(default), etc)}

Apprentice Joined: 14 Sep 2005 Posts: 121

You've got me intrigued, please explain further, remember that I'm quite the script n00b just poking around til I make stuff work. A little more info about me, I used to be a marine (y'know Muscles Are Required Intelligence Not Essential), and as we used to say in the Marines, I sort of need this to be in "Marine Terms" which means it needs to be broke down beyond barney style. If a 2 day old infant can't understand it, then it's not dumbed down enough. :P

Apprentice Joined: 14 Sep 2005 Posts: 121

I just got done looking at a datarecord, I remember someone referred one to me on a database question a while back. It works in that instance, but I don't see how it would work here.

Apprentice Joined: 14 Sep 2005 Posts: 121

I found the solution I needed, Twas quite simple really, but I was too out of it to realize it until I was at work today. I just replaced all the | in my prompt with © then used this to make it work