Zugg Software :: View topic

Apprentice Joined: 29 Dec 2000 Posts: 146 Location: USA

I'm having real trouble with this...

ok, I keep one floating window with all the 'communication' trafic.. seems to be a pretty common thing. Real easy set of triggers...

%1 tells you in %2 -> #window talk {%ansi( bold, red)%1 tells you %2}
%1 gossips, %2 -> #window talk {%ansi( high, cyan)%1 gossips %2}
You gossip, %1 -> #window talk you Gossip %1
%1 says, %2 -> #window talk {%ansi( bold, white)%1 says, %2}

so my thought on this (and maybe I'm totally misunderstanding the idea behind packages)
I create a package (call it comm)
then, I assign this package to all the chars I want to use these features (which is pretty much all) and be done with it.

Then if I want to edit this specific set of triggers (say add a timestamp %time("hh:mm:ss)" ), I edit ONE package, and not the same triggers in 20 different character files

Well I can't get the above to work AT ALL. I get a couple of different results...
#1 --it starts yelling about a looping trigger (it's trying to run the comm package triggers on the floating window, I can't seem to stop this)
#2 -- it don't work at all, won't open the talk window if it's not open, won't pipe any of the text over.
#3 -- it crashes (sent in a bug report a few mins ago, just trying to look at the compiled script tab)

so I'm back to zmud again, til I can get at least this working.

The good news, the mapper seems to run much faster than the previous version.
This is running just 1 character, I normally run 2 chars at the same time.

The only thing I can think of here, is I'm misunderstanding how this should be working. help is appreciated.

thanks

Apprentice Joined: 29 Dec 2000 Posts: 146 Location: USA

ok, I played with it a bit more (sent several more crash dumps), and I may have figured out at least part of the issue.
Cmud just does not like my .mud file
I created a new session,
manually made my layout changes,
manually added my triggers (dual monitors, with zmud running in one, cmud in the other)
and now it seems to behave much better.

I can now remove packages from the talk window, without crashing.

I do have one bug report (not sure it will get seen from in here)
I open a package and create a new trigger.
decide oh, that really should have gone into a class.
create a new class folder drag and drop the trigger into the new class folder.

at this point cmud will decide on some random view to give you, possibly into a package you hadn't even opened.