Clique

27 - Out-Of-Range Targets on the Default Compact Frames

What steps will reproduce the problem?
1. (Optional) Disable all add-ons except for Clique.
2. Create two Clique bindings on a single key: one "default" binding which casts a friendly, targeted ability (e.g. Healing Wave), and one "global" binding which casts a non-targeted ability (e.g. Water Shield).
3. Join a party or raid.  If joining a party, ensure that "Use Raid-Style Party Frames" is enabled in the Interface Options. (Possibly necessary: If joining a raid, ensure that "Keep Groups Together" is disabled.  Comment: When in a party, enabling this option gives you the "CompactParty" frames of WoW 4.0.6. When in a raid, enabling this option gives you the "CompactGroup" frames, which I think are not recognized in Clique's BlizzardFrames.lua
4. Position yourself so that a member of your group is out-of-range (OOR) of your friendly, targeted ability.
5. Try the following:
    5a. Move your cursor to a frame that lacks a target attribute (e.g., the WorldFrame or a CompactRaidMemberXBuffX) and is also adjacent to the unit frame of a group member that is OOR. Now slide your cursor directly onto the OOR unit's frame, and press your bound key.
    5b. Move your cursor to a frame that has a target attribute (e.g., a CompactRaidMemberX) whose target *is* within range and is also adjacent to the unit frame of a group member that is OOR. Now slide your cursor directly onto the OOR unit's frame, and press your bound key.

What is the expected output?
I expect to see Blizzard's "Out of range" error message appear near the top-center of my screen.  No abilities should be cast, and a glowing hand cursor for the friendly, targeted ability should *not* be activated.

What do you see instead?
Step 5a: Pressing the bound key results in the activation of the glowing hand cursor for the friendly, targeted ability.  Pressing the bound key once more (or Escape) will cancel the glowing hand.  Pressing the bound key subsequently will cause the non-targeted ability to be cast.
Step 5b: Pressing the bound key results in casting the non-targeted ability.  (Variation: If the friendly, targeted ability is setup as a "friendly" binding instead of a "default" binding, then pressing the bound key in this step does nothing. The "Out of range" error is still not reported.)

What version of the product are you using?
Clique v40100-1.3.5.

Do you have an error log of what happened?
This issue does not produce any errors.

Please provide any additional information below.
It is possible that being in combat affects this issue, but I still need to test this further.  I have experienced both the expected behavior (when I am sure I was in combat) and the issue I describe (when I was possibly out of combat) at different times in different battlegrounds.  I have done most of my testing out of combat in a capital city in a party with one other person, and under these conditions the issue is always reproduced.

User When Change
cerbul May 17, 2011 at 07:45 UTC Changed status from Waiting to Replied
Cladhaire May 16, 2011 at 16:05 UTC Changed status from New to Waiting
worstcase86 May 10, 2011 at 16:58 UTC Create

You must login to post a comment. Don't have an account? Register to get one!

  • 6 comments
  • Avatar of Cladhaire Cladhaire May 17, 2011 at 07:59 UTC - 0 likes

    Please just stop. The issue has been reported, and I don't have a fix for it. I have given you code to test. I'm fully aware that these two issues are linked.

    As I've said about ten times now, you can have one of two behaviours:

    1. Go back to the old problem where dangling bindings stick around when a frame is obscured or hidden. These bindings will be cleared after you use them once when your mouse is not over the frame.
    2. The current behaviour.

    That's it. I'm really not interested in further hypothetical discussions. I can give you a 100% accurate description of precisely what is happening right now (and I have ,actually) but I'm not interested in further discussion about this.

    Please test the code I've given you and see for yourself.

    I'm really quite and very willing to help. I spent about 2.5 hours on your issues last night between debugging and trying to come up with a solution. Just calm down and listen to what I've had to say, nothing is going to change that.

  • Avatar of cerbul cerbul May 17, 2011 at 07:49 UTC - 0 likes

    There is also other thing that is wrong, and as the OP stated, is dependant on rendering of the mouseover player. Here is what I get, assuming that I have my mouse away from any frame before I target the OOR player:

    If the player that I cast a spell on is an OOR player that is NOT rendered, I get a glowing hand. If the player that I cast a spell on is an OOR player that IS rendered, I get the spell canceled, correctly.

    I would love to get the spell canceled in both cases, and never get a glowing hand.

  • Avatar of cerbul cerbul May 17, 2011 at 07:45 UTC - 0 likes

    Sorry to interfere into this thread, but I searched a bit around and I feel like this ticket is about the exact same problem that I have, just that the OP posted with an OOR player instead of a dead/offline one. As I see here, the OP wants to get an "Out of range" error message instead of a glowing hand. But seems like, exactly as in my case, when the mouse is away from frames first, it will correctly show the "Out of range" error message, but if he targets a valid player frame first and then directly moving mouse over the OOR player, there will be a glowing hand when trying to cast anything.

    In my case I was getting the spell casted on my Target, instead of getting the glowing hand, like the OP did. Both behaviors are wrong, as long as you have your mouse over a dead/offline/out of range/out of line of sight player, the spell should fail completely, and not get it casted to my target or to get a glowing hand.

  • Avatar of Cladhaire Cladhaire May 16, 2011 at 16:03 UTC - 0 likes

    There is absolutely no way for me to detect is the case, the API just doesn't allow for it. This is the behaviour of the default UI when using similar mouseover macros, so I'm not sure what I can do, if that's the issue that we're describing.

  • Avatar of worstcase86 worstcase86 May 11, 2011 at 00:44 UTC - 0 likes

    @Cladhaire: Go

    /me is a fool.

    New observation: If your OOR target is near enough that his or her model is rendered in the world, you will get the expected behavior. If they are so far away that they are not rendered, you should get the behavior I describe here.

    I'm not so sure I'd call this an "issue" anymore, although it is weird. It is most likely that the times I am accidentally burning my cooldowns are due to the "primary issue" we discussed weeks ago. I'm going to put in a formal ticket for that, since I am still experiencing it.

  • Avatar of Cladhaire Cladhaire May 10, 2011 at 20:34 UTC - 0 likes

    I'm unable to reproduce this. I did the following, precisely, with both Barkskin and Hurrican:

    1. Create a new Clique profile so I have no bindings
    2. Bind 'Hurricane', a non-targeted ability to 'w', ONLY set to 'Global' bind set
    3. Bind 'Nourish', a targeted healing spell to 'w', ONLY set to 'default'
    4. Test that I can heal myself with 'w' and cast 'Hurricane' when not over a unit frame.
    5. Join a party with a guild-mate
    6. Ensure CompactRaidFrames is enabled
    7. Move out of range of the party-member
    8. Hover my mouse to the right of the frame over WorldFrame.
    9. Move into the OOR member's unit frame and press 'W". I get "Out of range".
    10. Put the mouse over my frame, and heal myself.
    11. Moving from my unit frame south into the OOR unit frame.
    12. Press 'W'. I get "Out of range".

    I'm not sure what I'm doing wrong.

  • 6 comments

Facts

Last updated
May 17, 2011
Reported
May 10, 2011
Status
Replied - Someone has replied after waiting for more information.
Type
Defect - A shortcoming, fault, or imperfection
Priority
Medium - Normal priority.
Votes
0

Reported by

Possible assignees