3.2 release candidate is upon us!
Collapse
X
-
I'd really like it if we could get it all over and done with much quicker, but having made a few releases now, experience tells me that it'll take a few years. I'd expect, though, that in even one year's time a lot of the changes will be pretty close to done.
If I could work full-time on Angband...takkaria whispers something about options. -more-Comment
-
Fixed thank you. Wow Nomads tilesComment
-
I noticed that in these RC versions so far, Macros don't seem to be working properly in David Gervais tile mode. Using a Paladin, I tried to create a Macro to cast spells from the priest's spell book (trigger is F1, F2, and F3), but every time I try to use the macros, all it does is open up the spell book. I also noticed that this problem does not occur in ASCI mode.Last edited by tg122; December 19, 2010, 07:17.Comment
-
I thought I would try out the nightly (0a7b85172a) and noticed a bug: accented characters are not showing up properly, at least on mac os x.
For example, Smฤล agol is displayed as Smรยagol; Angamaitฤลค is displayed as Angamaitฤย. The ฤล in Nฤลmenorean shows up as a dot.Comment
-
One for the Dark Lord on his dark throne
In the Land of Mordor where the Shadows lie.Comment
-
I think there may be a problem with your macros. I can create and use macros without problems in David Gervais tile mode. Can you provide some more details about the macros which work in ascii but not with these tiles - or maybe attach a prf file containing them? It's hard to fix if we can't reproduce the problem.I noticed that in these RC versions so far, Macros don't seem to be working properly in David Gervais tile mode. Using a Paladin, I tried to create a Macro to cast spells from the priest's spell book (trigger is F1, F2, and F3), but every time I try to use the macros, all it does is open up the spell book. I also noticed that this problem does not occur in ASCI mode."Been away so long I hardly knew the place, gee it's good to be back home" - The BeatlesComment
-
I just grabbed the latest nightly (0a7b851) to merge the latest changes into my 3.2 beta source (to fix the gold bug and so forth), and discovered that there have been a couple of changes that stop it compiling in VS2010.
Both z-form.c and z-textblock.c have been modified to now use the va_copy compiler macro, but this macro is apparently C99 only, not C89 (which the Angband coding guidelines say should be used) and VS2010 does not support it.
Can someone look at re-doing that code change in a way that's supported in C89 and therefore more broadly compiler friendly?Comment
-
Hmm. Not my area but there was a lot of chat on IRC last night about how to make this work. Apparently there's an MSVC problem which requires the va_copy macro - I'm not sure if there is an alternative solution which is C89 compliant. I know we had to disable strict C89 checking some weeks ago because of a completely unrelated change elsewhere in the refactoring.I just grabbed the latest nightly (0a7b851) to merge the latest changes into my 3.2 beta source (to fix the gold bug and so forth), and discovered that there have been a couple of changes that stop it compiling in VS2010.
Both z-form.c and z-textblock.c have been modified to now use the va_copy compiler macro, but this macro is apparently C99 only, not C89 (which the Angband coding guidelines say should be used) and VS2010 does not support it.
Can someone look at re-doing that code change in a way that's supported in C89 and therefore more broadly compiler friendly?
If you're interested in pursuing this, please take a look at http://trac.rephial.org/ticket/1254, which is what required the change in the first place. If you can find a different fix for this problem (which only affects AMD64 systems), which is C89-compliant and compiles under MSVC, please let us know."Been away so long I hardly knew the place, gee it's good to be back home" - The BeatlesComment
-
Oh, I hit this in rd1a64ee55c last night. It's actually the inscriptions at fault, since I'm not using macros, just numbered books. I found that '@p1' on a priest book didn't work, but '@m1' does, even if you use the 'p' key to cast.I noticed that in these RC versions so far, Macros don't seem to be working properly in David Gervais tile mode. Using a Paladin, I tried to create a Macro to cast spells from the priest's spell book (trigger is F1, F2, and F3), but every time I try to use the macros, all it does is open up the spell book. I also noticed that this problem does not occur in ASCI mode.
I'm not convinced it's got anything to do with tile mode, though: I've been using my own tiles, but I switched over to ASCII and still had this issue.Comment
-
As luck would have it, I'm running MSVC on an AMD64 system (exactly the combination that the fix says it won't work on) - although to complicate things slightly I'm using the x86 version of Windows 7, not the x64 version.Hmm. Not my area but there was a lot of chat on IRC last night about how to make this work. Apparently there's an MSVC problem which requires the va_copy macro - I'm not sure if there is an alternative solution which is C89 compliant. I know we had to disable strict C89 checking some weeks ago because of a completely unrelated change elsewhere in the refactoring.
If you're interested in pursuing this, please take a look at http://trac.rephial.org/ticket/1254, which is what required the change in the first place. If you can find a different fix for this problem (which only affects AMD64 systems), which is C89-compliant and compiles under MSVC, please let us know.
Unfortunately, this isn't really my area of expertise either - so I'm rather stumped as to an alternate fix.
If someone else comes up with a fix, I'm in a good position to test it, though.
By the way, the ticket seems to imply that va_copy is a noop on MSVC - with the implication that it will be ignored. This isn't the case. It actually stops compilation because it's an undefined symbol...Comment
-
After looking on the Internet, where there are lots of discussions about va_copy and MSVC, I've added...
...to the top of each of the two files that use it.Code:/* * Some compilers don't have va_copy predefined. * This redefinition may work as a substitute on some of them. */ #ifndef va_copy #define va_copy(ap1, ap2) ((ap1) = (ap2)) #endif
Some quick testing (acquiring random items - including artefacts - and identifying them) hasn't crashed it yet, so it might be a potential workaround for MSVC compilers - but I'm not qualified to judge for certain.Comment
-
Thanks for this. I'm sorry - I wrote my earlier reply before I noticed that d_m pushed a fix to staging after I went to bed last night. It's very similar to yours, so I've pushed it to master and you should be able to test it - either update from github and compile yourself or wait a couple of hours for the next nightly build.After looking on the Internet, where there are lots of discussions about va_copy and MSVC, I've added...
...to the top of each of the two files that use it.Code:/* * Some compilers don't have va_copy predefined. * This redefinition may work as a substitute on some of them. */ #ifndef va_copy #define va_copy(ap1, ap2) ((ap1) = (ap2)) #endif
Some quick testing (acquiring random items - including artefacts - and identifying them) hasn't crashed it yet, so it might be a potential workaround for MSVC compilers - but I'm not qualified to judge for certain.
Please let us know if it's fixed the problem."Been away so long I hardly knew the place, gee it's good to be back home" - The BeatlesComment
-
Well, the OP said specifically that he had a macro that worked in ascii but not in tile mode. That sounds very unlikely, but that's what he said.Oh, I hit this in rd1a64ee55c last night. It's actually the inscriptions at fault, since I'm not using macros, just numbered books. I found that '@p1' on a priest book didn't work, but '@m1' does, even if you use the 'p' key to cast.
I'm not convinced it's got anything to do with tile mode, though: I've been using my own tiles, but I switched over to ASCII and still had this issue.
I think this issue is very narrow indeed: I think it's specific to the p command and it's specific to @pX inscriptions where X is a single digit. For example, I can macro F2 to paa and it works fine for casting the first spell from the book I'm carrying in slot a.
In fact, testing reveals that this isn't a macro issue at all: the 'p' command does not recognise @pX inscriptions, whether in a macro or from direct input.
The p command was removed recently (by accident) and restored. I think somewhere during this process this problem was introduced.
I have opened ticket #1260 for this."Been away so long I hardly knew the place, gee it's good to be back home" - The BeatlesComment
Comment