Newb(ish) question - Page 3

Mathias · February 4th, 2014, 07:50 AM

#resmax[resAdvance] is calculated in a script on the resAdvance pick itself, at Setup/2000.

You should have a script at setup/2010 that re-calculates the XP/advances, and then sets #resmax[resAdvances] = the number it calculated. Having to add to both resLeft and resMax in a script is a kludge. Even if you're not fixing it in your own code, I'd appreciate it if you could fix it in the code examples thread - if you're posting examples for everyone to learn from, those examples should be well-constructed examples.

SeeleyOne · February 4th, 2014, 08:08 AM

Thanks. I was thinking about the inelegance of the fix. I hate writing kludgey code. It works, but your way is better. I will fix it this evening.

SeeleyOne · February 4th, 2014, 03:13 PM

I fixed it in the Common Code thread. It works great and is cleaner. The syntax is generally not so much the issue, but figuring out the timing is what I need to learn now. When I started messing with Hero Lab in the past I had no coding experience. While that is not really needed (so long as you can find an example to copy from elsewhere), now that I have learned Java and C++, I find that it makes a lot more sense overall.

zarlor · February 4th, 2014, 04:47 PM

If it helps any there is some documentation on Timing if you go to the Help file in the Editor. Of course that does not necessarily tell you the exact timing of some stuff, but some of that can be found in the various source files.

SeeleyOne · February 4th, 2014, 05:19 PM

I have found the Develop -> Floating Info Windows -> Show Task List (either Active Hero or Full List) to be helpful. I have found the help files to not be as helpful as I would have liked. If they were more extensive and up to date they would be far more helpful. But there is relatively little demand. It seems that most people think that they need to be master programmers to learn how to use the editor.

zarlor · February 5th, 2014, 08:13 AM

BTW, thanks for testing and getting all that worked out. Hopefully if we do see a decision to give us something like an entry in the Editor to modify this your work will make it easier to implement, but a definite thanks for adding it to the Common Code thread. I think that will be really helpful since I've seen it mentioned a few different times here by different people so hopefully that will be really useful for them.

SeeleyOne Senior Member Join Date: Nov 2009 Posts: 891 February 4th, 2014, 08:08 AM	Thanks. I was thinking about the inelegance of the fix. I hate writing kludgey code. It works, but your way is better. I will fix it this evening. Evil wins because good rolls poorly .... or the players are not paying enough attention to the game.
#22