---

Playing emulated 2D games with anything other than an exact pixel scaling bugs me.

---

Hmm, you can tell the difference here? http://img512.imageshack.us/img512/5963/aapoint.png

And that's only at 2x scale. At 5x I have to use a paint program and zoom in to see the differences.

I wish we didn't have to use non-square pixels, too; but it distorts the video pretty badly if you use exact multiples of 256. People look super thin, the moon in Chrono Trigger looks like an oval, etc
I kind of miss CRT monitors and their ability to display 8:7 resolutions directly. But I don't miss the geometry distortion along the corners.

---

Seriously? I wouldn't call that a mess. I looked at the code, it seems pretty tidy, especially compared to mine.

---

Mostly meaning that it's heavily tailored to bsnes' specific needs, instead of being more general purpose. Same thing with my custom file dialog.

---

(Especially considering that it's done using C++, which I find a lot harder to use than Python/PyQt because of all the memory management that needs to be done )

---

I don't usually mind memory management, and I actually cheat a bit -- I don't always delete "permanent" objects that are created at startup like I should. My reasoning is that the OS process termination cleans them up anyway

But Qt is downright scary. It "acquires" all the pointers you feed into it, and deletes them all for you. It's ... very disorienting when you're not used to it. But you can literally throw new Q[ObjectName]'s all around and you won't leak memory, so long as you delete the grandparent. It actually makes it a real treat to use.

Example:

---

  for(unsigned i = 0; i < mapper().size() i++) {

    InputGroup &group = *(mapper()[i])



    QTreeWidgetItem *grandparent = map[group.category];

    if(!grandparent) continue;



    QTreeWidgetItem *parent = new QTreeWidgetItem(grandparent)

    parent->setData(0, Qt::UserRole, QVariant(-1))

    parent->setText(0, group.label)



    for(unsigned i = 0; i < group.size() i++) {

      QTreeWidgetItem *child = new QTreeWidgetItem(parent)

      child->setData(0, Qt::UserRole, QVariant(inputTable.size()))

      inputTable.add(group[i])

    }

  }

---

____________________
"Elements of the past and the future, combining, to make something not quite as good as either."

Ooooh, 6x width to 5x height sounds very intriguing. Let's see ...

The aspect correction ratios are:
NTSC: width * 54 / 47
That gives 1536x1120 when we want 1471x1120 -> 6x5

PAL: width * 32 / 23
That gives 1792x1200 when we want 1781x1200 -> 7x5

PAL is much wider than NTSC for some reason.

This is indeed wonderful for 1920x1200 monitors. Kind of a shame the market is heading toward 1920x1080.

EDIT: I'll update my "Scale 5x" option to do 6:5 NTSC and 7:5 PAL. Thanks for the idea!

____________________
"Elements of the past and the future, combining, to make something not quite as good as either."

Yeah, it would only be ideal for fullscreen use. I always leave windowed mode at 2x scale.

I've implemented the change. Here are some example pictures:

http://byuu.org/temp/ntsc-1.png
http://byuu.org/temp/ntsc-2.png
http://byuu.org/temp/pal-1.png

____________________
"Elements of the past and the future, combining, to make something not quite as good as either."