Dolphin, the GameCube and Wii emulator - Forums

So... Guess who has a working GUI?

Mario&Lunch
Soup+Pasta Saga

(06-24-2015, 02:20 AM)Shonumi Wrote: [ -> ]So... Guess who has a working GUI?

Shonumi could you release a compiled version it's really been a long time.

Things are pretty rough (code-wise) at the moment, but I'll see what I can do. I haven't set up a Windows development environment in a long time. May take a while but I'll get back to you

Downloads SDL2, it needs SDL1.
Build using MSVC, it needs C99.
Here's GUI less version for now.

Last time I tried switching to SDL2, got a reproducable -5% performance increase. Planning to move to SDL2 eventually once I figure out what went wrong. No idea why MSVC needs C99 when this is 99% a C++ project though (maybe I'm forgetting something about the standards).

Marked Unofficial

VC complains about length not being a constant.  Rereading Stack Overflow its C++14 feature that C99 already has.

Unless that method is inlined and _length is compile-time constant, I wouldn't call it a constant if it changes :o

It's just a plain old int as a parameter. Any inlining I leave to the compiler.

To be fair, I haven't compiled with G++ warnings in a long time. I should get around to that eventually. Nice task for weekend.

So now I am working on a puzzle game, where users can make and share puzzles on Facebook. One of the things with the game is that it's much easier to make puzzles than solving them (they are sort of NP-hard unless there's deductions to figure out each part at a time, like in Sudoku).

But one of the issues is while it's fun to make hard levels, often people don't have enough motivation to solve them. So I was thinking it would be cool if the creator could set a bounty ($$$) on the puzzle, and whoever solved it first got the bounty. (The puzzle would expire in some time, and the bounty would be paid back to the creator). There could also be a price for trying to solve the puzzle, increasing the bounty from everyone who failed.

I've looked into facebook APIs and taking the payments seems easy enough... but I guess you may have to write the part that pays back the money yourself? In case it could quickly get difficult in ascertaining that the program doesn't suddenly empty your bank account to some hacker or something? Does anyone know if this is at all feasible without an expensive team of security experts?