MT 1.3b34 Progress update
Moderators: dorpond, trevor, Azhrei
- trevor
- Codeum Arcanum (RPTools Founder)
- Posts: 11311
- Joined: Mon Jan 09, 2006 4:16 pm
- Location: Austin, Tx
- Contact:
MT 1.3b34 Progress update
I fell asleep at the keyboard while fixing some UI tweaks last night, oops.
Build definitely some time today.
Build definitely some time today.
Dreaming of a 1.3 release
Re: MT 1.3b34 Progress update
Well, you might check that section of code very carefully first...coherency may be suspect.trevor wrote:I fell asleep at the keyboard while fixing some UI tweaks last night, oops.
Build definitely some time today.
I know the things I write while drifting off are often a bit wonky.
Not exactly fit for compiling or publication.
But we are patient.
Or something.
0+0=1, for very unstable CPUs.
- Mathemagician
- Dragon
- Posts: 666
- Joined: Tue May 22, 2007 2:27 pm
Anecdote: When I was writing my town generator way back in the day, I had the most frustrating bug! All the men in the town were leaving their wives. At first I claimed brilliance that my fake people so quickly learned to divorce one another, until I noticed the wives still thought they were married to their respective husbands, but the men were nowhere to be found! I stayed up working on that darn bug til 5 in the morning, when I finally passed out on the keyboard.
It turns out, in trying to fix the bug (a simple fix, actually) I made things much worse. I had made the mistake of using lower case L as my indexing variable when choosing wives for the husbands, and somehow a 1 got there instead. Long story short, every man in the town was assigned, at one point or another, woman[1] as their wife, only to be booted out by the next man in line. Talk about a girl getting around the town...
Moral of the story, coding when falling asleep can ruin the reputation of a lot of imaginary people
Alternative moral, if you feel compelled to use a lower case L as your index variable, it might be worth the extra keystrokes to type "ell"
It turns out, in trying to fix the bug (a simple fix, actually) I made things much worse. I had made the mistake of using lower case L as my indexing variable when choosing wives for the husbands, and somehow a 1 got there instead. Long story short, every man in the town was assigned, at one point or another, woman[1] as their wife, only to be booted out by the next man in line. Talk about a girl getting around the town...
Moral of the story, coding when falling asleep can ruin the reputation of a lot of imaginary people
Alternative moral, if you feel compelled to use a lower case L as your index variable, it might be worth the extra keystrokes to type "ell"
See, this is why l and 1 and I are bad indices. (Can you tell which is which? Guess.)Mathemagician wrote:Anecdote: When I was writing my town generator way back in the day, I had the most frustrating bug! All the men in the town were leaving their wives. At first I claimed brilliance that my fake people so quickly learned to divorce one another, until I noticed the wives still thought they were married to their respective husbands, but the men were nowhere to be found! I stayed up working on that darn bug til 5 in the morning, when I finally passed out on the keyboard.
It turns out, in trying to fix the bug (a simple fix, actually) I made things much worse. I had made the mistake of using lower case L as my indexing variable when choosing wives for the husbands, and somehow a 1 got there instead. Long story short, every man in the town was assigned, at one point or another, woman[1] as their wife, only to be booted out by the next man in line. Talk about a girl getting around the town...
Moral of the story, coding when falling asleep can ruin the reputation of a lot of imaginary people
Alternative moral, if you feel compelled to use a lower case L as your index variable, it might be worth the extra keystrokes to type "ell"
It is so font dependent that you have no business using any of the three: one, upper-case i, and lower-case L are all too similar in english without context. Terrible decision.
Coding while tired=dangerous.
0+0=1, for very unstable CPUs.
- UntoldGlory
- Great Wyrm
- Posts: 1649
- Joined: Sun Mar 16, 2008 8:12 pm
- UntoldGlory
- Great Wyrm
- Posts: 1649
- Joined: Sun Mar 16, 2008 8:12 pm
What we need is someone else to magically appear like Ryss and take over another section of the code.trevor wrote:I'm not personally adding any features as I've been focused on reviewing integrating the patches and fixing bugs. But Ryss has been hard at work on the macro panel and all of his updates are going in.
*Casts "Summon Coder XII"
Hmm....
Let's see if it works.
Maybe it's a 4e ritual?
0+0=1, for very unstable CPUs.
- Naryt
- Dragon
- Posts: 517
- Joined: Fri Oct 26, 2007 8:55 am
- Location: Near a tree, in a cave, under a rock.
OT: Fonts
Very easy to tell but then again, that's why I use a font that has serifs.Orchard wrote:See, this is why l and 1 and I are bad indices. (Can you tell which is which? Guess.)
A wandering lost soul
Re: OT: Fonts
Again, font choice is important.Naryt wrote:Very easy to tell but then again, that's why I use a font that has serifs.Orchard wrote:See, this is why l and 1 and I are bad indices. (Can you tell which is which? Guess.)
But back to the topic at hand.
I'm glad to see a quick bug-fix. Trevor's dedication to this community continues to amaze me.
0+0=1, for very unstable CPUs.
- UntoldGlory
- Great Wyrm
- Posts: 1649
- Joined: Sun Mar 16, 2008 8:12 pm