08/07/08, 1:47 PM
|
#85 (permalink)
|
|
Von Kaiser
|
The author posted the following last night on WoWInterface. Looks promising.
Here's a short list of features that are implemented in the next release:
Click-activated actions on rings
There are now two ways to interact with a ring, controllable via a per-ring option:
1. Push binding to show a ring -> Position Mouse Pointer -> Release binding to activate action.
2. Press binding to show or hide a ring -> Move Mouse -> Left-click to activate action.
Because it's a per-ring option, you may choose which rings you want to use which behavior; this enables you to save yourself from wasting consumables and still use the simpler option for rings that aren't critical.
"Only while I have this item" slices
Added a per-slice option to custom rings to hide the slice if you don't have the item it wants in your inventory.
There's a fix in for the bug that's preventing any ring from being deleted in 0.9, as well as an additional feature that keeps bundled rings from re-appearing after they have been deleted. Additionally, a copy of the saved variable table is now kept in the global namespace, so if WoW panics and decides to dump the saved variables to disk without firing the relevant events, you shouldn't be liable to lose rings previously saved to disk.
The current plan is to make hiding of the shapeshift/aura bar a configurable option before the next release, but that hasn't been done yet.
Comments on some of the suggestions raised in comments:
Binding to mouse buttons
OPie blocks left/right mouse button bindings (in its bindings UI) by design; this is intended and unlikely to change.
Modifiers should work in combination with any mouse button but the left and right: you may freely bind rings to, say, alt+Middle Button or ctrl+shift+alt+Mouse Button 5.
Activating rings using action bars
You could, but it's non-trivial (and wouldn't make sense in 0.9, as you can't "release" the action bar macro conditionally). It makes a bit more sense with the click-to-activate behavior in 0.10, but it'll still remain a bit of a hack: you need to find the internal ring name used by OPie, then construct a macro that looks like: /click ORTB__(Internal Ring Name) use 1 -- for example /click ORTB__OPieDruidShift use 1 or /click ORTB__CommonTrades use 1 or /click ORTB__OPieTrinkets use 1.
Default actions
are an interesting idea, but would probably rob you of the "safe" region to cancel the ring use in, and would require you to spawn rings at mouse. Seems too limiting
|
|
|
|
|
|
|