2010-09-26 05:09:31 +00:00
|
|
|
/****************************************************************************
|
2011-09-05 03:48:23 +00:00
|
|
|
** Meta object code from reading C++ file 'platform.moc.hpp'
|
2010-09-26 05:09:31 +00:00
|
|
|
**
|
Update to v094r08 release.
byuu says:
Lots of changes this time around. FreeBSD stability and compilation is
still a work in progress.
FreeBSD 10 + Clang 3.3 = 108fps
FreeBSD 10 + GCC 4.7 = 130fps
Errata 1: I've been fighting that god-damned endian.h header for the
past nine WIPs now. The above WIP isn't building now because FreeBSD
isn't including headers before using certain types, and you end up with
a trillion error messages. So just delete all the endian.h includes from
nall/intrinsics.hpp to build.
Errata 2: I was trying to match g++ and g++47, so I used $(findstring
g++,$(compiler)), which ends up also matching clang++. Oops. Easy fix,
put Clang first and then else if g++ next. Not ideal, but oh well. All
it's doing for now is declaring -fwrapv twice, so you don't have to fix
it just yet. Probably just going to alias g++="g++47" and do exact
matching instead.
Errata 3: both OpenGL::term and VideoGLX::term are causing a core dump
on BSD. No idea why. The resources are initialized and valid, but
releasing them crashes the application.
Changelog:
- nall/Makefile is more flexible with overriding $(compiler), so you can
build with GCC or Clang on BSD (defaults to GCC now)
- PLATFORM_X was renamed to PLATFORM_XORG, and it's also declared with
PLATFORM_LINUX or PLATFORM_BSD
- PLATFORM_XORG probably isn't the best name ... still thinking about
what best to call LINUX|BSD|SOLARIS or ^(WINDOWS|MACOSX)
- fixed a few legitimate Clang warning messages in nall
- Compiler::VisualCPP is ugly as hell, renamed to Compiler::CL
- nall/platform includes nall/intrinsics first. Trying to move away from
testing for _WIN32, etc directly in all files. Work in progress.
- nall turns off Clang warnings that I won't "fix", because they aren't
broken. It's much less noisy to compile with warnings on now.
- phoenix gains the ability to set background and foreground colors on
various text container widgets (GTK only for now.)
- rewrote a lot of the MSU1 code to try and simplify it. Really hope
I didn't break anything ... I don't have any MSU1 test ROMs handy
- SNES coprocessor audio is now mixed as sclamp<16>(system_sample
+ coprocessor_sample) instead of sclamp<16>((sys + cop) / 2)
- allows for greater chance of aliasing (still low, SNES audio is
quiet), but doesn't cut base system volume in half anymore
- fixed Super Scope and Justifier cursor colors
- use input.xlib instead of input.x ... allows Xlib input driver to be
visible on Linux and BSD once again
- make install and make uninstall must be run as root again; no longer
using install but cp instead for BSD compatibility
- killed $(DESTDIR) ... use make prefix=$DESTDIR$prefix instead
- you can now set text/background colors for the loki console via (eg):
- settings.terminal.background-color 0x000000
- settings.terminal.foreground-color 0xffffff
2014-02-24 09:39:09 +00:00
|
|
|
** Created: Fri Feb 14 13:37:55 2014
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
** by: The Qt Meta Object Compiler version 63 (Qt 4.8.2)
|
2010-09-26 05:09:31 +00:00
|
|
|
**
|
|
|
|
** WARNING! All changes made in this file will be lost!
|
|
|
|
*****************************************************************************/
|
|
|
|
|
|
|
|
#if !defined(Q_MOC_OUTPUT_REVISION)
|
2011-09-05 03:48:23 +00:00
|
|
|
#error "The header file 'platform.moc.hpp' doesn't include <QObject>."
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
#elif Q_MOC_OUTPUT_REVISION != 63
|
|
|
|
#error "This file was generated using the moc from 4.8.2. It"
|
2010-09-26 05:09:31 +00:00
|
|
|
#error "cannot be used with the include files from this version of Qt."
|
|
|
|
#error "(The moc has changed too much.)"
|
|
|
|
#endif
|
|
|
|
|
|
|
|
QT_BEGIN_MOC_NAMESPACE
|
2013-03-15 13:11:33 +00:00
|
|
|
static const uint qt_meta_data_phoenix__pTimer[] = {
|
2011-06-05 03:45:04 +00:00
|
|
|
|
|
|
|
// content:
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
6, // revision
|
2011-06-05 03:45:04 +00:00
|
|
|
0, // classname
|
|
|
|
0, 0, // classinfo
|
|
|
|
1, 14, // methods
|
|
|
|
0, 0, // properties
|
|
|
|
0, 0, // enums/sets
|
|
|
|
0, 0, // constructors
|
|
|
|
0, // flags
|
|
|
|
0, // signalCount
|
|
|
|
|
|
|
|
// slots: signature, parameters, type, tag, flags
|
2013-03-15 13:11:33 +00:00
|
|
|
17, 16, 16, 16, 0x0a,
|
2011-06-05 03:45:04 +00:00
|
|
|
|
|
|
|
0 // eod
|
|
|
|
};
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
static const char qt_meta_stringdata_phoenix__pTimer[] = {
|
|
|
|
"phoenix::pTimer\0\0onActivate()\0"
|
2011-06-05 03:45:04 +00:00
|
|
|
};
|
|
|
|
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
void phoenix::pTimer::qt_static_metacall(QObject *_o, QMetaObject::Call _c, int _id, void **_a)
|
|
|
|
{
|
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
|
|
|
Q_ASSERT(staticMetaObject.cast(_o));
|
|
|
|
pTimer *_t = static_cast<pTimer *>(_o);
|
|
|
|
switch (_id) {
|
|
|
|
case 0: _t->onActivate(); break;
|
|
|
|
default: ;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
Q_UNUSED(_a);
|
|
|
|
}
|
|
|
|
|
|
|
|
const QMetaObjectExtraData phoenix::pTimer::staticMetaObjectExtraData = {
|
|
|
|
0, qt_static_metacall
|
|
|
|
};
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject phoenix::pTimer::staticMetaObject = {
|
|
|
|
{ &QObject::staticMetaObject, qt_meta_stringdata_phoenix__pTimer,
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
qt_meta_data_phoenix__pTimer, &staticMetaObjectExtraData }
|
2011-06-05 03:45:04 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
#ifdef Q_NO_DATA_RELOCATION
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject &phoenix::pTimer::getStaticMetaObject() { return staticMetaObject; }
|
2011-06-05 03:45:04 +00:00
|
|
|
#endif //Q_NO_DATA_RELOCATION
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject *phoenix::pTimer::metaObject() const
|
2011-06-05 03:45:04 +00:00
|
|
|
{
|
|
|
|
return QObject::d_ptr->metaObject ? QObject::d_ptr->metaObject : &staticMetaObject;
|
|
|
|
}
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
void *phoenix::pTimer::qt_metacast(const char *_clname)
|
2011-06-05 03:45:04 +00:00
|
|
|
{
|
|
|
|
if (!_clname) return 0;
|
2013-03-15 13:11:33 +00:00
|
|
|
if (!strcmp(_clname, qt_meta_stringdata_phoenix__pTimer))
|
2011-06-05 03:45:04 +00:00
|
|
|
return static_cast<void*>(const_cast< pTimer*>(this));
|
|
|
|
if (!strcmp(_clname, "pObject"))
|
|
|
|
return static_cast< pObject*>(const_cast< pTimer*>(this));
|
|
|
|
return QObject::qt_metacast(_clname);
|
|
|
|
}
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
int phoenix::pTimer::qt_metacall(QMetaObject::Call _c, int _id, void **_a)
|
2011-06-05 03:45:04 +00:00
|
|
|
{
|
|
|
|
_id = QObject::qt_metacall(_c, _id, _a);
|
|
|
|
if (_id < 0)
|
|
|
|
return _id;
|
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
if (_id < 1)
|
|
|
|
qt_static_metacall(this, _c, _id, _a);
|
2011-06-05 03:45:04 +00:00
|
|
|
_id -= 1;
|
|
|
|
}
|
|
|
|
return _id;
|
|
|
|
}
|
2013-03-15 13:11:33 +00:00
|
|
|
static const uint qt_meta_data_phoenix__pWindow[] = {
|
2010-09-26 05:09:31 +00:00
|
|
|
|
|
|
|
// content:
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
6, // revision
|
2010-09-26 05:09:31 +00:00
|
|
|
0, // classname
|
|
|
|
0, 0, // classinfo
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
0, 0, // methods
|
2010-09-26 05:09:31 +00:00
|
|
|
0, 0, // properties
|
|
|
|
0, 0, // enums/sets
|
|
|
|
0, 0, // constructors
|
|
|
|
0, // flags
|
|
|
|
0, // signalCount
|
|
|
|
|
|
|
|
0 // eod
|
|
|
|
};
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
static const char qt_meta_stringdata_phoenix__pWindow[] = {
|
|
|
|
"phoenix::pWindow\0"
|
2010-09-26 05:09:31 +00:00
|
|
|
};
|
|
|
|
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
void phoenix::pWindow::qt_static_metacall(QObject *_o, QMetaObject::Call _c, int _id, void **_a)
|
|
|
|
{
|
|
|
|
Q_UNUSED(_o);
|
|
|
|
Q_UNUSED(_id);
|
|
|
|
Q_UNUSED(_c);
|
|
|
|
Q_UNUSED(_a);
|
|
|
|
}
|
|
|
|
|
|
|
|
const QMetaObjectExtraData phoenix::pWindow::staticMetaObjectExtraData = {
|
|
|
|
0, qt_static_metacall
|
|
|
|
};
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject phoenix::pWindow::staticMetaObject = {
|
|
|
|
{ &QObject::staticMetaObject, qt_meta_stringdata_phoenix__pWindow,
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
qt_meta_data_phoenix__pWindow, &staticMetaObjectExtraData }
|
2010-09-26 05:09:31 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
#ifdef Q_NO_DATA_RELOCATION
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject &phoenix::pWindow::getStaticMetaObject() { return staticMetaObject; }
|
2010-09-26 05:09:31 +00:00
|
|
|
#endif //Q_NO_DATA_RELOCATION
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject *phoenix::pWindow::metaObject() const
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
|
|
|
return QObject::d_ptr->metaObject ? QObject::d_ptr->metaObject : &staticMetaObject;
|
|
|
|
}
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
void *phoenix::pWindow::qt_metacast(const char *_clname)
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
|
|
|
if (!_clname) return 0;
|
2013-03-15 13:11:33 +00:00
|
|
|
if (!strcmp(_clname, qt_meta_stringdata_phoenix__pWindow))
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
return static_cast<void*>(const_cast< pWindow*>(this));
|
|
|
|
if (!strcmp(_clname, "pObject"))
|
|
|
|
return static_cast< pObject*>(const_cast< pWindow*>(this));
|
|
|
|
return QObject::qt_metacast(_clname);
|
2010-09-26 05:09:31 +00:00
|
|
|
}
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
int phoenix::pWindow::qt_metacall(QMetaObject::Call _c, int _id, void **_a)
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
_id = QObject::qt_metacall(_c, _id, _a);
|
2010-09-26 05:09:31 +00:00
|
|
|
if (_id < 0)
|
|
|
|
return _id;
|
|
|
|
return _id;
|
|
|
|
}
|
2013-03-15 13:11:33 +00:00
|
|
|
static const uint qt_meta_data_phoenix__pItem[] = {
|
2010-09-26 05:09:31 +00:00
|
|
|
|
|
|
|
// content:
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
6, // revision
|
2010-09-26 05:09:31 +00:00
|
|
|
0, // classname
|
|
|
|
0, 0, // classinfo
|
|
|
|
1, 14, // methods
|
|
|
|
0, 0, // properties
|
|
|
|
0, 0, // enums/sets
|
|
|
|
0, 0, // constructors
|
|
|
|
0, // flags
|
|
|
|
0, // signalCount
|
|
|
|
|
|
|
|
// slots: signature, parameters, type, tag, flags
|
2013-03-15 13:11:33 +00:00
|
|
|
16, 15, 15, 15, 0x0a,
|
2010-09-26 05:09:31 +00:00
|
|
|
|
|
|
|
0 // eod
|
|
|
|
};
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
static const char qt_meta_stringdata_phoenix__pItem[] = {
|
|
|
|
"phoenix::pItem\0\0onActivate()\0"
|
2010-09-26 05:09:31 +00:00
|
|
|
};
|
|
|
|
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
void phoenix::pItem::qt_static_metacall(QObject *_o, QMetaObject::Call _c, int _id, void **_a)
|
|
|
|
{
|
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
|
|
|
Q_ASSERT(staticMetaObject.cast(_o));
|
|
|
|
pItem *_t = static_cast<pItem *>(_o);
|
|
|
|
switch (_id) {
|
|
|
|
case 0: _t->onActivate(); break;
|
|
|
|
default: ;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
Q_UNUSED(_a);
|
|
|
|
}
|
|
|
|
|
|
|
|
const QMetaObjectExtraData phoenix::pItem::staticMetaObjectExtraData = {
|
|
|
|
0, qt_static_metacall
|
|
|
|
};
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject phoenix::pItem::staticMetaObject = {
|
|
|
|
{ &QObject::staticMetaObject, qt_meta_stringdata_phoenix__pItem,
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
qt_meta_data_phoenix__pItem, &staticMetaObjectExtraData }
|
2010-09-26 05:09:31 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
#ifdef Q_NO_DATA_RELOCATION
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject &phoenix::pItem::getStaticMetaObject() { return staticMetaObject; }
|
2010-09-26 05:09:31 +00:00
|
|
|
#endif //Q_NO_DATA_RELOCATION
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject *phoenix::pItem::metaObject() const
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
|
|
|
return QObject::d_ptr->metaObject ? QObject::d_ptr->metaObject : &staticMetaObject;
|
|
|
|
}
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
void *phoenix::pItem::qt_metacast(const char *_clname)
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
|
|
|
if (!_clname) return 0;
|
2013-03-15 13:11:33 +00:00
|
|
|
if (!strcmp(_clname, qt_meta_stringdata_phoenix__pItem))
|
2011-02-27 09:05:10 +00:00
|
|
|
return static_cast<void*>(const_cast< pItem*>(this));
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
if (!strcmp(_clname, "pAction"))
|
2011-02-27 09:05:10 +00:00
|
|
|
return static_cast< pAction*>(const_cast< pItem*>(this));
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
return QObject::qt_metacast(_clname);
|
2010-09-26 05:09:31 +00:00
|
|
|
}
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
int phoenix::pItem::qt_metacall(QMetaObject::Call _c, int _id, void **_a)
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
_id = QObject::qt_metacall(_c, _id, _a);
|
2010-09-26 05:09:31 +00:00
|
|
|
if (_id < 0)
|
|
|
|
return _id;
|
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
if (_id < 1)
|
|
|
|
qt_static_metacall(this, _c, _id, _a);
|
2010-09-26 05:09:31 +00:00
|
|
|
_id -= 1;
|
|
|
|
}
|
|
|
|
return _id;
|
|
|
|
}
|
2013-03-15 13:11:33 +00:00
|
|
|
static const uint qt_meta_data_phoenix__pCheckItem[] = {
|
2010-09-26 05:09:31 +00:00
|
|
|
|
|
|
|
// content:
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
6, // revision
|
2010-09-26 05:09:31 +00:00
|
|
|
0, // classname
|
|
|
|
0, 0, // classinfo
|
|
|
|
1, 14, // methods
|
|
|
|
0, 0, // properties
|
|
|
|
0, 0, // enums/sets
|
|
|
|
0, 0, // constructors
|
|
|
|
0, // flags
|
|
|
|
0, // signalCount
|
|
|
|
|
|
|
|
// slots: signature, parameters, type, tag, flags
|
2013-03-15 13:11:33 +00:00
|
|
|
21, 20, 20, 20, 0x0a,
|
2010-09-26 05:09:31 +00:00
|
|
|
|
|
|
|
0 // eod
|
|
|
|
};
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
static const char qt_meta_stringdata_phoenix__pCheckItem[] = {
|
|
|
|
"phoenix::pCheckItem\0\0onToggle()\0"
|
2010-09-26 05:09:31 +00:00
|
|
|
};
|
|
|
|
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
void phoenix::pCheckItem::qt_static_metacall(QObject *_o, QMetaObject::Call _c, int _id, void **_a)
|
|
|
|
{
|
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
|
|
|
Q_ASSERT(staticMetaObject.cast(_o));
|
|
|
|
pCheckItem *_t = static_cast<pCheckItem *>(_o);
|
|
|
|
switch (_id) {
|
|
|
|
case 0: _t->onToggle(); break;
|
|
|
|
default: ;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
Q_UNUSED(_a);
|
|
|
|
}
|
|
|
|
|
|
|
|
const QMetaObjectExtraData phoenix::pCheckItem::staticMetaObjectExtraData = {
|
|
|
|
0, qt_static_metacall
|
|
|
|
};
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject phoenix::pCheckItem::staticMetaObject = {
|
|
|
|
{ &QObject::staticMetaObject, qt_meta_stringdata_phoenix__pCheckItem,
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
qt_meta_data_phoenix__pCheckItem, &staticMetaObjectExtraData }
|
2010-09-26 05:09:31 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
#ifdef Q_NO_DATA_RELOCATION
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject &phoenix::pCheckItem::getStaticMetaObject() { return staticMetaObject; }
|
2010-09-26 05:09:31 +00:00
|
|
|
#endif //Q_NO_DATA_RELOCATION
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject *phoenix::pCheckItem::metaObject() const
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
|
|
|
return QObject::d_ptr->metaObject ? QObject::d_ptr->metaObject : &staticMetaObject;
|
|
|
|
}
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
void *phoenix::pCheckItem::qt_metacast(const char *_clname)
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
|
|
|
if (!_clname) return 0;
|
2013-03-15 13:11:33 +00:00
|
|
|
if (!strcmp(_clname, qt_meta_stringdata_phoenix__pCheckItem))
|
2011-02-27 09:05:10 +00:00
|
|
|
return static_cast<void*>(const_cast< pCheckItem*>(this));
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
if (!strcmp(_clname, "pAction"))
|
2011-02-27 09:05:10 +00:00
|
|
|
return static_cast< pAction*>(const_cast< pCheckItem*>(this));
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
return QObject::qt_metacast(_clname);
|
2010-09-26 05:09:31 +00:00
|
|
|
}
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
int phoenix::pCheckItem::qt_metacall(QMetaObject::Call _c, int _id, void **_a)
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
_id = QObject::qt_metacall(_c, _id, _a);
|
2010-09-26 05:09:31 +00:00
|
|
|
if (_id < 0)
|
|
|
|
return _id;
|
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
if (_id < 1)
|
|
|
|
qt_static_metacall(this, _c, _id, _a);
|
2010-09-26 05:09:31 +00:00
|
|
|
_id -= 1;
|
|
|
|
}
|
|
|
|
return _id;
|
|
|
|
}
|
2013-03-15 13:11:33 +00:00
|
|
|
static const uint qt_meta_data_phoenix__pRadioItem[] = {
|
2010-09-26 05:09:31 +00:00
|
|
|
|
|
|
|
// content:
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
6, // revision
|
2010-09-26 05:09:31 +00:00
|
|
|
0, // classname
|
|
|
|
0, 0, // classinfo
|
|
|
|
1, 14, // methods
|
|
|
|
0, 0, // properties
|
|
|
|
0, 0, // enums/sets
|
|
|
|
0, 0, // constructors
|
|
|
|
0, // flags
|
|
|
|
0, // signalCount
|
|
|
|
|
|
|
|
// slots: signature, parameters, type, tag, flags
|
2013-03-15 13:11:33 +00:00
|
|
|
21, 20, 20, 20, 0x0a,
|
2010-09-26 05:09:31 +00:00
|
|
|
|
|
|
|
0 // eod
|
|
|
|
};
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
static const char qt_meta_stringdata_phoenix__pRadioItem[] = {
|
|
|
|
"phoenix::pRadioItem\0\0onActivate()\0"
|
2010-09-26 05:09:31 +00:00
|
|
|
};
|
|
|
|
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
void phoenix::pRadioItem::qt_static_metacall(QObject *_o, QMetaObject::Call _c, int _id, void **_a)
|
|
|
|
{
|
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
|
|
|
Q_ASSERT(staticMetaObject.cast(_o));
|
|
|
|
pRadioItem *_t = static_cast<pRadioItem *>(_o);
|
|
|
|
switch (_id) {
|
|
|
|
case 0: _t->onActivate(); break;
|
|
|
|
default: ;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
Q_UNUSED(_a);
|
|
|
|
}
|
|
|
|
|
|
|
|
const QMetaObjectExtraData phoenix::pRadioItem::staticMetaObjectExtraData = {
|
|
|
|
0, qt_static_metacall
|
|
|
|
};
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject phoenix::pRadioItem::staticMetaObject = {
|
|
|
|
{ &QObject::staticMetaObject, qt_meta_stringdata_phoenix__pRadioItem,
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
qt_meta_data_phoenix__pRadioItem, &staticMetaObjectExtraData }
|
2010-09-26 05:09:31 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
#ifdef Q_NO_DATA_RELOCATION
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject &phoenix::pRadioItem::getStaticMetaObject() { return staticMetaObject; }
|
2010-09-26 05:09:31 +00:00
|
|
|
#endif //Q_NO_DATA_RELOCATION
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject *phoenix::pRadioItem::metaObject() const
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
|
|
|
return QObject::d_ptr->metaObject ? QObject::d_ptr->metaObject : &staticMetaObject;
|
|
|
|
}
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
void *phoenix::pRadioItem::qt_metacast(const char *_clname)
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
|
|
|
if (!_clname) return 0;
|
2013-03-15 13:11:33 +00:00
|
|
|
if (!strcmp(_clname, qt_meta_stringdata_phoenix__pRadioItem))
|
2011-02-27 09:05:10 +00:00
|
|
|
return static_cast<void*>(const_cast< pRadioItem*>(this));
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
if (!strcmp(_clname, "pAction"))
|
2011-02-27 09:05:10 +00:00
|
|
|
return static_cast< pAction*>(const_cast< pRadioItem*>(this));
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
return QObject::qt_metacast(_clname);
|
2010-09-26 05:09:31 +00:00
|
|
|
}
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
int phoenix::pRadioItem::qt_metacall(QMetaObject::Call _c, int _id, void **_a)
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
_id = QObject::qt_metacall(_c, _id, _a);
|
2010-09-26 05:09:31 +00:00
|
|
|
if (_id < 0)
|
|
|
|
return _id;
|
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
if (_id < 1)
|
|
|
|
qt_static_metacall(this, _c, _id, _a);
|
2010-09-26 05:09:31 +00:00
|
|
|
_id -= 1;
|
|
|
|
}
|
|
|
|
return _id;
|
|
|
|
}
|
2013-03-15 13:11:33 +00:00
|
|
|
static const uint qt_meta_data_phoenix__pButton[] = {
|
2010-09-26 05:09:31 +00:00
|
|
|
|
|
|
|
// content:
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
6, // revision
|
2010-09-26 05:09:31 +00:00
|
|
|
0, // classname
|
|
|
|
0, 0, // classinfo
|
|
|
|
1, 14, // methods
|
|
|
|
0, 0, // properties
|
|
|
|
0, 0, // enums/sets
|
|
|
|
0, 0, // constructors
|
|
|
|
0, // flags
|
|
|
|
0, // signalCount
|
|
|
|
|
|
|
|
// slots: signature, parameters, type, tag, flags
|
2013-03-15 13:11:33 +00:00
|
|
|
18, 17, 17, 17, 0x0a,
|
2010-09-26 05:09:31 +00:00
|
|
|
|
|
|
|
0 // eod
|
|
|
|
};
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
static const char qt_meta_stringdata_phoenix__pButton[] = {
|
|
|
|
"phoenix::pButton\0\0onActivate()\0"
|
2010-09-26 05:09:31 +00:00
|
|
|
};
|
|
|
|
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
void phoenix::pButton::qt_static_metacall(QObject *_o, QMetaObject::Call _c, int _id, void **_a)
|
|
|
|
{
|
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
|
|
|
Q_ASSERT(staticMetaObject.cast(_o));
|
|
|
|
pButton *_t = static_cast<pButton *>(_o);
|
|
|
|
switch (_id) {
|
|
|
|
case 0: _t->onActivate(); break;
|
|
|
|
default: ;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
Q_UNUSED(_a);
|
|
|
|
}
|
|
|
|
|
|
|
|
const QMetaObjectExtraData phoenix::pButton::staticMetaObjectExtraData = {
|
|
|
|
0, qt_static_metacall
|
|
|
|
};
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject phoenix::pButton::staticMetaObject = {
|
|
|
|
{ &QObject::staticMetaObject, qt_meta_stringdata_phoenix__pButton,
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
qt_meta_data_phoenix__pButton, &staticMetaObjectExtraData }
|
2010-09-26 05:09:31 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
#ifdef Q_NO_DATA_RELOCATION
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject &phoenix::pButton::getStaticMetaObject() { return staticMetaObject; }
|
2010-09-26 05:09:31 +00:00
|
|
|
#endif //Q_NO_DATA_RELOCATION
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject *phoenix::pButton::metaObject() const
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
|
|
|
return QObject::d_ptr->metaObject ? QObject::d_ptr->metaObject : &staticMetaObject;
|
|
|
|
}
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
void *phoenix::pButton::qt_metacast(const char *_clname)
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
|
|
|
if (!_clname) return 0;
|
2013-03-15 13:11:33 +00:00
|
|
|
if (!strcmp(_clname, qt_meta_stringdata_phoenix__pButton))
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
return static_cast<void*>(const_cast< pButton*>(this));
|
|
|
|
if (!strcmp(_clname, "pWidget"))
|
|
|
|
return static_cast< pWidget*>(const_cast< pButton*>(this));
|
|
|
|
return QObject::qt_metacast(_clname);
|
2010-09-26 05:09:31 +00:00
|
|
|
}
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
int phoenix::pButton::qt_metacall(QMetaObject::Call _c, int _id, void **_a)
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
_id = QObject::qt_metacall(_c, _id, _a);
|
2010-09-26 05:09:31 +00:00
|
|
|
if (_id < 0)
|
|
|
|
return _id;
|
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
if (_id < 1)
|
|
|
|
qt_static_metacall(this, _c, _id, _a);
|
2010-09-26 05:09:31 +00:00
|
|
|
_id -= 1;
|
|
|
|
}
|
|
|
|
return _id;
|
|
|
|
}
|
2013-03-15 13:11:33 +00:00
|
|
|
static const uint qt_meta_data_phoenix__pCanvas[] = {
|
2011-03-26 11:31:07 +00:00
|
|
|
|
|
|
|
// content:
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
6, // revision
|
2011-03-26 11:31:07 +00:00
|
|
|
0, // classname
|
|
|
|
0, 0, // classinfo
|
|
|
|
0, 0, // methods
|
|
|
|
0, 0, // properties
|
|
|
|
0, 0, // enums/sets
|
|
|
|
0, 0, // constructors
|
|
|
|
0, // flags
|
|
|
|
0, // signalCount
|
|
|
|
|
|
|
|
0 // eod
|
|
|
|
};
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
static const char qt_meta_stringdata_phoenix__pCanvas[] = {
|
|
|
|
"phoenix::pCanvas\0"
|
2011-03-26 11:31:07 +00:00
|
|
|
};
|
|
|
|
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
void phoenix::pCanvas::qt_static_metacall(QObject *_o, QMetaObject::Call _c, int _id, void **_a)
|
|
|
|
{
|
|
|
|
Q_UNUSED(_o);
|
|
|
|
Q_UNUSED(_id);
|
|
|
|
Q_UNUSED(_c);
|
|
|
|
Q_UNUSED(_a);
|
|
|
|
}
|
|
|
|
|
|
|
|
const QMetaObjectExtraData phoenix::pCanvas::staticMetaObjectExtraData = {
|
|
|
|
0, qt_static_metacall
|
|
|
|
};
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject phoenix::pCanvas::staticMetaObject = {
|
|
|
|
{ &QObject::staticMetaObject, qt_meta_stringdata_phoenix__pCanvas,
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
qt_meta_data_phoenix__pCanvas, &staticMetaObjectExtraData }
|
2011-03-26 11:31:07 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
#ifdef Q_NO_DATA_RELOCATION
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject &phoenix::pCanvas::getStaticMetaObject() { return staticMetaObject; }
|
2011-03-26 11:31:07 +00:00
|
|
|
#endif //Q_NO_DATA_RELOCATION
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject *phoenix::pCanvas::metaObject() const
|
2011-03-26 11:31:07 +00:00
|
|
|
{
|
|
|
|
return QObject::d_ptr->metaObject ? QObject::d_ptr->metaObject : &staticMetaObject;
|
|
|
|
}
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
void *phoenix::pCanvas::qt_metacast(const char *_clname)
|
2011-03-26 11:31:07 +00:00
|
|
|
{
|
|
|
|
if (!_clname) return 0;
|
2013-03-15 13:11:33 +00:00
|
|
|
if (!strcmp(_clname, qt_meta_stringdata_phoenix__pCanvas))
|
2011-03-26 11:31:07 +00:00
|
|
|
return static_cast<void*>(const_cast< pCanvas*>(this));
|
|
|
|
if (!strcmp(_clname, "pWidget"))
|
|
|
|
return static_cast< pWidget*>(const_cast< pCanvas*>(this));
|
|
|
|
return QObject::qt_metacast(_clname);
|
|
|
|
}
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
int phoenix::pCanvas::qt_metacall(QMetaObject::Call _c, int _id, void **_a)
|
2011-03-26 11:31:07 +00:00
|
|
|
{
|
|
|
|
_id = QObject::qt_metacall(_c, _id, _a);
|
|
|
|
if (_id < 0)
|
|
|
|
return _id;
|
|
|
|
return _id;
|
|
|
|
}
|
2013-03-15 13:11:33 +00:00
|
|
|
static const uint qt_meta_data_phoenix__pCheckButton[] = {
|
2010-09-26 05:09:31 +00:00
|
|
|
|
|
|
|
// content:
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
6, // revision
|
2010-09-26 05:09:31 +00:00
|
|
|
0, // classname
|
|
|
|
0, 0, // classinfo
|
|
|
|
1, 14, // methods
|
|
|
|
0, 0, // properties
|
|
|
|
0, 0, // enums/sets
|
|
|
|
0, 0, // constructors
|
|
|
|
0, // flags
|
|
|
|
0, // signalCount
|
|
|
|
|
|
|
|
// slots: signature, parameters, type, tag, flags
|
2013-11-28 10:29:01 +00:00
|
|
|
31, 23, 22, 22, 0x0a,
|
2010-09-26 05:09:31 +00:00
|
|
|
|
|
|
|
0 // eod
|
|
|
|
};
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
static const char qt_meta_stringdata_phoenix__pCheckButton[] = {
|
2013-11-28 10:29:01 +00:00
|
|
|
"phoenix::pCheckButton\0\0checked\0"
|
|
|
|
"onToggle(bool)\0"
|
2010-09-26 05:09:31 +00:00
|
|
|
};
|
|
|
|
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
void phoenix::pCheckButton::qt_static_metacall(QObject *_o, QMetaObject::Call _c, int _id, void **_a)
|
|
|
|
{
|
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
|
|
|
Q_ASSERT(staticMetaObject.cast(_o));
|
|
|
|
pCheckButton *_t = static_cast<pCheckButton *>(_o);
|
|
|
|
switch (_id) {
|
2013-11-28 10:29:01 +00:00
|
|
|
case 0: _t->onToggle((*reinterpret_cast< bool(*)>(_a[1]))); break;
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
default: ;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
const QMetaObjectExtraData phoenix::pCheckButton::staticMetaObjectExtraData = {
|
|
|
|
0, qt_static_metacall
|
|
|
|
};
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject phoenix::pCheckButton::staticMetaObject = {
|
|
|
|
{ &QObject::staticMetaObject, qt_meta_stringdata_phoenix__pCheckButton,
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
qt_meta_data_phoenix__pCheckButton, &staticMetaObjectExtraData }
|
2010-09-26 05:09:31 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
#ifdef Q_NO_DATA_RELOCATION
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject &phoenix::pCheckButton::getStaticMetaObject() { return staticMetaObject; }
|
2010-09-26 05:09:31 +00:00
|
|
|
#endif //Q_NO_DATA_RELOCATION
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject *phoenix::pCheckButton::metaObject() const
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
|
|
|
return QObject::d_ptr->metaObject ? QObject::d_ptr->metaObject : &staticMetaObject;
|
|
|
|
}
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
void *phoenix::pCheckButton::qt_metacast(const char *_clname)
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
|
|
|
if (!_clname) return 0;
|
2013-03-15 13:11:33 +00:00
|
|
|
if (!strcmp(_clname, qt_meta_stringdata_phoenix__pCheckButton))
|
|
|
|
return static_cast<void*>(const_cast< pCheckButton*>(this));
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
if (!strcmp(_clname, "pWidget"))
|
2013-03-15 13:11:33 +00:00
|
|
|
return static_cast< pWidget*>(const_cast< pCheckButton*>(this));
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
return QObject::qt_metacast(_clname);
|
2010-09-26 05:09:31 +00:00
|
|
|
}
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
int phoenix::pCheckButton::qt_metacall(QMetaObject::Call _c, int _id, void **_a)
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
_id = QObject::qt_metacall(_c, _id, _a);
|
2010-09-26 05:09:31 +00:00
|
|
|
if (_id < 0)
|
|
|
|
return _id;
|
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
if (_id < 1)
|
|
|
|
qt_static_metacall(this, _c, _id, _a);
|
2010-09-26 05:09:31 +00:00
|
|
|
_id -= 1;
|
|
|
|
}
|
|
|
|
return _id;
|
|
|
|
}
|
2013-11-28 10:29:01 +00:00
|
|
|
static const uint qt_meta_data_phoenix__pCheckLabel[] = {
|
|
|
|
|
|
|
|
// content:
|
|
|
|
6, // revision
|
|
|
|
0, // classname
|
|
|
|
0, 0, // classinfo
|
|
|
|
1, 14, // methods
|
|
|
|
0, 0, // properties
|
|
|
|
0, 0, // enums/sets
|
|
|
|
0, 0, // constructors
|
|
|
|
0, // flags
|
|
|
|
0, // signalCount
|
|
|
|
|
|
|
|
// slots: signature, parameters, type, tag, flags
|
|
|
|
22, 21, 21, 21, 0x0a,
|
|
|
|
|
|
|
|
0 // eod
|
|
|
|
};
|
|
|
|
|
|
|
|
static const char qt_meta_stringdata_phoenix__pCheckLabel[] = {
|
|
|
|
"phoenix::pCheckLabel\0\0onToggle()\0"
|
|
|
|
};
|
|
|
|
|
|
|
|
void phoenix::pCheckLabel::qt_static_metacall(QObject *_o, QMetaObject::Call _c, int _id, void **_a)
|
|
|
|
{
|
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
|
|
|
Q_ASSERT(staticMetaObject.cast(_o));
|
|
|
|
pCheckLabel *_t = static_cast<pCheckLabel *>(_o);
|
|
|
|
switch (_id) {
|
|
|
|
case 0: _t->onToggle(); break;
|
|
|
|
default: ;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
Q_UNUSED(_a);
|
|
|
|
}
|
|
|
|
|
|
|
|
const QMetaObjectExtraData phoenix::pCheckLabel::staticMetaObjectExtraData = {
|
|
|
|
0, qt_static_metacall
|
|
|
|
};
|
|
|
|
|
|
|
|
const QMetaObject phoenix::pCheckLabel::staticMetaObject = {
|
|
|
|
{ &QObject::staticMetaObject, qt_meta_stringdata_phoenix__pCheckLabel,
|
|
|
|
qt_meta_data_phoenix__pCheckLabel, &staticMetaObjectExtraData }
|
|
|
|
};
|
|
|
|
|
|
|
|
#ifdef Q_NO_DATA_RELOCATION
|
|
|
|
const QMetaObject &phoenix::pCheckLabel::getStaticMetaObject() { return staticMetaObject; }
|
|
|
|
#endif //Q_NO_DATA_RELOCATION
|
|
|
|
|
|
|
|
const QMetaObject *phoenix::pCheckLabel::metaObject() const
|
|
|
|
{
|
|
|
|
return QObject::d_ptr->metaObject ? QObject::d_ptr->metaObject : &staticMetaObject;
|
|
|
|
}
|
|
|
|
|
|
|
|
void *phoenix::pCheckLabel::qt_metacast(const char *_clname)
|
|
|
|
{
|
|
|
|
if (!_clname) return 0;
|
|
|
|
if (!strcmp(_clname, qt_meta_stringdata_phoenix__pCheckLabel))
|
|
|
|
return static_cast<void*>(const_cast< pCheckLabel*>(this));
|
|
|
|
if (!strcmp(_clname, "pWidget"))
|
|
|
|
return static_cast< pWidget*>(const_cast< pCheckLabel*>(this));
|
|
|
|
return QObject::qt_metacast(_clname);
|
|
|
|
}
|
|
|
|
|
|
|
|
int phoenix::pCheckLabel::qt_metacall(QMetaObject::Call _c, int _id, void **_a)
|
|
|
|
{
|
|
|
|
_id = QObject::qt_metacall(_c, _id, _a);
|
|
|
|
if (_id < 0)
|
|
|
|
return _id;
|
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
|
|
|
if (_id < 1)
|
|
|
|
qt_static_metacall(this, _c, _id, _a);
|
|
|
|
_id -= 1;
|
|
|
|
}
|
|
|
|
return _id;
|
|
|
|
}
|
2013-03-15 13:11:33 +00:00
|
|
|
static const uint qt_meta_data_phoenix__pComboButton[] = {
|
2010-09-26 05:09:31 +00:00
|
|
|
|
|
|
|
// content:
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
6, // revision
|
2010-09-26 05:09:31 +00:00
|
|
|
0, // classname
|
|
|
|
0, 0, // classinfo
|
|
|
|
1, 14, // methods
|
|
|
|
0, 0, // properties
|
|
|
|
0, 0, // enums/sets
|
|
|
|
0, 0, // constructors
|
|
|
|
0, // flags
|
|
|
|
0, // signalCount
|
|
|
|
|
|
|
|
// slots: signature, parameters, type, tag, flags
|
2013-03-15 13:11:33 +00:00
|
|
|
23, 22, 22, 22, 0x0a,
|
2010-09-26 05:09:31 +00:00
|
|
|
|
|
|
|
0 // eod
|
|
|
|
};
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
static const char qt_meta_stringdata_phoenix__pComboButton[] = {
|
|
|
|
"phoenix::pComboButton\0\0onChange()\0"
|
2010-09-26 05:09:31 +00:00
|
|
|
};
|
|
|
|
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
void phoenix::pComboButton::qt_static_metacall(QObject *_o, QMetaObject::Call _c, int _id, void **_a)
|
|
|
|
{
|
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
|
|
|
Q_ASSERT(staticMetaObject.cast(_o));
|
|
|
|
pComboButton *_t = static_cast<pComboButton *>(_o);
|
|
|
|
switch (_id) {
|
|
|
|
case 0: _t->onChange(); break;
|
|
|
|
default: ;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
Q_UNUSED(_a);
|
|
|
|
}
|
|
|
|
|
|
|
|
const QMetaObjectExtraData phoenix::pComboButton::staticMetaObjectExtraData = {
|
|
|
|
0, qt_static_metacall
|
|
|
|
};
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject phoenix::pComboButton::staticMetaObject = {
|
|
|
|
{ &QObject::staticMetaObject, qt_meta_stringdata_phoenix__pComboButton,
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
qt_meta_data_phoenix__pComboButton, &staticMetaObjectExtraData }
|
2010-09-26 05:09:31 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
#ifdef Q_NO_DATA_RELOCATION
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject &phoenix::pComboButton::getStaticMetaObject() { return staticMetaObject; }
|
2010-09-26 05:09:31 +00:00
|
|
|
#endif //Q_NO_DATA_RELOCATION
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject *phoenix::pComboButton::metaObject() const
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
|
|
|
return QObject::d_ptr->metaObject ? QObject::d_ptr->metaObject : &staticMetaObject;
|
|
|
|
}
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
void *phoenix::pComboButton::qt_metacast(const char *_clname)
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
|
|
|
if (!_clname) return 0;
|
2013-03-15 13:11:33 +00:00
|
|
|
if (!strcmp(_clname, qt_meta_stringdata_phoenix__pComboButton))
|
|
|
|
return static_cast<void*>(const_cast< pComboButton*>(this));
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
if (!strcmp(_clname, "pWidget"))
|
2013-03-15 13:11:33 +00:00
|
|
|
return static_cast< pWidget*>(const_cast< pComboButton*>(this));
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
return QObject::qt_metacast(_clname);
|
2010-09-26 05:09:31 +00:00
|
|
|
}
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
int phoenix::pComboButton::qt_metacall(QMetaObject::Call _c, int _id, void **_a)
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
_id = QObject::qt_metacall(_c, _id, _a);
|
2010-09-26 05:09:31 +00:00
|
|
|
if (_id < 0)
|
|
|
|
return _id;
|
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
if (_id < 1)
|
|
|
|
qt_static_metacall(this, _c, _id, _a);
|
2010-09-26 05:09:31 +00:00
|
|
|
_id -= 1;
|
|
|
|
}
|
|
|
|
return _id;
|
|
|
|
}
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
static const uint qt_meta_data_phoenix__pConsole[] = {
|
|
|
|
|
|
|
|
// content:
|
|
|
|
6, // revision
|
|
|
|
0, // classname
|
|
|
|
0, 0, // classinfo
|
|
|
|
0, 0, // methods
|
|
|
|
0, 0, // properties
|
|
|
|
0, 0, // enums/sets
|
|
|
|
0, 0, // constructors
|
|
|
|
0, // flags
|
|
|
|
0, // signalCount
|
|
|
|
|
|
|
|
0 // eod
|
|
|
|
};
|
|
|
|
|
|
|
|
static const char qt_meta_stringdata_phoenix__pConsole[] = {
|
|
|
|
"phoenix::pConsole\0"
|
|
|
|
};
|
|
|
|
|
|
|
|
void phoenix::pConsole::qt_static_metacall(QObject *_o, QMetaObject::Call _c, int _id, void **_a)
|
|
|
|
{
|
|
|
|
Q_UNUSED(_o);
|
|
|
|
Q_UNUSED(_id);
|
|
|
|
Q_UNUSED(_c);
|
|
|
|
Q_UNUSED(_a);
|
|
|
|
}
|
|
|
|
|
|
|
|
const QMetaObjectExtraData phoenix::pConsole::staticMetaObjectExtraData = {
|
|
|
|
0, qt_static_metacall
|
|
|
|
};
|
|
|
|
|
|
|
|
const QMetaObject phoenix::pConsole::staticMetaObject = {
|
|
|
|
{ &QObject::staticMetaObject, qt_meta_stringdata_phoenix__pConsole,
|
|
|
|
qt_meta_data_phoenix__pConsole, &staticMetaObjectExtraData }
|
|
|
|
};
|
|
|
|
|
|
|
|
#ifdef Q_NO_DATA_RELOCATION
|
|
|
|
const QMetaObject &phoenix::pConsole::getStaticMetaObject() { return staticMetaObject; }
|
|
|
|
#endif //Q_NO_DATA_RELOCATION
|
|
|
|
|
|
|
|
const QMetaObject *phoenix::pConsole::metaObject() const
|
|
|
|
{
|
|
|
|
return QObject::d_ptr->metaObject ? QObject::d_ptr->metaObject : &staticMetaObject;
|
|
|
|
}
|
|
|
|
|
|
|
|
void *phoenix::pConsole::qt_metacast(const char *_clname)
|
|
|
|
{
|
|
|
|
if (!_clname) return 0;
|
|
|
|
if (!strcmp(_clname, qt_meta_stringdata_phoenix__pConsole))
|
|
|
|
return static_cast<void*>(const_cast< pConsole*>(this));
|
|
|
|
if (!strcmp(_clname, "pWidget"))
|
|
|
|
return static_cast< pWidget*>(const_cast< pConsole*>(this));
|
|
|
|
return QObject::qt_metacast(_clname);
|
|
|
|
}
|
|
|
|
|
|
|
|
int phoenix::pConsole::qt_metacall(QMetaObject::Call _c, int _id, void **_a)
|
|
|
|
{
|
|
|
|
_id = QObject::qt_metacall(_c, _id, _a);
|
|
|
|
if (_id < 0)
|
|
|
|
return _id;
|
|
|
|
return _id;
|
|
|
|
}
|
2013-11-28 10:29:01 +00:00
|
|
|
static const uint qt_meta_data_phoenix__pFrame[] = {
|
|
|
|
|
|
|
|
// content:
|
|
|
|
6, // revision
|
|
|
|
0, // classname
|
|
|
|
0, 0, // classinfo
|
|
|
|
0, 0, // methods
|
|
|
|
0, 0, // properties
|
|
|
|
0, 0, // enums/sets
|
|
|
|
0, 0, // constructors
|
|
|
|
0, // flags
|
|
|
|
0, // signalCount
|
|
|
|
|
|
|
|
0 // eod
|
|
|
|
};
|
|
|
|
|
|
|
|
static const char qt_meta_stringdata_phoenix__pFrame[] = {
|
|
|
|
"phoenix::pFrame\0"
|
|
|
|
};
|
|
|
|
|
|
|
|
void phoenix::pFrame::qt_static_metacall(QObject *_o, QMetaObject::Call _c, int _id, void **_a)
|
|
|
|
{
|
|
|
|
Q_UNUSED(_o);
|
|
|
|
Q_UNUSED(_id);
|
|
|
|
Q_UNUSED(_c);
|
|
|
|
Q_UNUSED(_a);
|
|
|
|
}
|
|
|
|
|
|
|
|
const QMetaObjectExtraData phoenix::pFrame::staticMetaObjectExtraData = {
|
|
|
|
0, qt_static_metacall
|
|
|
|
};
|
|
|
|
|
|
|
|
const QMetaObject phoenix::pFrame::staticMetaObject = {
|
|
|
|
{ &QObject::staticMetaObject, qt_meta_stringdata_phoenix__pFrame,
|
|
|
|
qt_meta_data_phoenix__pFrame, &staticMetaObjectExtraData }
|
|
|
|
};
|
|
|
|
|
|
|
|
#ifdef Q_NO_DATA_RELOCATION
|
|
|
|
const QMetaObject &phoenix::pFrame::getStaticMetaObject() { return staticMetaObject; }
|
|
|
|
#endif //Q_NO_DATA_RELOCATION
|
|
|
|
|
|
|
|
const QMetaObject *phoenix::pFrame::metaObject() const
|
|
|
|
{
|
|
|
|
return QObject::d_ptr->metaObject ? QObject::d_ptr->metaObject : &staticMetaObject;
|
|
|
|
}
|
|
|
|
|
|
|
|
void *phoenix::pFrame::qt_metacast(const char *_clname)
|
|
|
|
{
|
|
|
|
if (!_clname) return 0;
|
|
|
|
if (!strcmp(_clname, qt_meta_stringdata_phoenix__pFrame))
|
|
|
|
return static_cast<void*>(const_cast< pFrame*>(this));
|
|
|
|
if (!strcmp(_clname, "pWidget"))
|
|
|
|
return static_cast< pWidget*>(const_cast< pFrame*>(this));
|
|
|
|
return QObject::qt_metacast(_clname);
|
|
|
|
}
|
|
|
|
|
|
|
|
int phoenix::pFrame::qt_metacall(QMetaObject::Call _c, int _id, void **_a)
|
|
|
|
{
|
|
|
|
_id = QObject::qt_metacall(_c, _id, _a);
|
|
|
|
if (_id < 0)
|
|
|
|
return _id;
|
|
|
|
return _id;
|
|
|
|
}
|
2013-03-15 13:11:33 +00:00
|
|
|
static const uint qt_meta_data_phoenix__pHexEdit[] = {
|
Update to v075r03 release.
byuu says:
Changelog:
- added full HexEditor widget to phoenix/Qt (has dynamic scrollbar like
phoenix/GTK, but does not yet support page up/down scrolling)
- optimized debugger to look great with either phoenix/GTK or phoenix/Qt
- fixed phoenix/Qt fullscreen mode (had to allow resizing of the layout,
and resize the container)
- fixed phoenix/Qt Window::setBackgroundColor() bug that was making
statusbar invisible
- entering fullscreen now captures mouse, leaving fullscreen releases it
- so by default, no cursor in fullscreen mode now
- F12 key was assigned the task of toggling mouse capture,
Tools->Capture Mouse was removed
- above change allows toggling mouse capture in fullscreen if you like
It wasn't my idea, but toggling the mouse capture in fullscreen also hiding the mouse cursor is what I call genius design. Two birds with one stone, and very intuitive.
Also, the default GUI on Linux for bsnes and bgameboy is now Qt, instead
of GTK+. I did this because Qt's fullscreen is far more stable, and
I fixed up the remaining bugs anyway.
2011-02-02 10:35:15 +00:00
|
|
|
|
|
|
|
// content:
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
6, // revision
|
Update to v075r03 release.
byuu says:
Changelog:
- added full HexEditor widget to phoenix/Qt (has dynamic scrollbar like
phoenix/GTK, but does not yet support page up/down scrolling)
- optimized debugger to look great with either phoenix/GTK or phoenix/Qt
- fixed phoenix/Qt fullscreen mode (had to allow resizing of the layout,
and resize the container)
- fixed phoenix/Qt Window::setBackgroundColor() bug that was making
statusbar invisible
- entering fullscreen now captures mouse, leaving fullscreen releases it
- so by default, no cursor in fullscreen mode now
- F12 key was assigned the task of toggling mouse capture,
Tools->Capture Mouse was removed
- above change allows toggling mouse capture in fullscreen if you like
It wasn't my idea, but toggling the mouse capture in fullscreen also hiding the mouse cursor is what I call genius design. Two birds with one stone, and very intuitive.
Also, the default GUI on Linux for bsnes and bgameboy is now Qt, instead
of GTK+. I did this because Qt's fullscreen is far more stable, and
I fixed up the remaining bugs anyway.
2011-02-02 10:35:15 +00:00
|
|
|
0, // classname
|
|
|
|
0, 0, // classinfo
|
|
|
|
1, 14, // methods
|
|
|
|
0, 0, // properties
|
|
|
|
0, 0, // enums/sets
|
|
|
|
0, 0, // constructors
|
|
|
|
0, // flags
|
|
|
|
0, // signalCount
|
|
|
|
|
|
|
|
// slots: signature, parameters, type, tag, flags
|
2013-03-15 13:11:33 +00:00
|
|
|
19, 18, 18, 18, 0x0a,
|
Update to v075r03 release.
byuu says:
Changelog:
- added full HexEditor widget to phoenix/Qt (has dynamic scrollbar like
phoenix/GTK, but does not yet support page up/down scrolling)
- optimized debugger to look great with either phoenix/GTK or phoenix/Qt
- fixed phoenix/Qt fullscreen mode (had to allow resizing of the layout,
and resize the container)
- fixed phoenix/Qt Window::setBackgroundColor() bug that was making
statusbar invisible
- entering fullscreen now captures mouse, leaving fullscreen releases it
- so by default, no cursor in fullscreen mode now
- F12 key was assigned the task of toggling mouse capture,
Tools->Capture Mouse was removed
- above change allows toggling mouse capture in fullscreen if you like
It wasn't my idea, but toggling the mouse capture in fullscreen also hiding the mouse cursor is what I call genius design. Two birds with one stone, and very intuitive.
Also, the default GUI on Linux for bsnes and bgameboy is now Qt, instead
of GTK+. I did this because Qt's fullscreen is far more stable, and
I fixed up the remaining bugs anyway.
2011-02-02 10:35:15 +00:00
|
|
|
|
|
|
|
0 // eod
|
|
|
|
};
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
static const char qt_meta_stringdata_phoenix__pHexEdit[] = {
|
|
|
|
"phoenix::pHexEdit\0\0onScroll()\0"
|
Update to v075r03 release.
byuu says:
Changelog:
- added full HexEditor widget to phoenix/Qt (has dynamic scrollbar like
phoenix/GTK, but does not yet support page up/down scrolling)
- optimized debugger to look great with either phoenix/GTK or phoenix/Qt
- fixed phoenix/Qt fullscreen mode (had to allow resizing of the layout,
and resize the container)
- fixed phoenix/Qt Window::setBackgroundColor() bug that was making
statusbar invisible
- entering fullscreen now captures mouse, leaving fullscreen releases it
- so by default, no cursor in fullscreen mode now
- F12 key was assigned the task of toggling mouse capture,
Tools->Capture Mouse was removed
- above change allows toggling mouse capture in fullscreen if you like
It wasn't my idea, but toggling the mouse capture in fullscreen also hiding the mouse cursor is what I call genius design. Two birds with one stone, and very intuitive.
Also, the default GUI on Linux for bsnes and bgameboy is now Qt, instead
of GTK+. I did this because Qt's fullscreen is far more stable, and
I fixed up the remaining bugs anyway.
2011-02-02 10:35:15 +00:00
|
|
|
};
|
|
|
|
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
void phoenix::pHexEdit::qt_static_metacall(QObject *_o, QMetaObject::Call _c, int _id, void **_a)
|
|
|
|
{
|
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
|
|
|
Q_ASSERT(staticMetaObject.cast(_o));
|
|
|
|
pHexEdit *_t = static_cast<pHexEdit *>(_o);
|
|
|
|
switch (_id) {
|
|
|
|
case 0: _t->onScroll(); break;
|
|
|
|
default: ;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
Q_UNUSED(_a);
|
|
|
|
}
|
|
|
|
|
|
|
|
const QMetaObjectExtraData phoenix::pHexEdit::staticMetaObjectExtraData = {
|
|
|
|
0, qt_static_metacall
|
|
|
|
};
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject phoenix::pHexEdit::staticMetaObject = {
|
|
|
|
{ &QObject::staticMetaObject, qt_meta_stringdata_phoenix__pHexEdit,
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
qt_meta_data_phoenix__pHexEdit, &staticMetaObjectExtraData }
|
Update to v075r03 release.
byuu says:
Changelog:
- added full HexEditor widget to phoenix/Qt (has dynamic scrollbar like
phoenix/GTK, but does not yet support page up/down scrolling)
- optimized debugger to look great with either phoenix/GTK or phoenix/Qt
- fixed phoenix/Qt fullscreen mode (had to allow resizing of the layout,
and resize the container)
- fixed phoenix/Qt Window::setBackgroundColor() bug that was making
statusbar invisible
- entering fullscreen now captures mouse, leaving fullscreen releases it
- so by default, no cursor in fullscreen mode now
- F12 key was assigned the task of toggling mouse capture,
Tools->Capture Mouse was removed
- above change allows toggling mouse capture in fullscreen if you like
It wasn't my idea, but toggling the mouse capture in fullscreen also hiding the mouse cursor is what I call genius design. Two birds with one stone, and very intuitive.
Also, the default GUI on Linux for bsnes and bgameboy is now Qt, instead
of GTK+. I did this because Qt's fullscreen is far more stable, and
I fixed up the remaining bugs anyway.
2011-02-02 10:35:15 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
#ifdef Q_NO_DATA_RELOCATION
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject &phoenix::pHexEdit::getStaticMetaObject() { return staticMetaObject; }
|
Update to v075r03 release.
byuu says:
Changelog:
- added full HexEditor widget to phoenix/Qt (has dynamic scrollbar like
phoenix/GTK, but does not yet support page up/down scrolling)
- optimized debugger to look great with either phoenix/GTK or phoenix/Qt
- fixed phoenix/Qt fullscreen mode (had to allow resizing of the layout,
and resize the container)
- fixed phoenix/Qt Window::setBackgroundColor() bug that was making
statusbar invisible
- entering fullscreen now captures mouse, leaving fullscreen releases it
- so by default, no cursor in fullscreen mode now
- F12 key was assigned the task of toggling mouse capture,
Tools->Capture Mouse was removed
- above change allows toggling mouse capture in fullscreen if you like
It wasn't my idea, but toggling the mouse capture in fullscreen also hiding the mouse cursor is what I call genius design. Two birds with one stone, and very intuitive.
Also, the default GUI on Linux for bsnes and bgameboy is now Qt, instead
of GTK+. I did this because Qt's fullscreen is far more stable, and
I fixed up the remaining bugs anyway.
2011-02-02 10:35:15 +00:00
|
|
|
#endif //Q_NO_DATA_RELOCATION
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject *phoenix::pHexEdit::metaObject() const
|
Update to v075r03 release.
byuu says:
Changelog:
- added full HexEditor widget to phoenix/Qt (has dynamic scrollbar like
phoenix/GTK, but does not yet support page up/down scrolling)
- optimized debugger to look great with either phoenix/GTK or phoenix/Qt
- fixed phoenix/Qt fullscreen mode (had to allow resizing of the layout,
and resize the container)
- fixed phoenix/Qt Window::setBackgroundColor() bug that was making
statusbar invisible
- entering fullscreen now captures mouse, leaving fullscreen releases it
- so by default, no cursor in fullscreen mode now
- F12 key was assigned the task of toggling mouse capture,
Tools->Capture Mouse was removed
- above change allows toggling mouse capture in fullscreen if you like
It wasn't my idea, but toggling the mouse capture in fullscreen also hiding the mouse cursor is what I call genius design. Two birds with one stone, and very intuitive.
Also, the default GUI on Linux for bsnes and bgameboy is now Qt, instead
of GTK+. I did this because Qt's fullscreen is far more stable, and
I fixed up the remaining bugs anyway.
2011-02-02 10:35:15 +00:00
|
|
|
{
|
|
|
|
return QObject::d_ptr->metaObject ? QObject::d_ptr->metaObject : &staticMetaObject;
|
|
|
|
}
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
void *phoenix::pHexEdit::qt_metacast(const char *_clname)
|
Update to v075r03 release.
byuu says:
Changelog:
- added full HexEditor widget to phoenix/Qt (has dynamic scrollbar like
phoenix/GTK, but does not yet support page up/down scrolling)
- optimized debugger to look great with either phoenix/GTK or phoenix/Qt
- fixed phoenix/Qt fullscreen mode (had to allow resizing of the layout,
and resize the container)
- fixed phoenix/Qt Window::setBackgroundColor() bug that was making
statusbar invisible
- entering fullscreen now captures mouse, leaving fullscreen releases it
- so by default, no cursor in fullscreen mode now
- F12 key was assigned the task of toggling mouse capture,
Tools->Capture Mouse was removed
- above change allows toggling mouse capture in fullscreen if you like
It wasn't my idea, but toggling the mouse capture in fullscreen also hiding the mouse cursor is what I call genius design. Two birds with one stone, and very intuitive.
Also, the default GUI on Linux for bsnes and bgameboy is now Qt, instead
of GTK+. I did this because Qt's fullscreen is far more stable, and
I fixed up the remaining bugs anyway.
2011-02-02 10:35:15 +00:00
|
|
|
{
|
|
|
|
if (!_clname) return 0;
|
2013-03-15 13:11:33 +00:00
|
|
|
if (!strcmp(_clname, qt_meta_stringdata_phoenix__pHexEdit))
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
return static_cast<void*>(const_cast< pHexEdit*>(this));
|
|
|
|
if (!strcmp(_clname, "pWidget"))
|
|
|
|
return static_cast< pWidget*>(const_cast< pHexEdit*>(this));
|
|
|
|
return QObject::qt_metacast(_clname);
|
Update to v075r03 release.
byuu says:
Changelog:
- added full HexEditor widget to phoenix/Qt (has dynamic scrollbar like
phoenix/GTK, but does not yet support page up/down scrolling)
- optimized debugger to look great with either phoenix/GTK or phoenix/Qt
- fixed phoenix/Qt fullscreen mode (had to allow resizing of the layout,
and resize the container)
- fixed phoenix/Qt Window::setBackgroundColor() bug that was making
statusbar invisible
- entering fullscreen now captures mouse, leaving fullscreen releases it
- so by default, no cursor in fullscreen mode now
- F12 key was assigned the task of toggling mouse capture,
Tools->Capture Mouse was removed
- above change allows toggling mouse capture in fullscreen if you like
It wasn't my idea, but toggling the mouse capture in fullscreen also hiding the mouse cursor is what I call genius design. Two birds with one stone, and very intuitive.
Also, the default GUI on Linux for bsnes and bgameboy is now Qt, instead
of GTK+. I did this because Qt's fullscreen is far more stable, and
I fixed up the remaining bugs anyway.
2011-02-02 10:35:15 +00:00
|
|
|
}
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
int phoenix::pHexEdit::qt_metacall(QMetaObject::Call _c, int _id, void **_a)
|
Update to v075r03 release.
byuu says:
Changelog:
- added full HexEditor widget to phoenix/Qt (has dynamic scrollbar like
phoenix/GTK, but does not yet support page up/down scrolling)
- optimized debugger to look great with either phoenix/GTK or phoenix/Qt
- fixed phoenix/Qt fullscreen mode (had to allow resizing of the layout,
and resize the container)
- fixed phoenix/Qt Window::setBackgroundColor() bug that was making
statusbar invisible
- entering fullscreen now captures mouse, leaving fullscreen releases it
- so by default, no cursor in fullscreen mode now
- F12 key was assigned the task of toggling mouse capture,
Tools->Capture Mouse was removed
- above change allows toggling mouse capture in fullscreen if you like
It wasn't my idea, but toggling the mouse capture in fullscreen also hiding the mouse cursor is what I call genius design. Two birds with one stone, and very intuitive.
Also, the default GUI on Linux for bsnes and bgameboy is now Qt, instead
of GTK+. I did this because Qt's fullscreen is far more stable, and
I fixed up the remaining bugs anyway.
2011-02-02 10:35:15 +00:00
|
|
|
{
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
_id = QObject::qt_metacall(_c, _id, _a);
|
Update to v075r03 release.
byuu says:
Changelog:
- added full HexEditor widget to phoenix/Qt (has dynamic scrollbar like
phoenix/GTK, but does not yet support page up/down scrolling)
- optimized debugger to look great with either phoenix/GTK or phoenix/Qt
- fixed phoenix/Qt fullscreen mode (had to allow resizing of the layout,
and resize the container)
- fixed phoenix/Qt Window::setBackgroundColor() bug that was making
statusbar invisible
- entering fullscreen now captures mouse, leaving fullscreen releases it
- so by default, no cursor in fullscreen mode now
- F12 key was assigned the task of toggling mouse capture,
Tools->Capture Mouse was removed
- above change allows toggling mouse capture in fullscreen if you like
It wasn't my idea, but toggling the mouse capture in fullscreen also hiding the mouse cursor is what I call genius design. Two birds with one stone, and very intuitive.
Also, the default GUI on Linux for bsnes and bgameboy is now Qt, instead
of GTK+. I did this because Qt's fullscreen is far more stable, and
I fixed up the remaining bugs anyway.
2011-02-02 10:35:15 +00:00
|
|
|
if (_id < 0)
|
|
|
|
return _id;
|
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
if (_id < 1)
|
|
|
|
qt_static_metacall(this, _c, _id, _a);
|
Update to v075r03 release.
byuu says:
Changelog:
- added full HexEditor widget to phoenix/Qt (has dynamic scrollbar like
phoenix/GTK, but does not yet support page up/down scrolling)
- optimized debugger to look great with either phoenix/GTK or phoenix/Qt
- fixed phoenix/Qt fullscreen mode (had to allow resizing of the layout,
and resize the container)
- fixed phoenix/Qt Window::setBackgroundColor() bug that was making
statusbar invisible
- entering fullscreen now captures mouse, leaving fullscreen releases it
- so by default, no cursor in fullscreen mode now
- F12 key was assigned the task of toggling mouse capture,
Tools->Capture Mouse was removed
- above change allows toggling mouse capture in fullscreen if you like
It wasn't my idea, but toggling the mouse capture in fullscreen also hiding the mouse cursor is what I call genius design. Two birds with one stone, and very intuitive.
Also, the default GUI on Linux for bsnes and bgameboy is now Qt, instead
of GTK+. I did this because Qt's fullscreen is far more stable, and
I fixed up the remaining bugs anyway.
2011-02-02 10:35:15 +00:00
|
|
|
_id -= 1;
|
|
|
|
}
|
|
|
|
return _id;
|
|
|
|
}
|
2013-03-15 13:11:33 +00:00
|
|
|
static const uint qt_meta_data_phoenix__pHorizontalScroller[] = {
|
2011-08-06 14:03:52 +00:00
|
|
|
|
|
|
|
// content:
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
6, // revision
|
2011-08-06 14:03:52 +00:00
|
|
|
0, // classname
|
|
|
|
0, 0, // classinfo
|
|
|
|
1, 14, // methods
|
|
|
|
0, 0, // properties
|
|
|
|
0, 0, // enums/sets
|
|
|
|
0, 0, // constructors
|
|
|
|
0, // flags
|
|
|
|
0, // signalCount
|
|
|
|
|
|
|
|
// slots: signature, parameters, type, tag, flags
|
2013-03-15 13:11:33 +00:00
|
|
|
30, 29, 29, 29, 0x0a,
|
2011-08-06 14:03:52 +00:00
|
|
|
|
|
|
|
0 // eod
|
|
|
|
};
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
static const char qt_meta_stringdata_phoenix__pHorizontalScroller[] = {
|
|
|
|
"phoenix::pHorizontalScroller\0\0onChange()\0"
|
2011-08-06 14:03:52 +00:00
|
|
|
};
|
|
|
|
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
void phoenix::pHorizontalScroller::qt_static_metacall(QObject *_o, QMetaObject::Call _c, int _id, void **_a)
|
|
|
|
{
|
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
|
|
|
Q_ASSERT(staticMetaObject.cast(_o));
|
|
|
|
pHorizontalScroller *_t = static_cast<pHorizontalScroller *>(_o);
|
|
|
|
switch (_id) {
|
|
|
|
case 0: _t->onChange(); break;
|
|
|
|
default: ;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
Q_UNUSED(_a);
|
|
|
|
}
|
|
|
|
|
|
|
|
const QMetaObjectExtraData phoenix::pHorizontalScroller::staticMetaObjectExtraData = {
|
|
|
|
0, qt_static_metacall
|
|
|
|
};
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject phoenix::pHorizontalScroller::staticMetaObject = {
|
|
|
|
{ &QObject::staticMetaObject, qt_meta_stringdata_phoenix__pHorizontalScroller,
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
qt_meta_data_phoenix__pHorizontalScroller, &staticMetaObjectExtraData }
|
2011-08-06 14:03:52 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
#ifdef Q_NO_DATA_RELOCATION
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject &phoenix::pHorizontalScroller::getStaticMetaObject() { return staticMetaObject; }
|
2011-08-06 14:03:52 +00:00
|
|
|
#endif //Q_NO_DATA_RELOCATION
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject *phoenix::pHorizontalScroller::metaObject() const
|
2011-08-06 14:03:52 +00:00
|
|
|
{
|
|
|
|
return QObject::d_ptr->metaObject ? QObject::d_ptr->metaObject : &staticMetaObject;
|
|
|
|
}
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
void *phoenix::pHorizontalScroller::qt_metacast(const char *_clname)
|
2011-08-06 14:03:52 +00:00
|
|
|
{
|
|
|
|
if (!_clname) return 0;
|
2013-03-15 13:11:33 +00:00
|
|
|
if (!strcmp(_clname, qt_meta_stringdata_phoenix__pHorizontalScroller))
|
|
|
|
return static_cast<void*>(const_cast< pHorizontalScroller*>(this));
|
2011-08-06 14:03:52 +00:00
|
|
|
if (!strcmp(_clname, "pWidget"))
|
2013-03-15 13:11:33 +00:00
|
|
|
return static_cast< pWidget*>(const_cast< pHorizontalScroller*>(this));
|
2011-08-06 14:03:52 +00:00
|
|
|
return QObject::qt_metacast(_clname);
|
|
|
|
}
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
int phoenix::pHorizontalScroller::qt_metacall(QMetaObject::Call _c, int _id, void **_a)
|
2011-08-06 14:03:52 +00:00
|
|
|
{
|
|
|
|
_id = QObject::qt_metacall(_c, _id, _a);
|
|
|
|
if (_id < 0)
|
|
|
|
return _id;
|
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
if (_id < 1)
|
|
|
|
qt_static_metacall(this, _c, _id, _a);
|
2011-08-06 14:03:52 +00:00
|
|
|
_id -= 1;
|
|
|
|
}
|
|
|
|
return _id;
|
|
|
|
}
|
2013-03-15 13:11:33 +00:00
|
|
|
static const uint qt_meta_data_phoenix__pHorizontalSlider[] = {
|
2010-09-26 05:09:31 +00:00
|
|
|
|
|
|
|
// content:
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
6, // revision
|
2010-09-26 05:09:31 +00:00
|
|
|
0, // classname
|
|
|
|
0, 0, // classinfo
|
|
|
|
1, 14, // methods
|
|
|
|
0, 0, // properties
|
|
|
|
0, 0, // enums/sets
|
|
|
|
0, 0, // constructors
|
|
|
|
0, // flags
|
|
|
|
0, // signalCount
|
|
|
|
|
|
|
|
// slots: signature, parameters, type, tag, flags
|
2013-03-15 13:11:33 +00:00
|
|
|
28, 27, 27, 27, 0x0a,
|
2010-09-26 05:09:31 +00:00
|
|
|
|
|
|
|
0 // eod
|
|
|
|
};
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
static const char qt_meta_stringdata_phoenix__pHorizontalSlider[] = {
|
|
|
|
"phoenix::pHorizontalSlider\0\0onChange()\0"
|
2010-09-26 05:09:31 +00:00
|
|
|
};
|
|
|
|
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
void phoenix::pHorizontalSlider::qt_static_metacall(QObject *_o, QMetaObject::Call _c, int _id, void **_a)
|
|
|
|
{
|
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
|
|
|
Q_ASSERT(staticMetaObject.cast(_o));
|
|
|
|
pHorizontalSlider *_t = static_cast<pHorizontalSlider *>(_o);
|
|
|
|
switch (_id) {
|
|
|
|
case 0: _t->onChange(); break;
|
|
|
|
default: ;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
Q_UNUSED(_a);
|
|
|
|
}
|
|
|
|
|
|
|
|
const QMetaObjectExtraData phoenix::pHorizontalSlider::staticMetaObjectExtraData = {
|
|
|
|
0, qt_static_metacall
|
|
|
|
};
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject phoenix::pHorizontalSlider::staticMetaObject = {
|
|
|
|
{ &QObject::staticMetaObject, qt_meta_stringdata_phoenix__pHorizontalSlider,
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
qt_meta_data_phoenix__pHorizontalSlider, &staticMetaObjectExtraData }
|
2010-09-26 05:09:31 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
#ifdef Q_NO_DATA_RELOCATION
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject &phoenix::pHorizontalSlider::getStaticMetaObject() { return staticMetaObject; }
|
2010-09-26 05:09:31 +00:00
|
|
|
#endif //Q_NO_DATA_RELOCATION
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject *phoenix::pHorizontalSlider::metaObject() const
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
|
|
|
return QObject::d_ptr->metaObject ? QObject::d_ptr->metaObject : &staticMetaObject;
|
|
|
|
}
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
void *phoenix::pHorizontalSlider::qt_metacast(const char *_clname)
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
|
|
|
if (!_clname) return 0;
|
2013-03-15 13:11:33 +00:00
|
|
|
if (!strcmp(_clname, qt_meta_stringdata_phoenix__pHorizontalSlider))
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
return static_cast<void*>(const_cast< pHorizontalSlider*>(this));
|
|
|
|
if (!strcmp(_clname, "pWidget"))
|
|
|
|
return static_cast< pWidget*>(const_cast< pHorizontalSlider*>(this));
|
|
|
|
return QObject::qt_metacast(_clname);
|
2010-09-26 05:09:31 +00:00
|
|
|
}
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
int phoenix::pHorizontalSlider::qt_metacall(QMetaObject::Call _c, int _id, void **_a)
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
_id = QObject::qt_metacall(_c, _id, _a);
|
2010-09-26 05:09:31 +00:00
|
|
|
if (_id < 0)
|
|
|
|
return _id;
|
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
if (_id < 1)
|
|
|
|
qt_static_metacall(this, _c, _id, _a);
|
2010-09-26 05:09:31 +00:00
|
|
|
_id -= 1;
|
|
|
|
}
|
|
|
|
return _id;
|
|
|
|
}
|
2013-03-15 13:11:33 +00:00
|
|
|
static const uint qt_meta_data_phoenix__pLineEdit[] = {
|
2010-09-26 05:09:31 +00:00
|
|
|
|
|
|
|
// content:
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
6, // revision
|
2010-09-26 05:09:31 +00:00
|
|
|
0, // classname
|
|
|
|
0, 0, // classinfo
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
2, 14, // methods
|
2010-09-26 05:09:31 +00:00
|
|
|
0, 0, // properties
|
|
|
|
0, 0, // enums/sets
|
|
|
|
0, 0, // constructors
|
|
|
|
0, // flags
|
|
|
|
0, // signalCount
|
|
|
|
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
// slots: signature, parameters, type, tag, flags
|
2013-03-15 13:11:33 +00:00
|
|
|
20, 19, 19, 19, 0x0a,
|
|
|
|
33, 19, 19, 19, 0x0a,
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
|
2010-09-26 05:09:31 +00:00
|
|
|
0 // eod
|
|
|
|
};
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
static const char qt_meta_stringdata_phoenix__pLineEdit[] = {
|
|
|
|
"phoenix::pLineEdit\0\0onActivate()\0"
|
|
|
|
"onChange()\0"
|
2010-09-26 05:09:31 +00:00
|
|
|
};
|
|
|
|
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
void phoenix::pLineEdit::qt_static_metacall(QObject *_o, QMetaObject::Call _c, int _id, void **_a)
|
|
|
|
{
|
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
|
|
|
Q_ASSERT(staticMetaObject.cast(_o));
|
|
|
|
pLineEdit *_t = static_cast<pLineEdit *>(_o);
|
|
|
|
switch (_id) {
|
|
|
|
case 0: _t->onActivate(); break;
|
|
|
|
case 1: _t->onChange(); break;
|
|
|
|
default: ;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
Q_UNUSED(_a);
|
|
|
|
}
|
|
|
|
|
|
|
|
const QMetaObjectExtraData phoenix::pLineEdit::staticMetaObjectExtraData = {
|
|
|
|
0, qt_static_metacall
|
|
|
|
};
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject phoenix::pLineEdit::staticMetaObject = {
|
|
|
|
{ &QObject::staticMetaObject, qt_meta_stringdata_phoenix__pLineEdit,
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
qt_meta_data_phoenix__pLineEdit, &staticMetaObjectExtraData }
|
2010-09-26 05:09:31 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
#ifdef Q_NO_DATA_RELOCATION
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject &phoenix::pLineEdit::getStaticMetaObject() { return staticMetaObject; }
|
2010-09-26 05:09:31 +00:00
|
|
|
#endif //Q_NO_DATA_RELOCATION
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject *phoenix::pLineEdit::metaObject() const
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
|
|
|
return QObject::d_ptr->metaObject ? QObject::d_ptr->metaObject : &staticMetaObject;
|
|
|
|
}
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
void *phoenix::pLineEdit::qt_metacast(const char *_clname)
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
|
|
|
if (!_clname) return 0;
|
2013-03-15 13:11:33 +00:00
|
|
|
if (!strcmp(_clname, qt_meta_stringdata_phoenix__pLineEdit))
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
return static_cast<void*>(const_cast< pLineEdit*>(this));
|
|
|
|
if (!strcmp(_clname, "pWidget"))
|
|
|
|
return static_cast< pWidget*>(const_cast< pLineEdit*>(this));
|
|
|
|
return QObject::qt_metacast(_clname);
|
2010-09-26 05:09:31 +00:00
|
|
|
}
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
int phoenix::pLineEdit::qt_metacall(QMetaObject::Call _c, int _id, void **_a)
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
_id = QObject::qt_metacall(_c, _id, _a);
|
2010-09-26 05:09:31 +00:00
|
|
|
if (_id < 0)
|
|
|
|
return _id;
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
if (_id < 2)
|
|
|
|
qt_static_metacall(this, _c, _id, _a);
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
_id -= 2;
|
|
|
|
}
|
2010-09-26 05:09:31 +00:00
|
|
|
return _id;
|
|
|
|
}
|
2013-03-15 13:11:33 +00:00
|
|
|
static const uint qt_meta_data_phoenix__pListView[] = {
|
2010-09-26 05:09:31 +00:00
|
|
|
|
|
|
|
// content:
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
6, // revision
|
2010-09-26 05:09:31 +00:00
|
|
|
0, // classname
|
|
|
|
0, 0, // classinfo
|
Update to v070r08 release.
byuu says:
- all three ports of phoenix gain the ability to use
ListBox::setCheckable(), checked(row), setChecked(row, checked
= true);
- cheat editor updated to take advantage of this
Some fun differences between the implementations. Windows was the least
flexible, it only lets you have a check at the start of each item.
Luckily that's all I need for my purposes so it'll work. It's also a lot
easier, as now I don't need a ton of extra code to try and set
per-column checkboxes. Now both Windows and Qt can put text into the
first item with the checkbox, but GTK+ cannot. Further, Qt needs this
because even if you hide the checkbox column, it still tries to search
for typed text from the checkbox column. GTK+ does this too, but unlike
GTK+, Qt lacks an API call to set the search column. Since my code
basically has to change this in real-time since you have to call the
setProperty functions after create(), this means I always set up the
checkbox columns regardless of whether or not they are used. For Qt,
I had to work around this and it'll be an annoying edge case if you try
and use setCheckable(true) and then setCheckable(false), because Qt has
no way to clear the checkboxes from an item once you've enabled them for
the first time. But without doing it this way, there's no way for eg the
ROM file loader to allow type-searching, so that's the way I do it.
Windows works the same, and GTK+ has a separate column (hidden from the
phoenix API standpoint) for the checkboxes, with no column header label
text.
All in all, a major hassle, but it was the only really major GUI hit
from leaving Qt, aside from the horror that's going to be the debugger,
which needs all kinds of highly specialized controls.
2010-10-04 05:33:49 +00:00
|
|
|
3, 14, // methods
|
2010-09-26 05:09:31 +00:00
|
|
|
0, 0, // properties
|
|
|
|
0, 0, // enums/sets
|
|
|
|
0, 0, // constructors
|
|
|
|
0, // flags
|
|
|
|
0, // signalCount
|
|
|
|
|
|
|
|
// slots: signature, parameters, type, tag, flags
|
2013-03-15 13:11:33 +00:00
|
|
|
20, 19, 19, 19, 0x0a,
|
|
|
|
38, 33, 19, 19, 0x0a,
|
|
|
|
65, 33, 19, 19, 0x0a,
|
2010-09-26 05:09:31 +00:00
|
|
|
|
|
|
|
0 // eod
|
|
|
|
};
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
static const char qt_meta_stringdata_phoenix__pListView[] = {
|
|
|
|
"phoenix::pListView\0\0onActivate()\0item\0"
|
Update to v080r08 release.
byuu says, in a post between the v080r07 release and the v080r08
release:
phoenix/Windows:
The slider and scrollbar setParent calls setLength+setPosition, but
setLength sets position = 0 (due to new length possibly invalidating
previous position.)
Cache position first to fix this, can now reparent widgets with proper
slider/scroll positions.
ListView had a workaround where the horizontal scrollbar was always
appearing on single-column lists. The workaround was forcing the config
settings list in bsnes to only select the text portions of each item in
the list, instead of the entire lines. The workaround was needed because
without setting a single header text, the header text count was equal to
zero, causing autoSizeColumns to have no effect. Made the constructor
call setHeaderText("") to guarantee size() >= 1 always. Removes the need
for the workaround, and gives a good file browser and configuration
setting window.
phoenix/Qt:
Worked around Qt bugs #258,674+258,675: if you click a list item with
your mouse, currentItem()->isSelected() returns false. It does not
return true until you select an item with a keyboard key. I forced it to
set the selected item upon currentItemChanged() message. It was also not
sending a changed message upon clearing the selection and then selecting
the same item again. I had to do something undocumented:
setCurrentItem(nullptr) so that currentItemChanged works again.
phoenix/All:
Fonts are now initialized to the platform default settings, Tahoma or
Sans 8-point. This lets geometry on widgets not attached to windows work
better. Makes the ../... buttons smaller pretty much everywhere.
byuu says, announcing the v080r08 release:
Fixed all of the above phoenix issues, and improved the auto-disabling
of buttons on the input setting and state manager windows.
Also manually initiailized lastConfigure for Valgrind in GTK+. Windows
and GTK+ ports look a lot nicer now.
2011-08-08 12:04:47 +00:00
|
|
|
"onChange(QTreeWidgetItem*)\0"
|
2011-12-12 10:59:53 +00:00
|
|
|
"onToggle(QTreeWidgetItem*)\0"
|
2010-09-26 05:09:31 +00:00
|
|
|
};
|
|
|
|
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
void phoenix::pListView::qt_static_metacall(QObject *_o, QMetaObject::Call _c, int _id, void **_a)
|
|
|
|
{
|
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
|
|
|
Q_ASSERT(staticMetaObject.cast(_o));
|
|
|
|
pListView *_t = static_cast<pListView *>(_o);
|
|
|
|
switch (_id) {
|
|
|
|
case 0: _t->onActivate(); break;
|
|
|
|
case 1: _t->onChange((*reinterpret_cast< QTreeWidgetItem*(*)>(_a[1]))); break;
|
|
|
|
case 2: _t->onToggle((*reinterpret_cast< QTreeWidgetItem*(*)>(_a[1]))); break;
|
|
|
|
default: ;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
const QMetaObjectExtraData phoenix::pListView::staticMetaObjectExtraData = {
|
|
|
|
0, qt_static_metacall
|
|
|
|
};
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject phoenix::pListView::staticMetaObject = {
|
|
|
|
{ &QObject::staticMetaObject, qt_meta_stringdata_phoenix__pListView,
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
qt_meta_data_phoenix__pListView, &staticMetaObjectExtraData }
|
2010-09-26 05:09:31 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
#ifdef Q_NO_DATA_RELOCATION
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject &phoenix::pListView::getStaticMetaObject() { return staticMetaObject; }
|
2010-09-26 05:09:31 +00:00
|
|
|
#endif //Q_NO_DATA_RELOCATION
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject *phoenix::pListView::metaObject() const
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
|
|
|
return QObject::d_ptr->metaObject ? QObject::d_ptr->metaObject : &staticMetaObject;
|
|
|
|
}
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
void *phoenix::pListView::qt_metacast(const char *_clname)
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
|
|
|
if (!_clname) return 0;
|
2013-03-15 13:11:33 +00:00
|
|
|
if (!strcmp(_clname, qt_meta_stringdata_phoenix__pListView))
|
2011-02-16 12:35:40 +00:00
|
|
|
return static_cast<void*>(const_cast< pListView*>(this));
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
if (!strcmp(_clname, "pWidget"))
|
2011-02-16 12:35:40 +00:00
|
|
|
return static_cast< pWidget*>(const_cast< pListView*>(this));
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
return QObject::qt_metacast(_clname);
|
2010-09-26 05:09:31 +00:00
|
|
|
}
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
int phoenix::pListView::qt_metacall(QMetaObject::Call _c, int _id, void **_a)
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
_id = QObject::qt_metacall(_c, _id, _a);
|
2010-09-26 05:09:31 +00:00
|
|
|
if (_id < 0)
|
|
|
|
return _id;
|
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
if (_id < 3)
|
|
|
|
qt_static_metacall(this, _c, _id, _a);
|
Update to v070r08 release.
byuu says:
- all three ports of phoenix gain the ability to use
ListBox::setCheckable(), checked(row), setChecked(row, checked
= true);
- cheat editor updated to take advantage of this
Some fun differences between the implementations. Windows was the least
flexible, it only lets you have a check at the start of each item.
Luckily that's all I need for my purposes so it'll work. It's also a lot
easier, as now I don't need a ton of extra code to try and set
per-column checkboxes. Now both Windows and Qt can put text into the
first item with the checkbox, but GTK+ cannot. Further, Qt needs this
because even if you hide the checkbox column, it still tries to search
for typed text from the checkbox column. GTK+ does this too, but unlike
GTK+, Qt lacks an API call to set the search column. Since my code
basically has to change this in real-time since you have to call the
setProperty functions after create(), this means I always set up the
checkbox columns regardless of whether or not they are used. For Qt,
I had to work around this and it'll be an annoying edge case if you try
and use setCheckable(true) and then setCheckable(false), because Qt has
no way to clear the checkboxes from an item once you've enabled them for
the first time. But without doing it this way, there's no way for eg the
ROM file loader to allow type-searching, so that's the way I do it.
Windows works the same, and GTK+ has a separate column (hidden from the
phoenix API standpoint) for the checkboxes, with no column header label
text.
All in all, a major hassle, but it was the only really major GUI hit
from leaving Qt, aside from the horror that's going to be the debugger,
which needs all kinds of highly specialized controls.
2010-10-04 05:33:49 +00:00
|
|
|
_id -= 3;
|
2010-09-26 05:09:31 +00:00
|
|
|
}
|
|
|
|
return _id;
|
|
|
|
}
|
2013-11-28 10:29:01 +00:00
|
|
|
static const uint qt_meta_data_phoenix__pRadioLabel[] = {
|
|
|
|
|
|
|
|
// content:
|
|
|
|
6, // revision
|
|
|
|
0, // classname
|
|
|
|
0, 0, // classinfo
|
|
|
|
1, 14, // methods
|
|
|
|
0, 0, // properties
|
|
|
|
0, 0, // enums/sets
|
|
|
|
0, 0, // constructors
|
|
|
|
0, // flags
|
|
|
|
0, // signalCount
|
|
|
|
|
|
|
|
// slots: signature, parameters, type, tag, flags
|
|
|
|
22, 21, 21, 21, 0x0a,
|
|
|
|
|
|
|
|
0 // eod
|
|
|
|
};
|
|
|
|
|
|
|
|
static const char qt_meta_stringdata_phoenix__pRadioLabel[] = {
|
|
|
|
"phoenix::pRadioLabel\0\0onActivate()\0"
|
|
|
|
};
|
|
|
|
|
|
|
|
void phoenix::pRadioLabel::qt_static_metacall(QObject *_o, QMetaObject::Call _c, int _id, void **_a)
|
|
|
|
{
|
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
|
|
|
Q_ASSERT(staticMetaObject.cast(_o));
|
|
|
|
pRadioLabel *_t = static_cast<pRadioLabel *>(_o);
|
|
|
|
switch (_id) {
|
|
|
|
case 0: _t->onActivate(); break;
|
|
|
|
default: ;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
Q_UNUSED(_a);
|
|
|
|
}
|
|
|
|
|
|
|
|
const QMetaObjectExtraData phoenix::pRadioLabel::staticMetaObjectExtraData = {
|
|
|
|
0, qt_static_metacall
|
|
|
|
};
|
|
|
|
|
|
|
|
const QMetaObject phoenix::pRadioLabel::staticMetaObject = {
|
|
|
|
{ &QObject::staticMetaObject, qt_meta_stringdata_phoenix__pRadioLabel,
|
|
|
|
qt_meta_data_phoenix__pRadioLabel, &staticMetaObjectExtraData }
|
|
|
|
};
|
|
|
|
|
|
|
|
#ifdef Q_NO_DATA_RELOCATION
|
|
|
|
const QMetaObject &phoenix::pRadioLabel::getStaticMetaObject() { return staticMetaObject; }
|
|
|
|
#endif //Q_NO_DATA_RELOCATION
|
|
|
|
|
|
|
|
const QMetaObject *phoenix::pRadioLabel::metaObject() const
|
|
|
|
{
|
|
|
|
return QObject::d_ptr->metaObject ? QObject::d_ptr->metaObject : &staticMetaObject;
|
|
|
|
}
|
|
|
|
|
|
|
|
void *phoenix::pRadioLabel::qt_metacast(const char *_clname)
|
|
|
|
{
|
|
|
|
if (!_clname) return 0;
|
|
|
|
if (!strcmp(_clname, qt_meta_stringdata_phoenix__pRadioLabel))
|
|
|
|
return static_cast<void*>(const_cast< pRadioLabel*>(this));
|
|
|
|
if (!strcmp(_clname, "pWidget"))
|
|
|
|
return static_cast< pWidget*>(const_cast< pRadioLabel*>(this));
|
|
|
|
return QObject::qt_metacast(_clname);
|
|
|
|
}
|
|
|
|
|
|
|
|
int phoenix::pRadioLabel::qt_metacall(QMetaObject::Call _c, int _id, void **_a)
|
|
|
|
{
|
|
|
|
_id = QObject::qt_metacall(_c, _id, _a);
|
|
|
|
if (_id < 0)
|
|
|
|
return _id;
|
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
|
|
|
if (_id < 1)
|
|
|
|
qt_static_metacall(this, _c, _id, _a);
|
|
|
|
_id -= 1;
|
|
|
|
}
|
|
|
|
return _id;
|
|
|
|
}
|
2013-03-15 13:11:33 +00:00
|
|
|
static const uint qt_meta_data_phoenix__pRadioButton[] = {
|
2010-09-26 05:09:31 +00:00
|
|
|
|
|
|
|
// content:
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
6, // revision
|
2010-09-26 05:09:31 +00:00
|
|
|
0, // classname
|
|
|
|
0, 0, // classinfo
|
|
|
|
1, 14, // methods
|
|
|
|
0, 0, // properties
|
|
|
|
0, 0, // enums/sets
|
|
|
|
0, 0, // constructors
|
|
|
|
0, // flags
|
|
|
|
0, // signalCount
|
|
|
|
|
|
|
|
// slots: signature, parameters, type, tag, flags
|
2013-03-15 13:11:33 +00:00
|
|
|
23, 22, 22, 22, 0x0a,
|
2010-09-26 05:09:31 +00:00
|
|
|
|
|
|
|
0 // eod
|
|
|
|
};
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
static const char qt_meta_stringdata_phoenix__pRadioButton[] = {
|
|
|
|
"phoenix::pRadioButton\0\0onActivate()\0"
|
2010-09-26 05:09:31 +00:00
|
|
|
};
|
|
|
|
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
void phoenix::pRadioButton::qt_static_metacall(QObject *_o, QMetaObject::Call _c, int _id, void **_a)
|
|
|
|
{
|
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
|
|
|
Q_ASSERT(staticMetaObject.cast(_o));
|
|
|
|
pRadioButton *_t = static_cast<pRadioButton *>(_o);
|
|
|
|
switch (_id) {
|
|
|
|
case 0: _t->onActivate(); break;
|
|
|
|
default: ;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
Q_UNUSED(_a);
|
|
|
|
}
|
|
|
|
|
|
|
|
const QMetaObjectExtraData phoenix::pRadioButton::staticMetaObjectExtraData = {
|
|
|
|
0, qt_static_metacall
|
|
|
|
};
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject phoenix::pRadioButton::staticMetaObject = {
|
|
|
|
{ &QObject::staticMetaObject, qt_meta_stringdata_phoenix__pRadioButton,
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
qt_meta_data_phoenix__pRadioButton, &staticMetaObjectExtraData }
|
2010-09-26 05:09:31 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
#ifdef Q_NO_DATA_RELOCATION
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject &phoenix::pRadioButton::getStaticMetaObject() { return staticMetaObject; }
|
2010-09-26 05:09:31 +00:00
|
|
|
#endif //Q_NO_DATA_RELOCATION
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject *phoenix::pRadioButton::metaObject() const
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
|
|
|
return QObject::d_ptr->metaObject ? QObject::d_ptr->metaObject : &staticMetaObject;
|
|
|
|
}
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
void *phoenix::pRadioButton::qt_metacast(const char *_clname)
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
|
|
|
if (!_clname) return 0;
|
2013-03-15 13:11:33 +00:00
|
|
|
if (!strcmp(_clname, qt_meta_stringdata_phoenix__pRadioButton))
|
|
|
|
return static_cast<void*>(const_cast< pRadioButton*>(this));
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
if (!strcmp(_clname, "pWidget"))
|
2013-03-15 13:11:33 +00:00
|
|
|
return static_cast< pWidget*>(const_cast< pRadioButton*>(this));
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
return QObject::qt_metacast(_clname);
|
2010-09-26 05:09:31 +00:00
|
|
|
}
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
int phoenix::pRadioButton::qt_metacall(QMetaObject::Call _c, int _id, void **_a)
|
2013-11-28 10:29:01 +00:00
|
|
|
{
|
|
|
|
_id = QObject::qt_metacall(_c, _id, _a);
|
|
|
|
if (_id < 0)
|
|
|
|
return _id;
|
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
|
|
|
if (_id < 1)
|
|
|
|
qt_static_metacall(this, _c, _id, _a);
|
|
|
|
_id -= 1;
|
|
|
|
}
|
|
|
|
return _id;
|
|
|
|
}
|
|
|
|
static const uint qt_meta_data_phoenix__pTabFrame[] = {
|
|
|
|
|
|
|
|
// content:
|
|
|
|
6, // revision
|
|
|
|
0, // classname
|
|
|
|
0, 0, // classinfo
|
|
|
|
1, 14, // methods
|
|
|
|
0, 0, // properties
|
|
|
|
0, 0, // enums/sets
|
|
|
|
0, 0, // constructors
|
|
|
|
0, // flags
|
|
|
|
0, // signalCount
|
|
|
|
|
|
|
|
// slots: signature, parameters, type, tag, flags
|
|
|
|
30, 20, 19, 19, 0x0a,
|
|
|
|
|
|
|
|
0 // eod
|
|
|
|
};
|
|
|
|
|
|
|
|
static const char qt_meta_stringdata_phoenix__pTabFrame[] = {
|
|
|
|
"phoenix::pTabFrame\0\0selection\0"
|
|
|
|
"onChange(int)\0"
|
|
|
|
};
|
|
|
|
|
|
|
|
void phoenix::pTabFrame::qt_static_metacall(QObject *_o, QMetaObject::Call _c, int _id, void **_a)
|
|
|
|
{
|
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
|
|
|
Q_ASSERT(staticMetaObject.cast(_o));
|
|
|
|
pTabFrame *_t = static_cast<pTabFrame *>(_o);
|
|
|
|
switch (_id) {
|
|
|
|
case 0: _t->onChange((*reinterpret_cast< int(*)>(_a[1]))); break;
|
|
|
|
default: ;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
const QMetaObjectExtraData phoenix::pTabFrame::staticMetaObjectExtraData = {
|
|
|
|
0, qt_static_metacall
|
|
|
|
};
|
|
|
|
|
|
|
|
const QMetaObject phoenix::pTabFrame::staticMetaObject = {
|
|
|
|
{ &QObject::staticMetaObject, qt_meta_stringdata_phoenix__pTabFrame,
|
|
|
|
qt_meta_data_phoenix__pTabFrame, &staticMetaObjectExtraData }
|
|
|
|
};
|
|
|
|
|
|
|
|
#ifdef Q_NO_DATA_RELOCATION
|
|
|
|
const QMetaObject &phoenix::pTabFrame::getStaticMetaObject() { return staticMetaObject; }
|
|
|
|
#endif //Q_NO_DATA_RELOCATION
|
|
|
|
|
|
|
|
const QMetaObject *phoenix::pTabFrame::metaObject() const
|
|
|
|
{
|
|
|
|
return QObject::d_ptr->metaObject ? QObject::d_ptr->metaObject : &staticMetaObject;
|
|
|
|
}
|
|
|
|
|
|
|
|
void *phoenix::pTabFrame::qt_metacast(const char *_clname)
|
|
|
|
{
|
|
|
|
if (!_clname) return 0;
|
|
|
|
if (!strcmp(_clname, qt_meta_stringdata_phoenix__pTabFrame))
|
|
|
|
return static_cast<void*>(const_cast< pTabFrame*>(this));
|
|
|
|
if (!strcmp(_clname, "pWidget"))
|
|
|
|
return static_cast< pWidget*>(const_cast< pTabFrame*>(this));
|
|
|
|
return QObject::qt_metacast(_clname);
|
|
|
|
}
|
|
|
|
|
|
|
|
int phoenix::pTabFrame::qt_metacall(QMetaObject::Call _c, int _id, void **_a)
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
_id = QObject::qt_metacall(_c, _id, _a);
|
2010-09-26 05:09:31 +00:00
|
|
|
if (_id < 0)
|
|
|
|
return _id;
|
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
if (_id < 1)
|
|
|
|
qt_static_metacall(this, _c, _id, _a);
|
2010-09-26 05:09:31 +00:00
|
|
|
_id -= 1;
|
|
|
|
}
|
|
|
|
return _id;
|
|
|
|
}
|
2013-03-15 13:11:33 +00:00
|
|
|
static const uint qt_meta_data_phoenix__pTextEdit[] = {
|
2010-09-26 05:09:31 +00:00
|
|
|
|
|
|
|
// content:
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
6, // revision
|
2010-09-26 05:09:31 +00:00
|
|
|
0, // classname
|
|
|
|
0, 0, // classinfo
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
1, 14, // methods
|
2010-09-26 05:09:31 +00:00
|
|
|
0, 0, // properties
|
|
|
|
0, 0, // enums/sets
|
|
|
|
0, 0, // constructors
|
|
|
|
0, // flags
|
|
|
|
0, // signalCount
|
|
|
|
|
|
|
|
// slots: signature, parameters, type, tag, flags
|
2013-03-15 13:11:33 +00:00
|
|
|
20, 19, 19, 19, 0x0a,
|
2010-09-26 05:09:31 +00:00
|
|
|
|
|
|
|
0 // eod
|
|
|
|
};
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
static const char qt_meta_stringdata_phoenix__pTextEdit[] = {
|
|
|
|
"phoenix::pTextEdit\0\0onChange()\0"
|
2010-09-26 05:09:31 +00:00
|
|
|
};
|
|
|
|
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
void phoenix::pTextEdit::qt_static_metacall(QObject *_o, QMetaObject::Call _c, int _id, void **_a)
|
|
|
|
{
|
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
|
|
|
Q_ASSERT(staticMetaObject.cast(_o));
|
|
|
|
pTextEdit *_t = static_cast<pTextEdit *>(_o);
|
|
|
|
switch (_id) {
|
|
|
|
case 0: _t->onChange(); break;
|
|
|
|
default: ;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
Q_UNUSED(_a);
|
|
|
|
}
|
|
|
|
|
|
|
|
const QMetaObjectExtraData phoenix::pTextEdit::staticMetaObjectExtraData = {
|
|
|
|
0, qt_static_metacall
|
|
|
|
};
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject phoenix::pTextEdit::staticMetaObject = {
|
|
|
|
{ &QObject::staticMetaObject, qt_meta_stringdata_phoenix__pTextEdit,
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
qt_meta_data_phoenix__pTextEdit, &staticMetaObjectExtraData }
|
2010-09-26 05:09:31 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
#ifdef Q_NO_DATA_RELOCATION
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject &phoenix::pTextEdit::getStaticMetaObject() { return staticMetaObject; }
|
2010-09-26 05:09:31 +00:00
|
|
|
#endif //Q_NO_DATA_RELOCATION
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject *phoenix::pTextEdit::metaObject() const
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
|
|
|
return QObject::d_ptr->metaObject ? QObject::d_ptr->metaObject : &staticMetaObject;
|
|
|
|
}
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
void *phoenix::pTextEdit::qt_metacast(const char *_clname)
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
|
|
|
if (!_clname) return 0;
|
2013-03-15 13:11:33 +00:00
|
|
|
if (!strcmp(_clname, qt_meta_stringdata_phoenix__pTextEdit))
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
return static_cast<void*>(const_cast< pTextEdit*>(this));
|
|
|
|
if (!strcmp(_clname, "pWidget"))
|
|
|
|
return static_cast< pWidget*>(const_cast< pTextEdit*>(this));
|
|
|
|
return QObject::qt_metacast(_clname);
|
2010-09-26 05:09:31 +00:00
|
|
|
}
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
int phoenix::pTextEdit::qt_metacall(QMetaObject::Call _c, int _id, void **_a)
|
2011-08-06 14:03:52 +00:00
|
|
|
{
|
|
|
|
_id = QObject::qt_metacall(_c, _id, _a);
|
|
|
|
if (_id < 0)
|
|
|
|
return _id;
|
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
if (_id < 1)
|
|
|
|
qt_static_metacall(this, _c, _id, _a);
|
2011-08-06 14:03:52 +00:00
|
|
|
_id -= 1;
|
|
|
|
}
|
|
|
|
return _id;
|
|
|
|
}
|
2013-03-15 13:11:33 +00:00
|
|
|
static const uint qt_meta_data_phoenix__pVerticalScroller[] = {
|
2011-08-06 14:03:52 +00:00
|
|
|
|
|
|
|
// content:
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
6, // revision
|
2011-08-06 14:03:52 +00:00
|
|
|
0, // classname
|
|
|
|
0, 0, // classinfo
|
|
|
|
1, 14, // methods
|
|
|
|
0, 0, // properties
|
|
|
|
0, 0, // enums/sets
|
|
|
|
0, 0, // constructors
|
|
|
|
0, // flags
|
|
|
|
0, // signalCount
|
|
|
|
|
|
|
|
// slots: signature, parameters, type, tag, flags
|
2013-03-15 13:11:33 +00:00
|
|
|
28, 27, 27, 27, 0x0a,
|
2011-08-06 14:03:52 +00:00
|
|
|
|
|
|
|
0 // eod
|
|
|
|
};
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
static const char qt_meta_stringdata_phoenix__pVerticalScroller[] = {
|
|
|
|
"phoenix::pVerticalScroller\0\0onChange()\0"
|
2011-08-06 14:03:52 +00:00
|
|
|
};
|
|
|
|
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
void phoenix::pVerticalScroller::qt_static_metacall(QObject *_o, QMetaObject::Call _c, int _id, void **_a)
|
|
|
|
{
|
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
|
|
|
Q_ASSERT(staticMetaObject.cast(_o));
|
|
|
|
pVerticalScroller *_t = static_cast<pVerticalScroller *>(_o);
|
|
|
|
switch (_id) {
|
|
|
|
case 0: _t->onChange(); break;
|
|
|
|
default: ;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
Q_UNUSED(_a);
|
|
|
|
}
|
|
|
|
|
|
|
|
const QMetaObjectExtraData phoenix::pVerticalScroller::staticMetaObjectExtraData = {
|
|
|
|
0, qt_static_metacall
|
|
|
|
};
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject phoenix::pVerticalScroller::staticMetaObject = {
|
|
|
|
{ &QObject::staticMetaObject, qt_meta_stringdata_phoenix__pVerticalScroller,
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
qt_meta_data_phoenix__pVerticalScroller, &staticMetaObjectExtraData }
|
2011-08-06 14:03:52 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
#ifdef Q_NO_DATA_RELOCATION
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject &phoenix::pVerticalScroller::getStaticMetaObject() { return staticMetaObject; }
|
2011-08-06 14:03:52 +00:00
|
|
|
#endif //Q_NO_DATA_RELOCATION
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject *phoenix::pVerticalScroller::metaObject() const
|
2011-08-06 14:03:52 +00:00
|
|
|
{
|
|
|
|
return QObject::d_ptr->metaObject ? QObject::d_ptr->metaObject : &staticMetaObject;
|
|
|
|
}
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
void *phoenix::pVerticalScroller::qt_metacast(const char *_clname)
|
2011-08-06 14:03:52 +00:00
|
|
|
{
|
|
|
|
if (!_clname) return 0;
|
2013-03-15 13:11:33 +00:00
|
|
|
if (!strcmp(_clname, qt_meta_stringdata_phoenix__pVerticalScroller))
|
|
|
|
return static_cast<void*>(const_cast< pVerticalScroller*>(this));
|
2011-08-06 14:03:52 +00:00
|
|
|
if (!strcmp(_clname, "pWidget"))
|
2013-03-15 13:11:33 +00:00
|
|
|
return static_cast< pWidget*>(const_cast< pVerticalScroller*>(this));
|
2011-08-06 14:03:52 +00:00
|
|
|
return QObject::qt_metacast(_clname);
|
|
|
|
}
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
int phoenix::pVerticalScroller::qt_metacall(QMetaObject::Call _c, int _id, void **_a)
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
_id = QObject::qt_metacall(_c, _id, _a);
|
2010-09-26 05:09:31 +00:00
|
|
|
if (_id < 0)
|
|
|
|
return _id;
|
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
if (_id < 1)
|
|
|
|
qt_static_metacall(this, _c, _id, _a);
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
_id -= 1;
|
2010-09-26 05:09:31 +00:00
|
|
|
}
|
|
|
|
return _id;
|
|
|
|
}
|
2013-03-15 13:11:33 +00:00
|
|
|
static const uint qt_meta_data_phoenix__pVerticalSlider[] = {
|
2010-09-26 05:09:31 +00:00
|
|
|
|
|
|
|
// content:
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
6, // revision
|
2010-09-26 05:09:31 +00:00
|
|
|
0, // classname
|
|
|
|
0, 0, // classinfo
|
|
|
|
1, 14, // methods
|
|
|
|
0, 0, // properties
|
|
|
|
0, 0, // enums/sets
|
|
|
|
0, 0, // constructors
|
|
|
|
0, // flags
|
|
|
|
0, // signalCount
|
|
|
|
|
|
|
|
// slots: signature, parameters, type, tag, flags
|
2013-03-15 13:11:33 +00:00
|
|
|
26, 25, 25, 25, 0x0a,
|
2010-09-26 05:09:31 +00:00
|
|
|
|
|
|
|
0 // eod
|
|
|
|
};
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
static const char qt_meta_stringdata_phoenix__pVerticalSlider[] = {
|
|
|
|
"phoenix::pVerticalSlider\0\0onChange()\0"
|
2010-09-26 05:09:31 +00:00
|
|
|
};
|
|
|
|
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
void phoenix::pVerticalSlider::qt_static_metacall(QObject *_o, QMetaObject::Call _c, int _id, void **_a)
|
|
|
|
{
|
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
|
|
|
Q_ASSERT(staticMetaObject.cast(_o));
|
|
|
|
pVerticalSlider *_t = static_cast<pVerticalSlider *>(_o);
|
|
|
|
switch (_id) {
|
|
|
|
case 0: _t->onChange(); break;
|
|
|
|
default: ;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
Q_UNUSED(_a);
|
|
|
|
}
|
|
|
|
|
|
|
|
const QMetaObjectExtraData phoenix::pVerticalSlider::staticMetaObjectExtraData = {
|
|
|
|
0, qt_static_metacall
|
|
|
|
};
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject phoenix::pVerticalSlider::staticMetaObject = {
|
|
|
|
{ &QObject::staticMetaObject, qt_meta_stringdata_phoenix__pVerticalSlider,
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
qt_meta_data_phoenix__pVerticalSlider, &staticMetaObjectExtraData }
|
2010-09-26 05:09:31 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
#ifdef Q_NO_DATA_RELOCATION
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject &phoenix::pVerticalSlider::getStaticMetaObject() { return staticMetaObject; }
|
2010-09-26 05:09:31 +00:00
|
|
|
#endif //Q_NO_DATA_RELOCATION
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
const QMetaObject *phoenix::pVerticalSlider::metaObject() const
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
|
|
|
return QObject::d_ptr->metaObject ? QObject::d_ptr->metaObject : &staticMetaObject;
|
|
|
|
}
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
void *phoenix::pVerticalSlider::qt_metacast(const char *_clname)
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
|
|
|
if (!_clname) return 0;
|
2013-03-15 13:11:33 +00:00
|
|
|
if (!strcmp(_clname, qt_meta_stringdata_phoenix__pVerticalSlider))
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
return static_cast<void*>(const_cast< pVerticalSlider*>(this));
|
|
|
|
if (!strcmp(_clname, "pWidget"))
|
|
|
|
return static_cast< pWidget*>(const_cast< pVerticalSlider*>(this));
|
|
|
|
return QObject::qt_metacast(_clname);
|
2010-09-26 05:09:31 +00:00
|
|
|
}
|
|
|
|
|
2013-03-15 13:11:33 +00:00
|
|
|
int phoenix::pVerticalSlider::qt_metacall(QMetaObject::Call _c, int _id, void **_a)
|
2010-09-26 05:09:31 +00:00
|
|
|
{
|
Update to v075r12 release.
byuu says:
phoenix has been completely rewritten from scratch, and bsnes/ui + bsnes/ui-gameboy have been updated to use the new API. Debugger works too. Currently, only phoenix/Qt is completed, and there are two known issues:
1: font sizes of menu items are wrong, I can fix this easily enough
2: there's some sort of multi-second lag when loading games, not sure
what's happening there yet
The new phoenix isn't exactly complete yet, still making some key
changes, and then I'll start on phoenix/Windows and phoenix/GTK+.
The most noticeable difference is that you don't have to give all of the
header paths and PHOENIX_PLATFORM defines when compiling individual GUI
object files. It's only needed for phoenix.cpp itself. The overall
structure of the phoenix source folder is much saner as well for
sync.sh.
I'm really surprised things are working as well as they are for
a two-day power rewrite of an entire phoenix target. The other targets
won't be as bad insofar as the core stuff is completed this time. And
thank god for that, I was about ready to kill myself after writing
dozens of lines like this:
HorizontalSlider::HorizontalSlider() : state(*new State),
base_from_member<pHorizontalSlider&>(*new pHorizontalSlider(*this)),
Widget(base_from_member<pHorizontalSlider&>::value),
p(base_from_member<pHorizontalSlider&>::value) {}
But each platform does have some new, unique problems. phoenix/GTK+ was
acting screwy prior to the rewrite, and will most likely still have
issues. Even more important, one of the major points of this rewrite was
having the new phoenix/core cache widget settings/data, so that I can
destroy and recreate widgets rather than relying on SetParent. This
means that simple copying of the old phoenix/Windows won't work, and
this new method is significantly more involved.
2011-02-15 12:22:37 +00:00
|
|
|
_id = QObject::qt_metacall(_c, _id, _a);
|
2010-09-26 05:09:31 +00:00
|
|
|
if (_id < 0)
|
|
|
|
return _id;
|
|
|
|
if (_c == QMetaObject::InvokeMetaMethod) {
|
Update to v093r02 release.
byuu says:
Changelog:
- nall: fixed major memory leak in string class
- ruby: video shaders support #define-based settings now
- phoenix/GTK+: support > 256x256 icons for window / task bar / alt-tab
- sfc: remove random/ and config/, merge into system/
- ethos: delete higan.png (48x48), replace with higan512.png (512x512)
as new higan.png
- ethos: default gamma to 100% (no color adjustment)
- ethos: use "Video Shaders/Display Emulation/" instead of "Video
Shaders/Emulation/"
- use g++ instead of g++-4.7 (g++ -v must be >= 4.7)
- use -std=c++11 instead of -std=gnu++11
- applied a few patches from Debian upstream to make their packaging job
easier
So because colors are normalized in GLSL, I won't be able to offer video
shaders absolute color literals. We will have to perform basic color
conversion inside the core.
As such, the current plan is to create some sort of Emulator::Settings
interface. With that, I'll connect an option for color correction, which
will be on by default. For FC/SFC, that will mean gamma correction
(darker / stronger colors), and for GB/GBC/GBA, it will mean simulating
the weird brightness levels of the displays. I am undecided on whether
to use pea soup green for the GB or not. By not doing so, it'll be
easier for the display emulation shader to do it.
2013-11-09 11:45:54 +00:00
|
|
|
if (_id < 1)
|
|
|
|
qt_static_metacall(this, _c, _id, _a);
|
2010-09-26 05:09:31 +00:00
|
|
|
_id -= 1;
|
|
|
|
}
|
|
|
|
return _id;
|
|
|
|
}
|
|
|
|
QT_END_MOC_NAMESPACE
|