Event system gui improvement. (Almost ready to release, help find bugs)

[DrenDran]

In responce to this thread:
http://forum.blockland.us/index.php?topic=176751.0

This is what it looks like right now, more or less:


Download:
http://www.gamefront.com/files/21126786/Client_NewEvents.zip

The name system is different though, if you choose fxDTSBrick as your target, you get an extra parameter.
The first parameter is the brick names box if the target is fxDTSBrick. You type in the bricks names. You can have more than one, and it'll automatically create separate events for each one after you click send, for example:
onActivate -> fxDTSBrick -> setRendering -> |√|  |self brick1 brick2|
Make an event like that, and when you click send, three events will be created, one that's like the old "self" target, and one for "brick1" and one for "brick2".
Or leave it blank, and it'll just create one "self" target.
The red buttons under the "used" check boxes will clear that row.
If anything glitches up real bad, just hit "send" and click "Events" in the wrench window, the gui should reset, but keeping all your events.

[Ad Bot]

[jes00]

So far it works the same except the delay is in a different spot?

[pecon98]

I like this. Do you think that when you start getting to improvements maybe it could have input parameter support?

[DrenDran]

So far it works the same except the delay is in a different spot?

The red/green background is obviously different, event enabling was taken out for now (will probably end up doing it differently) but otherwise, no real changes. I want it to be tested as is and fix current bugs now, before I move on adding more features.

I like this. Do you think that when you start getting to improvements maybe it could have input parameter support?

You mean like, conditionals?

[pecon98]

You mean like, conditionals?

Yes.

[Lugnut]

So far it works the same except the delay is in a different spot?

That's what it looks like, but I'll definately be following this.

[DrenDran]

I just made the copy button work.
I'll update soon.

[jes00]

Will this allow people to create delays over 30000?

[DrenDran]

Will this allow people to create delays over 30000?

I haven't checked weather that's a server limitation or a client one.
If the latter, then sure, if the former, then there's nothing I can do about it.

[Greek2me]

So this doesn't need anything server-sided? Good.

[Superb]

This doesn't look to good.

[Greek2me]

This doesn't look to good.

Yeah, the GUI looks really crappy. But that's easy enough to change once it's all scripted.

Actually Dren once you finish scripting this would you want to send it to me so I can make a new GUI?

[DrenDran]

So this doesn't need anything server-sided? Good.

Nope.

This doesn't look to good.

What do you mean?
It's obviously not finished yet, I'd just like everyone to keep that in mind.

Once the parameters and named brick abilities are added, and this lets you do everything you could do with the old gui, I hope to start adding the improvment features everyone wants.


edit:

Yeah, the GUI looks really crappy. But that's easy enough to change once it's all scripted.

Actually Dren once you finish scripting this would you want to send it to me so I can make a new GUI?

Possibily, but a lot of the gui is rooted in the scripting.
What would you like to see change currently?

[Ephialtes]

How's this an improvement when you removed a core piece of functionality like enabling and disabling events? I would call it more of a botched face lift.

[DrenDran]

How's this an improvement when you removed a core piece of functionality like enabling and disabling events? I would call it more of a botched face lift.

I do believe I've explained a few times I want to get the basics working and tested before I start the 'improvements'. Enabling will be added back in later on, I was waiting to see if I could handle/implement it any differently.