| Anonymous | Login | Signup for a new account | 19-06-26 10:51 CEST |  |
| Main | My View | View Issues | Change Log | Roadmap |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update | |
| 0002121 | SphereServer | executable - generic | public | 15-12-12 02:10 | 06-01-13 16:09 | |
| Reporter | babidi | |||||
| Assigned To | Ben | |||||
| Priority | normal | Severity | major | Reproducibility | always | |
| Status | closed | Resolution | no change required | |||
| Platform | OS | OS Version | ||||
| Product Version | 20-09-2009, 0.56b Prerelease | |||||
| Target Version | Fixed in Version | |||||
| Summary | 0002121: x set real command | |||||
| Description | if you use f_oncommand for intercept command it will work until you begin using a mix of x and set example kill can be write with a series of x and set like: xkill x.kill x.set.kill xsetxsetsetxkill etc... there is no way to understand the real command | |||||
| Tags | No tags attached. | |||||
| Nightly Version | Not Available | |||||
| Experimental Flags | None | |||||
| Option Flags | None | |||||
| Internal Build Number | ||||||
| Attached Files |  xxxx.png [^] (92,519 bytes) 05-01-13 21:50
| |||||
 Relationships |
|
 Relationships |
|
Notes |
|
|
(0001452) Ben (manager) 29-12-12 01:01 |
There is nothing to change here. Out of all the commands that you wrote, only .kill and .xkill are valid. So you just need to intercept those 2 and your done! Any other combination will simply result in an "Invalid Set" error in sphere, so there is absolutly no reason to try and intercept them |
|
(0001455) babidi (reporter) 05-01-13 21:50 edited on: 05-01-13 21:51 |
of course it works. you have to target yourself until you arrive to the last command. Look at the screen of the journal i updated for an example |
|
(0001457) Ben (manager) 06-01-13 16:02 |
That kind of information should be said right away instead of making me waste my time! Anyways, there is nothing that can be done to improve this. You just need to be more creative when scripting. Here are some examples of ways to intercept these commands IF (STRMATCH("set*","<args>")) Message "Any command that start with .set" ENDIF IF (STRMATCH("x*","<args>")) Message "Commands that start with .x" ENDIF IF (STRMATCH("*kill","<args>")) Message "Any combination of chars with Kill at the end" ENDIF |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 15-12-12 02:10 | babidi | New Issue | |
| 29-12-12 01:01 | Ben | Note Added: 0001452 | |
| 29-12-12 01:01 | Ben | Status | new => closed |
| 29-12-12 01:01 | Ben | Assigned To | => Ben |
| 29-12-12 01:01 | Ben | Resolution | open => no change required |
| 05-01-13 21:50 | babidi | Note Added: 0001455 | |
| 05-01-13 21:50 | babidi | Status | closed => feedback |
| 05-01-13 21:50 | babidi | Resolution | no change required => reopened |
| 05-01-13 21:50 | babidi | File Added: xxxx.png | |
| 05-01-13 21:51 | babidi | Note Edited: 0001455 | View Revisions |
| 05-01-13 21:51 | babidi | Note Edited: 0001455 | View Revisions |
| 06-01-13 16:02 | Ben | Note Added: 0001457 | |
| 06-01-13 16:09 | Ben | Status | feedback => closed |
| 06-01-13 16:09 | Ben | Resolution | reopened => no change required |
|
Issue History |
| Copyright © 2000 - 2010 MantisBT Group |
 |