Bill Roper (billroper) wrote,
Bill Roper
billroper

Behavior Modification

The reason that yesterday's code change didn't quite work right was because the flags that I had carefully set to say that all of the scenarios needed to be recalculated were moved in this release from the object that they had been in into another object which was being replaced by a different copy of the object before the calculation occurred. There was, of course, a perfectly good reason to move all of those flags (as in, it was required to make a new feature work), but it caused this piece of existing code to break.

Since I was the one who moved the flags, I guess it's good that I'm the one who found the break.

Solution? Set the flags again after substituting the saved copy of the object that holds them. That'll fix 'em... (mutter)
Tags: musings, work
Subscribe

  • Time for Rebuilding

    Well, there's nothing like research. Having determined that DDR5 is going to carry a substantial price premium over DDR4 memory for at least a year…

  • Driven Wild

    The studio computer continues to misbehave in various ways. When I fired up Cubase today, I got a lot of nasty, blocky video, despite having cleaned…

  • Some Old Doggerel

    I recall having mangled a CSN tune many years ago on the way to Contraption. Like that convention, the particular co-worker whose code I was digging…

  • Post a new comment

    Error

    Anonymous comments are disabled in this journal

    switch
    default userpic

    Your reply will be screened

    Your IP address will be recorded 

    Help
  • 0 comments