Since WotLK there seems to be a problem with the cooking and alchimist buttons on deDE clients. Blizzard somehow decided that the grand master ranks are named "Alchemie" and "Kochen" instead of "Alchimie" and "Kochkunst", as the lower ranks are named. So, after reaching Grand Master in them both icons disappear from the professions button.
There also seems to be some disorder in the quest item buttons while rearranging them. Sometimes the icons rearrange but the functionality does not, so during some quests I was using the wrong item, which in some cases was fatal, like the Drakuru quest line in Zul'Drak. I could not find out under which circumstances this happens, it is not easy to reproduce.
Sorry that I am not more helpful here. If I can do something to help figuring it out, just tell me and I'll gladly do.
JWU is of now a discontinued project, i dont have the energy to keep fighting the small hurdles that seems to appear on wowace and curse all the time.
Thank you all for the time you used JWU, and may your time with Curse Client be as happy as your time with JWU.
/Rolf
Thank you for your work with JWU. It's sad to see you go.
In fact all this is sad to see happen. JWU was the last updater I could use. I don't blame you, rolfba, I can see that you don't have the energy to keep on fighting and understand that your thesis is much more important.
java -jar JWowUpdater.jar
Exception in thread "main" java.lang.UnsupportedClassVersionError: Bad version number in .class file
at java.lang.ClassLoader.defineClass2(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:719)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:160)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:254)
at java.net.URLClassLoader.access$100(URLClassLoader.java:56)
at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:268)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
I'm using the same Java version as before, which is
java version "1.5.0_14-p8"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_14-p8-root_02_mar_2008_22_14)
Java HotSpot(TM) Server VM (build 1.5.0_14-p8-root_02_mar_2008_22_14, mixed mode)
I have access to a leather worker, so I will look into that salt shaker thing in the weekend.
For now I added "Brilliant Glass" to Jewelcrafting, durcyn, could you please commit it?
I looked at BT4 and I really like the keybinding mode.
Will you make it optional or the only way to configure, just like it is in bt4 right now?
If so I wouldn't be that fond of it. Because in bt4 the keyboard settings are not seen in Blizzard's keybinding interface. If rebinding something there you get a warning, just like the one you get in bt4's /kb. But: When the keybings made in keybinding mode are not visible to the standard keybinding interface you don't see if you change one of bt4's keybindings by accindent nor will you get a warning.
I don't think this is how I want AutoBar to behave, because I might end up with a accidently unbound keys without noticing it immediately. The worst situation to notice it then is when you are in the middle of a boss fight, which, thanks to murphy, will be exactly the case ;)
Do you have Feral Charge but not an actual Bear or Dire Bear form? I moved the code around to check for that but I did not think it is possible... r74340
No, of course not. My toon is a feral druid at level 70, so it has Dire Bear form. Is there anything I can do to debug it? Please tell me, I'd be glad to help. Whether you tell me on #wowace or here is the same to me. Do as you please.
SunTsu
PS.: Tried your latest change right now. Did not change anything for me except that it is line 1208 now. Could it be a localization problem? I am using deDE locales
I'm getting the following error on Revision 74242 right now:
..\AddOns\AutoBar\AutoBarButton.lua line 1206: bad argument #1 to 'concat' (table contains non-strings)"
This looks like a problem with the recently added druid buttons, because I don't get any error as warrior or rogue. I just commented out the Feral Charge lines and the error went away for me.
Could you please look into it?
Thanks alot for your great work on AutoBar,
SunTsu
< CIA-40> mikk * r70644 Baggins_AnywhereBags/ (Baggins_AnywhereBags.toc Core.lua Guildbank.lua):
< CIA-40> Baggins_AnywhereBags:
< CIA-40> - Add support for guild bank. Will appear as a character named e.g. "<MyGuild>"
Of course it updates them.
But there is no point in scanning for updates twice.
Until that last new version there was a check on start up and another one of every non-ace-addon during the upgrade. During that scan it would upgrade the recently checked addon.
So, the point would be to keep in memory which non-ace-addons had to be updated and just do that during the update phase.
rolfba chose to do it the other way around, which is not quite what I would have done, but still is an improvement.
The basic goal was to have working non-ace-upgrades without redundant update-checks, which, hopefully, is reached. Whether the check should be done during the initial update scan, which I'd prefer, or during the updates itselves, which rolfba implemented, is just a matter of taste and oppinion.
If the addon author releases an addon update as a "beta" release, as its probabely the case with Outfitter 4.1b5, then JWU dosent update. Its only the release versions submitted to curse that is checked.
OK, I didn't know that but makes sense now that i know.
But still there are those temporary problems with curse. JWU from time to time tells me that addons don't exist on Curse, which they normally do.
I don't know whether this is a problem on curse's side or on JWU's.
I'm experiencing that, too, from time to time.
Looks like there still is a problem with the curse layout.
Yesterday JWowUpdater did the "cound not be found" thing to me on SolarianAlarm and Outfitter. Today it doesn't but still won't update Outfitter though there is a new version. (4.1b5 vs. 4.0.1)
0
There also seems to be some disorder in the quest item buttons while rearranging them. Sometimes the icons rearrange but the functionality does not, so during some quests I was using the wrong item, which in some cases was fatal, like the Drakuru quest line in Zul'Drak. I could not find out under which circumstances this happens, it is not easy to reproduce.
Sorry that I am not more helpful here. If I can do something to help figuring it out, just tell me and I'll gladly do.
PS: This is "v696 beta release"
Regards,
SunTsu
0
Thank you for your work with JWU. It's sad to see you go.
In fact all this is sad to see happen. JWU was the last updater I could use. I don't blame you, rolfba, I can see that you don't have the energy to keep on fighting and understand that your thesis is much more important.
Good luck with it, then.
SunTsu
0
There seems to be another source. I still have that problem, not as frequently as I had it, but it still exists.
Sorry to be the one with the bad news,
SunTsu
0
0
I'm using the same Java version as before, which is
This ist FreeBSD, as you might remember.
Would you please look into it?
Thanks in advance,
SunTsu
0
For now I added "Brilliant Glass" to Jewelcrafting, durcyn, could you please commit it?
Works for me, I hope it does for everyone.
SunTsu
0
Will you make it optional or the only way to configure, just like it is in bt4 right now?
If so I wouldn't be that fond of it. Because in bt4 the keyboard settings are not seen in Blizzard's keybinding interface. If rebinding something there you get a warning, just like the one you get in bt4's /kb. But: When the keybings made in keybinding mode are not visible to the standard keybinding interface you don't see if you change one of bt4's keybindings by accindent nor will you get a warning.
I don't think this is how I want AutoBar to behave, because I might end up with a accidently unbound keys without noticing it immediately. The worst situation to notice it then is when you are in the middle of a boss fight, which, thanks to murphy, will be exactly the case ;)
Just my 0.2 cents,
SunTsu
0
That bothered me all the time from when I first looked at it.
I hope it works for everybody else.
SunTsu
*edit* Forgot to do the same thing to "Bear Form"
0
No, of course not. My toon is a feral druid at level 70, so it has Dire Bear form. Is there anything I can do to debug it? Please tell me, I'd be glad to help. Whether you tell me on #wowace or here is the same to me. Do as you please.
SunTsu
PS.: Tried your latest change right now. Did not change anything for me except that it is line 1208 now. Could it be a localization problem? I am using deDE locales
0
This looks like a problem with the recently added druid buttons, because I don't get any error as warrior or rogue. I just commented out the Feral Charge lines and the error went away for me.
Could you please look into it?
Thanks alot for your great work on AutoBar,
SunTsu
0
Looks like a dream finally came true.
Thanks a lot, mikk
SunTsu
0
Great, then I just misunderstood your changelog. This was just what I was proposing.
But, I know, I am a spoil sport, I still get "... with ID: [...] could not be found on site: [CURSE]", so it looks like there is some more to it.
Anyway, great Job, Rolf. I really love JWU!
SunTsu
0
But there is no point in scanning for updates twice.
Until that last new version there was a check on start up and another one of every non-ace-addon during the upgrade. During that scan it would upgrade the recently checked addon.
So, the point would be to keep in memory which non-ace-addons had to be updated and just do that during the update phase.
rolfba chose to do it the other way around, which is not quite what I would have done, but still is an improvement.
The basic goal was to have working non-ace-upgrades without redundant update-checks, which, hopefully, is reached. Whether the check should be done during the initial update scan, which I'd prefer, or during the updates itselves, which rolfba implemented, is just a matter of taste and oppinion.
SunTsu
0
OK, I didn't know that but makes sense now that i know.
But still there are those temporary problems with curse. JWU from time to time tells me that addons don't exist on Curse, which they normally do.
I don't know whether this is a problem on curse's side or on JWU's.
Thanks for the quick reply,
SunTsu
0
Looks like there still is a problem with the curse layout.
Yesterday JWowUpdater did the "cound not be found" thing to me on SolarianAlarm and Outfitter. Today it doesn't but still won't update Outfitter though there is a new version. (4.1b5 vs. 4.0.1)
If I can help debugging it, just let me know.
SunTsu