Build 21 and the current state of the project

[Freddie]

This is the last suggestion for the entry window from the other thread. Any comments?

[Svpernova09]

This is the last suggestion for the entry window from the other thread. Any comments?

Is there any way to specify a character (as opposed to a WoW) It has always been easier for me to think in terms of what keys I'm sending which toon, not always which WoW. Maybe I'm just odd

[Freddie]

Is there any way to specify a character (as opposed to a WoW) It has always been easier for me to think in terms of what keys I'm sending which toon, not always which WoW. Maybe I'm just odd

That's the kind of thing this thread will help decide. So please, discuss! I'm listening.

Things don't have to work just one way. In fact I'd like the program to be extremely flexible so people can use it however they like. The tricky thing is designing the program so it provides lots of choices but seems simple to the user and not confusing.

[Svpernova09]

That's the kind of thing this thread will help decide. So please, discuss! I'm listening.

Well, I certainly don't want to steer you towards something thats totally different than your design. I don't know much about HKN, but from what I had seen, the scripts always named wow's wow1, wow2, etc. ISBoxer names the wow windows by Character name -> Character Set. IMHO, it would be easier to name the wow's by at least the character so you can see easier (again, imo) which keys are being sent to which toon and not have to worry about remember which WoW is which character. Maybe have a character based configuration and have that apply to a WoW "instance"? So you setup all your keybinds that get send to your tank, and you have a "tank" configuration that you can apply to whichever WoW instance is your tank.

Maybe individual character configurations would be overly complicated.

[Freddie]

People can name things however they like in both programs.

This isn't designed yet so please say any ideas you want. I've been thinking tentatively of configuring WoWs, Toons, and Teams. The first two sound like your WoW and tank.

I don't think per-character configuration is too complicated, but I think people should be able to configure things in other ways if they want.

[Svpernova09]

People can name things however they like in both programs.

This isn't designed yet so please say any ideas you want. I've been thinking tentatively of configuring WoWs, Toons, and Teams. The first two sound like your WoW and tank.

I don't think per-character configuration is too complicated, but I think people should be able to configure things in other ways if they want.

I agree completely with giving people multiple ways to configure things. I was just thinking in terms of other applications and how well / not so well they handle configuration.

[Vecter]

Well, I certainly don't want to steer you towards something thats totally different than your design. I don't know much about HKN, but from what I had seen, the scripts always named wow's wow1, wow2, etc. ISBoxer names the wow windows by Character name -> Character Set. IMHO, it would be easier to name the wow's by at least the character so you can see easier (again, imo) which keys are being sent to which toon and not have to worry about remember which WoW is which character. Maybe have a character based configuration and have that apply to a WoW "instance"? So you setup all your keybinds that get send to your tank, and you have a "tank" configuration that you can apply to whichever WoW instance is your tank.

Maybe individual character configurations would be overly complicated.

I would have to agree on Svpers point as well. I don't configure based on WoW instance but rather Char/Char Set. The instance of WoW a char belongs to is not pivotal to my configuration (at least setup wise.)