Just wanted to acknowledge that I've just read them and intend to see what can be done when I have the time/energy. (Props to both of you!)
However, I need some further details on your suggestions before I can come up with an optimal solution to them. I'm not sure when I'll
be able to make the updates, but I should be able to roll one out in a couple of months.
Will drop you both a PM shortly.
Thanks for your support!
FuzzYD
PS: I'm no longer a regular here, but I do check back on the occasion. Lifes kinda caught up with me and my interest has moved towards other programming projects outside the world of mapping.
(21/08/12) b04b: Minor patch to address some bugs with auto-portrait detection. SetPositionDC and SetSizeDC also now support ALL labels. (They were previously locked, but I felt it was restrictive when users want to play with the label positions.)
Hotfix is complete. I've tested it and it's working fine for the examples so far. Further feedback from the community would be appreciated should there be any bugs encountered. Thank you for using BossBars+!
May I know which version you're currently using and what error message its throwing please? (Screenshot's will do as well)
I suspect it's got something to do with (:value) could not be assigned or something along that line. Blizz changed the way some of their functions worked in 1.5, I suspect that might be the cause. I'll try roll out a hotfix for this ASAP, but I need a little more info on what might be causing it.
Update: I'll only be able to roll out a fix this coming Monday. There's been a few significant unpublished changes made to the library since the latest stable release (v03b). I'll need some time to clean it up and make sure everything is working as intended.
Noted, Thanks for the approval! I've got an update planned sometime over the next week or so, polished up much of the code into a more easily importable format. I plan to include the dependencies into the package, do you think this would suffice?
Okay.. Just run into that crappy problem where you can't override an old library without it breaking every damn function.. Does anyone have any idea how this might be done?
EDIT:
Do not update to Beta 03 yet, It might not be stable. I'm having some problems with ports. The library breaks for no reason when I save and load it.
EDIT #2:
Library support will be removed in Beta 03b. Libraries in their current state are too broken to be of any use. I apologize to anyone who has been using the Library and is in need of reworking any broken functions.
Beta 03 has been released. Please read the changelog
as there are some important changes for those of you who have participated in Beta 02. In particular, the way labels work has been revamped, thus a concern is that it may have broken your maps. No functions however were changed, thus there should be no issues with portability.
Please remember to update QuickLib to the latest version A01e as well.
It comes prepacked with the library. An important fix was made inside it that fixes the way colors are applied.
Thanks for backing me up on this one xXdRaGoNrIdDeRXx :) My bad for not making it clear in the first place that BossBarSetTextLabel must be used to set the player name. I've edited the function description on the opening posts in hopes of making this clearer.
That's great news :) Next fix might take awhile as it might require a rework of all the labels to fix up the click-through problem. The bbSetRace will be fixed at the same time. I'd prefer not to make another release with only such a simple change.
Another possibility is that the player name is being set as text before the players unit is being set. (Though I kinda doubt this since you say it works locally) This would cause the player name to be overridden by the automatic labeling feature. The fix to this would be to set the player name after the unit has been set. If this is the root of the problem, I will consider adding a function to allow auto-labels to be disabled as well.
Btw, check my last post for the screenshot of the player name working.
@Myteq: Go
@SoulTaker916: Go
Hey fellas,
Thanks for the suggestions/feedback.
Just wanted to acknowledge that I've just read them and intend to see what can be done when I have the time/energy. (Props to both of you!) However, I need some further details on your suggestions before I can come up with an optimal solution to them. I'm not sure when I'll be able to make the updates, but I should be able to roll one out in a couple of months.
Will drop you both a PM shortly.
Thanks for your support!
FuzzYD
PS: I'm no longer a regular here, but I do check back on the occasion. Lifes kinda caught up with me and my interest has moved towards other programming projects outside the world of mapping.
(21/08/12) b04b: Minor patch to address some bugs with auto-portrait detection. SetPositionDC and SetSizeDC also now support ALL labels. (They were previously locked, but I felt it was restrictive when users want to play with the label positions.)
@Tommerbob: Go
Awesome sauce. Thanks for the feedback :)
Hotfix is complete. I've tested it and it's working fine for the examples so far. Further feedback from the community would be appreciated should there be any bugs encountered. Thank you for using BossBars+!
@Tommerbob: Go
May I know which version you're currently using and what error message its throwing please? (Screenshot's will do as well)
I suspect it's got something to do with (:value) could not be assigned or something along that line. Blizz changed the way some of their functions worked in 1.5, I suspect that might be the cause. I'll try roll out a hotfix for this ASAP, but I need a little more info on what might be causing it.
Update:
I'll only be able to roll out a fix this coming Monday. There's been a few significant unpublished changes made to the library since the latest stable release (v03b). I'll need some time to clean it up and make sure everything is working as intended.@JademusSreg: Go
Yeap. Most of the dependencies are my own custom scripts. As for external libraries I'll keep note to link them should I use any.
@iE4TM4PS: Go
Nice stuff, don't mind if I link this to the opening post? Might make it clearer as to what can be done with this library.
@Spoilerfx: Go You're welcome :)
@JademusSreg: Go
Noted, Thanks for the approval! I've got an update planned sometime over the next week or so, polished up much of the code into a more easily importable format. I plan to include the dependencies into the package, do you think this would suffice?
@xXdRaGoNrIdDeRXx: Go
Noted. Thanks for the feedback :)
Okay.. Just run into that crappy problem where you can't override an old library without it breaking every damn function.. Does anyone have any idea how this might be done?
EDIT:
Do not update to Beta 03 yet, It might not be stable. I'm having some problems with ports. The library breaks for no reason when I save and load it.
EDIT #2:
Library support will be removed in Beta 03b. Libraries in their current state are too broken to be of any use. I apologize to anyone who has been using the Library and is in need of reworking any broken functions.
EDIT#3:
Beta 03b has been released.
Beta 03 has been released. Please read the changelog
as there are some important changes for those of you who have participated in Beta 02. In particular, the way labels work has been revamped, thus a concern is that it may have broken your maps. No functions however were changed, thus there should be no issues with portability.
Please remember to update QuickLib to the latest version A01e as well.
It comes prepacked with the library. An important fix was made inside it that fixes the way colors are applied.
@xXdRaGoNrIdDeRXx: Go
Thanks for backing me up on this one xXdRaGoNrIdDeRXx :) My bad for not making it clear in the first place that BossBarSetTextLabel must be used to set the player name. I've edited the function description on the opening posts in hopes of making this clearer.
@xXdRaGoNrIdDeRXx: Go
Thanks, I'm glad you appreciate it =)
@xXdRaGoNrIdDeRXx: Go
That's great news :) Next fix might take awhile as it might require a rework of all the labels to fix up the click-through problem. The bbSetRace will be fixed at the same time. I'd prefer not to make another release with only such a simple change.
im not setting the player name im using the function name of player and this happens after you pick your character so its not that
Hm. Alright. Check your PM? I'll see i can help you troubleshoot this.
Note: im gonna test it now just have to wait my upload is terrible plus i have to start up 2 sc2's
Heh.. you have no idea. I have to use cheatengine just to get a 10mb map uploaded. My connection keeps timing out within the 2 minutes.
Note to self:
@xXdRaGoNrIdDeRXx: Go
Another possibility is that the player name is being set as text before the players unit is being set. (Though I kinda doubt this since you say it works locally) This would cause the player name to be overridden by the automatic labeling feature. The fix to this would be to set the player name after the unit has been set. If this is the root of the problem, I will consider adding a function to allow auto-labels to be disabled as well.
Btw, check my last post for the screenshot of the player name working.