| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
Only thick rects remain there
|
|
|
|
|
|
Also, hooked the Restore button up to the load dialog
|
|
|
|
hardcoding it
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
In some places we used $DEVKITARM, but in others we hardcode the path
$DEVKITPRO/devkitARM. To ensure consistent behavior, I changed it to the
latter everywhere for now. Should it turn out that we really want to
have this flexible, we can reintroduce $DEVKITARM in a proper way. In
that case, we could augment configure to set DEVKITARM to
$DEVKITPRO/devkitARM, if it has not been set yet.
|
|
So far, the various *-fs-factory.cpp files were #including the
corresponding *-fs.cpp files. This is surprising and hence could lead to
all kinds of problems). To fix this, provide proper headers for the
*-fs.cpp files.
This also makes code reuse via subclassing possible.
Since not all ports were tested, this will likely lead to a few
easy to fix compile regressions.
|
|
|
|
|
|
|
|
synchronisation methods
|
|
|
|
|
|
|
|
|
|
|
|
|
|
screwed due to palette issues
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
