is there any way to drag the chocolatebars around or move them somehow, other than simply adding chocolate bars on top of other ones?
i'm trying to replace fubar with ldb and this seems to be the best option for my UI, but I can't get the chocolate bar in the right position, see my UI screenshot to see what I mean: http://s.wowinterface.com/preview/pvw30154.png
Calling the FontString:SetFont() method with an empty string as the first argument will crash the current 3.3 PTR client. I've reported this bug to Blizzard, but if it doesn't get fixed in the next few months before 3.3 goes live, you will need to change the behavior in ChocolateBar to avoid doing this.
This same bug (of Blizzard's) is still present in build 10554 of the 3.3.0 PTR.
Anyone using ChocolateBar on the PTR who hasn't copied over or edited their saved variables to use a new font will find their game crashing as the enter the game world.
Not sure if anyone has the same issue but since the docking code has been change (two or three revision ago, I'm using r82 right now), the LDB display on the right side goes off the bar a bit. For example, I have Borker uClock on the top right side, completely to the right and the minute digit is either completely off-screen or half off screen.
On the bottom right, I have Fubar_BagFu and again the right most digit is partially off screen.
Not sure if anyone has the same issue but since the docking code has been change (two or three revision ago, I'm using r82 right now), the LDB display on the right side goes off the bar a bit. For example, I have Borker uClock on the top right side, completely to the right and the minute digit is either completely off-screen or half off screen.
On the bottom right, I have Fubar_BagFu and again the right most digit is partially off screen.
When I try to change the font for Chocolatebar, I get this error:
1x ChocolateBar_Options-r97\Options.lua:322: attempt to index global 'LSM' (a nil value)
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[2]":9: in function <[string "safecall Dispatcher[2]"]:5>
(tail call): ?:
AceConfigDialog-3.0-43:796: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:611>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[3]":9: in function <[string "safecall Dispatcher[3]"]:5>
(tail call): ?:
AceGUI-3.0-30 (A3Fu_Bags):326: in function `Fire'
...ts\AceGUI-3.0-SharedMediaWidgets\SharedFunctions.lua:37: in function <...ts\AceGUI-3.0-SharedMediaWidgets\SharedFunctions.lua:30>:
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[3]":9: in function <[string "safecall Dispatcher[3]"]:5>
(tail call): ?:
AceGUI-3.0-30 (A3Fu_Bags):326: in function `Fire'
...s\AceGUI-3.0\widgets\AceGUIWidget-DropDown-Items.lua:339: in function <...s\AceGUI-3.0\widgets\AceGUIWidget-DropDown-Items.lua:334>:
When I try to change the font for Chocolatebar, I get this error:
1x ChocolateBar_Options-r97\Options.lua:322: attempt to index global 'LSM' (a nil value)
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[2]":9: in function <[string "safecall Dispatcher[2]"]:5>
(tail call): ?:
AceConfigDialog-3.0-43:796: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:611>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[3]":9: in function <[string "safecall Dispatcher[3]"]:5>
(tail call): ?:
AceGUI-3.0-30 (A3Fu_Bags):326: in function `Fire'
...ts\AceGUI-3.0-SharedMediaWidgets\SharedFunctions.lua:37: in function <...ts\AceGUI-3.0-SharedMediaWidgets\SharedFunctions.lua:30>:
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[3]":9: in function <[string "safecall Dispatcher[3]"]:5>
(tail call): ?:
AceGUI-3.0-30 (A3Fu_Bags):326: in function `Fire'
...s\AceGUI-3.0\widgets\AceGUIWidget-DropDown-Items.lua:339: in function <...s\AceGUI-3.0\widgets\AceGUIWidget-DropDown-Items.lua:334>:
I get this LUA error as well, posted it on the Curse site. I also get the same LUA error when changing the bar texture.
One of the features that didnt wanted me to switch from Fubar to Chocolate and LDB addons was there was no free placment of bars until lately wich made me happy I found a Bug in free bar placement tough.
I know is still a alpha version but wanted to send report anyway
How to reproduce it:
Create new bar, free placement, unlock move anywhere, lock, relog and bar wont be there.
i'm trying to replace fubar with ldb and this seems to be the best option for my UI, but I can't get the chocolate bar in the right position, see my UI screenshot to see what I mean: http://s.wowinterface.com/preview/pvw30154.png
Anyone using ChocolateBar on the PTR who hasn't copied over or edited their saved variables to use a new font will find their game crashing as the enter the game world.
Not sure if anyone has the same issue but since the docking code has been change (two or three revision ago, I'm using r82 right now), the LDB display on the right side goes off the bar a bit. For example, I have Borker uClock on the top right side, completely to the right and the minute digit is either completely off-screen or half off screen.
On the bottom right, I have Fubar_BagFu and again the right most digit is partially off screen.
Anyone else experience this?
Today's revision got it all fixed. Thank you!
I switched it to the alpha version of libjostle.
Date: 2009-12-26 12:44:32
ID: 4
Error occured in: Global
Count: 1
Message: ..\AddOns\ChocolateBar\Bar.lua line 9:
attempt to index local 'Bar' (a nil value)
Debug:
[C]: ?
ChocolateBar\Bar.lua:9: in main chunk
AddOns:
Swatter, v3.1.14 (<%codename%>)
Armory, vv7.6.3b
ArmoryGuildBank, vv7.6.3b
AucAdvanced, v5.7.4568 (KillerKoala)
AucFilterBasic, v5.7.4568 (KillerKoala)
AucFilterOutlier, v5.7.4568.2531
AucMatchUndercut, v5.7.4568.2531
AucStatClassic, v5.7.4568 (KillerKoala)
AucStatHistogram, v5.7.4568 (KillerKoala)
AucStatiLevel, v5.7.4568 (KillerKoala)
AucStatPurchased, v5.7.4568 (KillerKoala)
AucStatSales, v5.7.4568.2842
AucStatSimple, v5.7.4568 (KillerKoala)
AucStatStdDev, v5.7.4568 (KillerKoala)
AucStatWOWEcon, v5.7.4568.2530
AucUtilAHWindowControl, v5.7.4568.3311
AucUtilAppraiser, v5.7.4568.2530
AucUtilAskPrice, v5.7.4568.3175
AucUtilAutoMagic, v5.7.4568.3142
AucUtilCompactUI, v5.7.4568.2530
AucUtilEasyBuyout, v5.7.4568.3583
AucUtilFixAH, v5.7.4568 (KillerKoala)
AucUtilGlypher, v5.7.4568.2545
AucUtilItemSuggest, v5.7.4568.3108
AucUtilPriceLevel, v5.7.4568.2545
AucUtilScanButton, v5.7.4568.2530
AucUtilScanFinish, v5.7.4568.2530
AucUtilScanProgress, v5.7.4568.2530
AucUtilSearchUI, v5.7.4568.3655
AucUtilSimpleAuction, v5.7.4568.4553
AucUtilVendMarkup, v5.7.4568.2530
Babylonian, v5.1.DEV.130
BaudBag, v1.4.9
BrokerCPU, v30100.$Revision: 16 $
BrokerCurrency, v3.2.0.88
ChocolateBar, vr95
Configator, v5.1.DEV.190
DebugLib, v5.1.DEV.130
SlideBar, v3.1.14 (<%codename%>)
Stubby, v5.7.4568 (KillerKoala)
BlizRuntimeLib_enUS v3.3.0.30300 <us>
(ck=58d)
1x ChocolateBar_Options-r97\Options.lua:322: attempt to index global 'LSM' (a nil value)
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[2]":9: in function <[string "safecall Dispatcher[2]"]:5>
(tail call): ?:
AceConfigDialog-3.0-43:796: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:611>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[3]":9: in function <[string "safecall Dispatcher[3]"]:5>
(tail call): ?:
AceGUI-3.0-30 (A3Fu_Bags):326: in function `Fire'
...ts\AceGUI-3.0-SharedMediaWidgets\SharedFunctions.lua:37: in function <...ts\AceGUI-3.0-SharedMediaWidgets\SharedFunctions.lua:30>:
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[3]":9: in function <[string "safecall Dispatcher[3]"]:5>
(tail call): ?:
AceGUI-3.0-30 (A3Fu_Bags):326: in function `Fire'
...s\AceGUI-3.0\widgets\AceGUIWidget-DropDown-Items.lua:339: in function <...s\AceGUI-3.0\widgets\AceGUIWidget-DropDown-Items.lua:334>:
I get this LUA error as well, posted it on the Curse site. I also get the same LUA error when changing the bar texture.
I know is still a alpha version but wanted to send report anyway
How to reproduce it:
Create new bar, free placement, unlock move anywhere, lock, relog and bar wont be there.
Release tested was r99 though.
Thanks
Thanks, fixed in r100
Very strange, is this the first error you get?
Try r101, if you still have problems try to delete the saved variables of CB.