Stand alone init frame [Dev]

[aliasmask]

Anyone have a stand alone version of the initiative frame. I would like to add my own event handlers when someone's initiative begins and ends. Too bad there are no existing hooks for that for the existing initiative box.

[plothos]

I have started work on one of these, but it's not very far along and I haven't much time lately.

[aliasmask]

I'm just looking to something that produces a frame that I can add selected tokens to init, set the init, move up and down init order, has pictures w/names, can hide tokens init from others... basically, most of the things the current init panel does. I just need the hooks to run my own macros when current init changes.

I have started work on one of these, but it's not very far along and I haven't much time lately.

I know what you mean

[Raoden]

Heh, yeah, I've thought about this, but it hasn't made the top of my project priority list yet.

One thing, though: I don't think we're going to be able to duplicate the Initiative panel's way of displaying tokens' States.

[CoveredInFish]

Have you checked out RPTroll's Savage Worlds framework? He has completely avoided MT's ini mechanisms while implementing a complete ini solution. Dont know if it is "reusable" but it might be worth a look ...

[aliasmask]

Have you checked out RPTroll's Savage Worlds framework? He has completely avoided MT's ini mechanisms while implementing a complete ini solution. Dont know if it is "reusable" but it might be worth a look ...

Yeah, I know of some other frameworks by rep alone that do some init window substitution, but I was trying to avoid hacking out the bits of code I need if there was something stand alone out there.

I have a ton of projects I'm working on, all half done because I run in to a road block or something else I should do before that code is complete. But it's all slowly coming together. My main focus for today and tomorrow is to release my Spell Lib 2.0... but it'll be more of a 1.3 because I'm not going to complete some features I wanted for 2.0 but the major changes will be done.. ie no campaign properties needed, no tables needed but the config tools won't be done like adding a new spell, but the macro will be there to do it manually.

[plothos]

This is still very rough, but it might help. Attached are a lib token for my first pass at the init panel and a macro to be dropped on tokens or the global/campaign panels to add selected tokens to the new init panel.

[files moved below - found a bug and reposted]

[Rumble]

I started writing one of these and realized I was simply rewriting most of the initiative handling that happens in the Init Window. It's probably better to leverage as much of the initiative handling elements (reordering, delay, etc.) that's already there, and build a 'wrapper' around it using macros.

I took that approach in my frameworks - I have a set of macros built around turn advancement, but I let the initiative panel manage the initiative array, tell me which token was in initiative, which was up next, sort and reorder initiative, and all that. The macros that surround that functionality are what handle whether (for instance) the token who is gaining initiative has to take some ongoing damage, or whether any of the tokens on the map had a condition that was supposed to expire this turn.

Bottom line is that I would not discard the init panel entirely; there's a lot of handling code in there you'd have to reproduce otherwise.

[plothos]

Pretty sure all I'm missing is the state images, the ability (for now) to toggle hold, and the ability to drag tokens around (have to click arrows up and down).

Though I do have to expand on this to fiddle with how much access players have, etc. Should not be that hard to work up though.

[aliasmask]

I'm all for using the init panel with wrappers, but I just wanted to avoid the clicking of the next button in that panel force of habit. If I could disable the next button, that would work better. I never notice that before, but I see a lock movement. I imagine that locks movement for players when it's not their init. I'm not sure how "owner permissions" work in the init panel though.

[plothos]

Cleaned up a few things and added some functionality. And since nobody had even dl'ed the first one, no worries there.

[aliasmask]

Cleaned up a few things and added some functionality. And since nobody had even dl'ed the first one, no worries there.

I definitely get around to it and thanks for the work. I'll check it out after this weekend.

[Raoden]

Yeah, I'll check it out soon too.

Pretty sure all I'm missing is the state images, the ability (for now) to toggle hold, and the ability to drag tokens around (have to click arrows up and down).

Though I do have to expand on this to fiddle with how much access players have, etc. Should not be that hard to work up though.

What about the ability to double-click on a token to center your view on it and select it? I like what we're doing here, but Rumble might be right -- the default Init panel has a lot of bells and whistles attached to it already.

I'm all for using the init panel with wrappers, but I just wanted to avoid the clicking of the next button in that panel force of habit. If I could disable the next button, that would work better.

It's an ugly solution, but I suppose you could always just make a dummy Frame, make it tiny, and plop it over the default "Next" button.

[prestidigitator]

What about the ability to double-click on a token to center your view on it and select it? I like what we're doing here, but Rumble might be right -- the default Init panel has a lot of bells and whistles attached to it already.

It's not quite a double-click, but a button or link could easily use Wiki: goto() to do that.

[aliasmask]

It's an ugly solution, but I suppose you could always just make a dummy Frame, make it tiny, and plop it over the default "Next" button.

But I'm more worried about the players doing it rather than me.

It's not quite a double-click, but a button or link could easily use Wiki: goto() to do that.

I think it is a double click that will center and select the token. I use that all the time and it's a feature I really like. I try to use generic names and the only difference is in the number after the name. The token has the selected box around it that I look for. This is more of an issue when I have many tokens on the board.