Quote:
Originally posted by Accredo
Thanks Darq for your detailed reply and sorry for my not-so-quick one
"I tried your MinimumSize=258,76 in the group window (it only occurs once) and change the 76 to 50" suggestion and it worked just fine and is certainly close to what I was looking for.
Sadly I have another problem and perhaps only isolated to my system. Prior to making the above changes I began to experience keyboard lockups when I clicked any C2C; in this case Arcane and Elemental (I didn't get any of the others during this time)
The following is what would happen: Btw: This also occurred after I made the above change as well:
A.
-Clean install: w/Drums GU57UI less the C2C xml's (installed your Utilities)
-Clicked (insert arcane or elemental here)
-Keyboard locked up (Numlock was not affected) which would indicate it was not a system lockup.
-Keyboard unlocked as soon as 1) the mob died or 2) The Det timer expired.
B.
-Clean install: w/Default GU57UI and your Utilities
-Clicked (insert arcane or elemental here)
-Keyboard locked up (Numlock was not affected)
-Keyboard unlocked as soon as 1) the mob died 2) Det timer expired.
C.
After I made the MinimumSize changes the above same occurred in the same sequence.
I loaded up DrumsUI GU57UI (Clean load w/o your utilities) and all was fine casting the C2C's
|
Accredo, thank you for this report, and I'm sorry you're having trouble with the group window. I would like to see your group window data (at least the custom part between the Start and End markers) if you would do me the favor of sending it to me in an email on this website.
I did log in and test the click-to-cures with several setup combinations and I could not get the keyboard to lock up on me. I have my graphics settings turned way way up (from checking out the new spell animations) and I was amazed at the lag spike from some of the spells, priest cures included. I tried casting a cure on a group/raid member and then immediately using the keyboard to type a tell or using the arrow keys to turn in a circle and all of those worked, save for the substantial video hiccup just at the moment the cure was cast. This is not the same symptom you described, but it was the closest thing I could get to a lockup.
I do know that in the past when manually editing the windows, I have gotten lockups if I forgot to leave a space character between empty quotes in the XML data. By that I mean if you look at the data, all of the empty slots aren't really empty. They require at least a single space character (for example:
Gsay=" " as opposed to
Gsay=""). But when I have made this error it locks up the game completely. I've searched through the code to see if I made this error on tooltips, class detects, etc., and so far I don't see it.
Two other incidentals: 1) I formed a raid to test the raid window for your error and just happened to switch to "basic" mode on the right-click menu, thinking about your earlier question. Interestingly, the cure banks disappeared and I was left with just the default raid layout with the spell sets overlaid on the character (modes 1 through 4). So we may already have the raid window fixed like you want it. Once I started changing spell sets between characters it snapped back out to the larger size, but if you leave the character switcher alone it works well.
2) I did discover an issue with self-curing from the group window when you don't have a group -- instead of finding yourself it tries to find "g1" which is nomenclature for the Battlegrounds compatibility. Once you form a group, "g1" makes sense to the game and the self-cures work as they should. That was a last-minute oversight on my part and I'll patch it soon. In the meantime, I suggest self-curing while soloing with the threat/detrimental icons which have no Battlegrounds references.
__