Zugg Software :: View topic - [3.34] BUG: #T+ is not working properly, when we use more than one window at...

Wanderer Joined: 07 Jun 2009 Posts: 65

My session has 3 main windows: mud, logs: chat and quests.

If you read something in the window 2 or 3 will trigger the following alias to #t+ does not bring the desired rezultu and the results of %trigger is as follows:

Sorcerer Joined: 15 Apr 2011 Posts: 809

Try putting the settings you want to share between windows in a separate module, or use the //window/class/.../setting syntax to tell CMUD exactly where to look for the setting. You might also want to change the title of your post, I assume by #T? you meant #T+ and #T-, but #T? is actually a different command in CMUD, so I was momentarily confused when the post itself had nothing to do with it.

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

Any setting that is inside a window cannot be seen by other settings outside that window. Is this the problem you're seeing?

Posted: Fri Aug 12, 2011 4:32 pm

That's always been the case. If you're wanting to execute an alias from an alternative window, you'll need to do something like:

Sorcerer Joined: 15 Apr 2011 Posts: 809

Not true, Matt, you just have to use //window/class/... to reference it.

Wanderer Joined: 07 Jun 2009 Posts: 65

@Daern ofc #t+ / #t- / %trigger, my fault;]

@MattLofton exactly

@charneus the point is that for an alias, which operates in an X session for X session it should not matter which window I have just activated. Alias has to act in this window, which was called, unless it contains the user type # execwin: window_name: alias, etc.

most likely obstacle to mutual understanding is my knowledge of English;]

edit:
@charneus I do not want to play in multisessions, in my opinion,% trigger / # t + not working properly.
cmud performs alias in the first window, I read the logos in the second, and the alias is trying to # t + in the second instead of first. ;]

really do not know how it is easier to describe ...

Wanderer Joined: 07 Jun 2009 Posts: 65

Sorcerer Joined: 15 Apr 2011 Posts: 809

As I said in my first post, you could just make a module, and put all settings that you want to share between all windows in that module, instead of tying them to one window. Then you shouldn't need the #execwin command to execute commands in a separate window, you can use those settings from any window.

Wanderer Joined: 07 Jun 2009 Posts: 65

But why? I want to run an alias in the window in which it was called. So the first. Cmud should function properly regardless of how many windows and the sessions have also included.

I have no problem with the syntax, and an obvious error function "% trigger."

Please take a alias as in the example and call it by "# wait 3000; alias" and switch to another window. Alias will perform in the right window, but the% trigger and # t + will appeal to a window that is currently active / focus.
This is wrong!

Posted: Sat Aug 13, 2011 6:45 pm

Maybe I'm not understanding the issue entirely but if you want to enable/disable triggers in another window why don't you just specifcy the full path to them?

Wanderer Joined: 07 Jun 2009 Posts: 65

Since # t + should work by default in the window, where it was called. No matter whether I am at the time of the script switches to another window and read the logs ...

@ orphean not an option because it would have for each session and each trigger separately define "/ / window / / myclass / /". As a temporary solution and at the same time effectively applied #execwin %window {#t+ tr_checkaff}

It remains my hope that someone will test this issue and confirm the bug, which causes the patch in a subsequent version cmuda ...

Sorcerer Joined: 15 Apr 2011 Posts: 809

Araadan, I don't see the difference between adding //window/class to all your triggers, and adding #execwin %window to all your triggers. They'll both work in the long run anyway, but the former will be more efficient, so it's the recommended method of the two. I don't understand why you're so against using it. As for whether it's a bug, I don't think you decide that. It could really go either way, and I think at this point we need to wait for Zugg to comment. He's the only one who can decide if it's a bug or not.

Enchanter Joined: 09 Sep 2007 Posts: 605

Wanderer Joined: 07 Jun 2009 Posts: 65

@ Arde thank you for your support.
Analyzed my script for your comments and in fact, before each occurrence of an alias is used #wait.
On the other hand ... I think that pointed out the general direction and has made efforts to help identify the problem - the rest is a matter of programmers.
Fortunately, I found a temporary way to avoid this problem in the critical points.

ps. when I could write on the forum in Polish or German without googl translate? : P