I like these lines of code:

  const double left1  = inst1->x + inst1->bbox_left,  top1    = inst1->x + inst1->bbox_top,
               right1 = inst1->x + inst1->bbox_right, bottom1 = inst1->x + inst1->bbox_bottom;

    const double left2  = inst2->x + inst2->bbox_left,  top2    = inst2->x + inst2->bbox_top,
                 right2 = inst2->x + inst2->bbox_right, bottom2 = inst2->x + inst2->bbox_bottom;

something like that would require changes in the behavior of the textarea in order to underline the words or otherwise indicate where problems are. That would be a fair bit more extensive. Once that's done, it would be a simple matter of figuring out some efficient way to perform the check.

@polygone: LGM doesn't perform syntax checking, it delegates that task off to ENIGMA, since that's where the competent parser is.

OK. Would the interface not need to be done by LGM though?

What interface? I add a button somewhere that delegates to Enigma's checkForDuplicateVariables method?

JButton b = new JButton("DupVars");
b.addActionListener(new ActionListener() { public void actionPerformed(ActionEvent e) { EnigmaDriver.checkForDuplicateVariables(); } });
add(b);

done.

@polygone: LGM doesn't perform syntax checking, it delegates that task off to ENIGMA, since that's where the competent parser is.

I agree. You're experiencing a dozen different problems here which I don't know if we've corrected half of them with later revisions or what. Truth is, the zip has become dreadfully outdated now. I'd recommend doing a fresh checkout from the SVN. Join the IRC for more instructions. It's ok to experience problems with it, it's probably not your fault, it's probably ours - stuff we still need to fix. So do report your problems before you just hack it together to work for yourself, but also realize that we have broken some of our older release stuff that should have been kept stable or at least updated. Meh, it's a work in progress, what can I say.

So because the user fails at setting up their own path variable, we give them assistance? I don't... nevermind...

[bin path]

What is the bin path for? What makes that vary?
Also, you should clarify why you need to specify the makefile location.

Skeptical, not dubious. If a part of you is dubious, that means that it's hard to believe that part of you - e.g. questioning part of your existence... On the other hand, skeptical indicates that the part of you is still questioning things. Dubious applies *to* something, skepticism comes *from* something.

If you make it complex enough and it works, nobody will bother touching it.

That's what I was thinking from the start.

For low-level functions that intend to go into the back-end, it's not uncommon for people to use straight C++ rather than EDL.

We can have a wiki page that provides a fairly full introduction for beginners. Our wiki isn't just for explaining individual components, it's for general documentation, and can house tutorials and instructions.

I'm pretty sure with() just gets converted into the iterator, so there's no speed benefit one way or the other.

Actually the wiki might be part of the solution here. First off, if it's not already the case, we're highly interested in linking up the wiki login with site login, so you don't have to create a new account. Once on the wiki, every user has a user page, which is kinda your blank slate profile information which other users can also edit and contribute to.

LGM passed font information to ENIGMA, and passes each glyph separately. Josh asked for a compression callback, so I provided one. Everyone was using font_load_from_sprite, which required each subimage be a separate glyph, so to alleviate the processs I added in sprite strip loading into LGM. At this point, LGM+Plugin does everything ever asked of it to make the font support easier, short of drawing the glyphs itself each draw event... the rest is Josh being too lazy to do anything about it, or to even bother finding out/reporting any problems with the stuff I provided him.

Edit: guy32123 was nice enough to report that populating the font glyphs sometimes somehow populates more than 255 glyphs, causing an ArrayIndexOutOfBoundsException. I'm investigating it right now and trying to reproduce it.

Edit2: I think I fixed that. Should be in for the next revision (r583).