It's still broken; just not as much as before. So you should still
compile in debugger support for now. This will probably involve
moving around some classes in the codebase, such as all GUI related
classes used by the debugger will go in 'debugger/gui'.
Sorry for any inconvenience this may cause, but the debugger
support has almost doubled the size of the executable, and there
are some platforms that can neither use it nor deal with its overhead.
git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@740 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
$F000 to $FFFF.
Updated both debugger disassemble() methods to never pass $FFFF
when disassembling data.
git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@739 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
isn't very useful, only disassembles addresses 0-2048, and doesn't
seem to look right :)
git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@738 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
Added ability to use either software or hardware SDL surfaces in
FrameBufferSoft. So now there are potentially 3 video modes to
choose from: "Software (S)", "Software (H)", "OpenGL", selected
by -video 'soft', 'hard', 'gl' respectively.
Made 'directx' and 'hard' the default for Win32. Windowed
software/hard surface mode is now much closer in performance to
software/soft surface in Linux. Really ironic that software
mode in Linux performs so well, and in Windows so poorly.
Fullscreen software/hard surface in Windows is borked ATM, but I'm
pretty sure I can fix it.
Updated the VS.net project file.
git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@736 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
need to be refilled or a line has been (un)checked. Also, checked
lines are now shown correctly (scrolling the list scrolls the
checkboxes as well).
Added two different styles to CheckboxWidget. The first is as before,
but the new one doesn't draw the surrounding box and fills with a
solid color instead of using 'X'. Methods have been added to
set/unset drawing of the surrounding box, and change to doing a fill
vs using the 'X'.
git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@735 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
to anything yet. I may add the ability to CheckboxWidget to disable
drawing the surrounding border, as well as drawing a fill as well
as a bitmap. When that's done, click a breakpoint in RomWidget will
show (for example) a red square only, which is more like how
other graphical debuggers show a breakpoint.
git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@733 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
StringListWidget and CheckListWidget to extend from it. This means the
derived classes can concentrate on their main purpose, and leave all
the ListWidget stuff to the parent class.
Turned the TIA debugger area into an absolute size; 320x260. This
should be large enough to accommodate all PAL ROMS. This means the
tabset got shorter, but it's just too difficult to add widgets when
the area can change. A zoom widget is going to be added to the right
of the TIA image, and we need absolute sizes for that area.
Besides, now that area is usable for other widgets ...
git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@732 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
CheckListWidget, but that widget is not yet complete either. Eventually
the CheckListWidget will derive from ListWidget, and the RomWidget
will contain context menus, etc. For now, it doesn't do anything :)
git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@731 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
go in the savefile, not their Expression pointer addresses :)
Also, we no longer attempt to save the builtin functions.
git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@730 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
next to each other, and their contents are shown as output to the
screen (serialized from TIA), *NOT* how the bits are actually
stored in the PF registers.
git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@729 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
required infrastructure won't be complete for the next release.
The checkboxes are now read-only, so the collision bits can
still be seen (but not changed).
Refactored ToggleBitWidget into a new ToggleWidget class. Added
new classes ToggleBitWidget and TogglePixelWidget, which derive
from ToggleWidget. ToggleBitWidget works as before.
TogglePixelWidget works much the same as ToggleBitWidget, but
instead of drawing text, it fills a block with color. Also,
it doesn't support change-tracking.
Modified grP0 and grP1 TIA registers in TIA tab to be
TogglePixelWidgets. Now when these registers change, you
can see line by line how the graphics are drawn. Thanks to
Brian for the advice; I had to add this because it's just
too cool :)
git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@728 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
and a set of checkboxes to TiaWidget to toggle each bit. I've
confirmed that the code correctly changes the bits, but I haven't yet
found a ROM where changing these quantities has a noticable effect
on the TIA image. Brian, should we be seeing anything here, or
should the collision register bits be for info only (or am I
doing something wrong)?
git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@725 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
Modified NUSIZx register query, adding methods to set various bits
in those registers (nusizP0(), nusizM0(), etc). Updated the P0/P1
TIA tab registers to use those new methods.
Fixed some bugs in TIADebug when accessing bits 4-5 in NUSIZ0/1
and CTRLPF registers.
Still TODO is collision stuff and PF0/1/2 registers.
git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@722 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
Made posP0(), posP1() writable. This may be the wrong way to do it...
git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@721 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
return key to toggle a selected checkbox). Generally cleaned up
the CheckboxWidget class, so that it centers vertically based on
box/font size, and correctly determines its own size.
Added all P0/P1 info from 'tia' command to the TIA tab. Some work
is still required on the NUSIZx registers, though. I expect the
remainder of the TIA tab will be completed quickly, now that most
of the infrastructure is in place. Still TODO is add methods to
TIADebug to enable/disable collisions.
git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@720 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
Removed 4-line prompt output, since most of the info is available from
the main debugger area and always visible.
Some rearrangement of TiaDebug code, and added GRP0 register to TIA
tab (currently display only, it doesn't update the value).
git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@719 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
They're now in separate widgets, and must be tabbed/selected
separately.
Related to above, made the CPU PC widget hold 16bit values and be
wide enough to hold 16 digits (binary mode). Also, made the other
registers in CpuWidget be 8bit only.
Removed frame around a cell when a DataGridWidget or ToggleBitWidget
loses focus. It's obvious when a widget isn't in focus
(there's no bounding rectangle around the whole thing), so another
visual indicator wasn't really required.
git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@718 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
Changes highlighting of searched RAM from a framed rectangle to coloring
the cell text.
Removed CheatWidget, since its entire functionality is now handled by
RamWidget buttons.
Next up is the TIA tab (I really hate having to touch that one ...)
git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@717 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
The latter three completely replace the functionality of the CheatWidget,
so it will soon disappear.
The results of a RAM search are indicated by a blue frame around a cell.
Compare still isn't working, but I know how to fix it.
Made EditableWidget a CommandSender, and have it send signals when
data entry is complete or cancelled.
Some API cleanups in FrameBuffer/DialogContainer wrt refreshOverlay()
and refreshTIA().
git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@716 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
debugger area. Also, this group of buttons now works on either
the CPU registers or RAM area, depending on which one is currently
in focus. When not focused on either of those, the buttons are
disabled.
Moved the CpuWidget and RamWidget to the left as far as possible.
I'm planning to add the RAM 'Search', 'Compare', 'Restart', 'Undo'
and 'Revert' buttons to the space on the right. We're really
squeezing the interface as much as possible here :)
git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@715 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
operations buttons. I'm probably going to make this another widget,
and have it act on either CpuWidget or RamWidget, whichever is
currently in focus.
git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@714 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
widgets in a TabWidget, which is also in the dialog. All focus
related issues are now handled by the base Dialog directly; TabWidget
exits only to show a different set of widgets based on which tab
is selected. Still TODO is fix drawing of focus rectangle around
some widgets (specifically, those that have a scrollbar attached).
Moved CpuWidget into the main dialog area, so it's always visible.
Next I'll be moving the RamWidget to the main dialog, and combining
CheatWidget into it to save even more space.
Then, we can get back to work on the TiaWidget and RomWidget :)
git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@713 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
work: clicking "Load" loads the code "db000f" (no walls, in Pitfall).
Once loaded, you can enable and disable it with the checkbox.
I was going to add text entry and list widgets tonight, but I'm starving
and out of food, and should probably go eat... so tonight's nightly build
is going to be kind of a tease :)
git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@712 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
only redraws itself when updating, instead of requiring the dialog
below it to redraw as well. Related to this, adding a dialog
box on top of another no longer requires a restack and redraw
of other dialog boxes beneath it.
Fixed some dirty update problems with dialog boxes; they weren't
setting dirty rects, hence in some cases weren't being redrawn.
Updated debugger to be 1024x7xx pixels, and partitions the debugger
into separate 'areas'. The next step is to fill these areas,
starting with moving the CpuWidget and RamWidget onto the main
area (so they're always visible).
git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@711 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
This is a space-saving measure, so that input boxes don't have to
be onscreen until they're needed (and go away otherwise).
Partially ported CheatWidget to use an InputTextWidget. I'm not
doing any more work on CheatWidget, since it's going to disappear
(will be integrated directly into RamWidget).
git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@710 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
forces a redraw of the whole parent dialog (this is a big optimization
in the case of the DebuggerDialog, since it will soon have a
resolution of 1024x768).
Made the TiaOutputWidget act as a dirty rect, and only redraw itself
when necessary.
Fixed selection of items in TabWidget which have the
WIDGET_TAB_NAVIGATE property. Clicking them with the mouse now
correctly selects them (and deselects other widgets in that chain).
Still TODO here is have the TabWidget draw the outline around such
widgets itself, so that when one is selected and the others
deselected, only the outlines need to be redrawn (vs. the whole tab).
Removed FrameBuffer::blendRect(), since the GUI code will never
have blended rectangles (it would cause to much complexity in the
dirty update/rectangle code).
git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@709 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
one we'll use yet.
More layout issue fixes. When I changed the debugger fonts, everything
was redrawn correctly (just smaller). This is exactly what should
happen, and is a good first step to making the GUI be font-size aware.
Added change tracking to the CPU PS register (ToggleBitWidget).
git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@708 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
Eventually, the debugger GUI will support multiple fonts, and the
layout will automatically resize itself.
(Hopefully) fixed bug whereby pressing '~' would not exit the debugger.
Small performance improvement to OpenGL GUI mode. No redraws will be
done if no widget has been changed, but if any changes must be made,
the whole screen is redrawn. So it's partial support for dirty updates.
git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@707 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
this means the text is pretty huge.
The 9x15 X font, BTW, is public domain.
git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@706 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
out of sync. Implemented dirty widget support for the GUI. That
means the widgets will only be drawn when necessary. There are still
a few gotcha's:
1) OpenGL mode hasn't been ported to this new scheme.
2) It's not totally finished, so some artifacts may appear onscreen.
3) Selecting active widgets with the mouse is borked.
4) Prompt commands that change the core aren't shown in the other
tabs/interface. Fixing this will require some infrastructure work
in Debugger and DebuggerParser.
5) A lot of print debug code has been left in; please ignore it for now.
Moved a lot of the debugger widgets to use non-proportional font (still
TODO is get a larger font) and not use 'magic numbers' for the layout.
That means when a new font is added, the layout should re-arrange itself.
Moved various Debugger tab widgets from 'src/gui' to 'src/debugger',
because they shouldn't be compiled when debugger support isn't
included. So now (for example), RamWidget and RamDebug are both in
the debugger directory.
Probably more stuff I'm forgetting about. It looks like the ScummVM
code can be made adequately fast, so the jump to Qt won't be necessary.
git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@705 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
or on the command line. See http://members.cox.net/rcolbert/ for details.
Cheetah codes are cool, but all they can do is modify ROM. We'll also be
adding some sort of extended Stella cheat code support to allow modifying
RAM, either once or once per frame, like the Game Genie does on an NES.
Most likely the actual codes will resemble Bob's codes, but with extra
digits. Unfortunately there won't be an easy way for the real Cheetah
to support these extended codes :(
git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@704 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
expect the 'net will be flooded with hacked versions of Battlezone that
give you infinite lives :)
git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@702 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
Every cart type is going to have to support this by having a getImage()
method that returns the size of and pointer to its internal ROM image
array. Currently only Cartridge4K supports it, but it does work.
git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@700 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
common conditions such as "joystick 0 pressed to the left" (this would
be "_joy0left"). To see the list, type "help".
git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@699 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
a modifier (such as Shift). This allows us to actually type a ~ character
in the debugger (our unary NOT operator!).
git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@695 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
...but we need them in the Expression classes and the DebuggerParser.
Expressions now return uInt16 instead of int. This gets us 6502-like
behaviour when dealing with numbers that don't fit into the 6502's 16-bit
address space. -1 in 6502-speak is equal to $ffff (twos' complement); this
is exactly what happens in C++ if you try to assign -1 to an unsigned
short (aka a uInt16). I believe the C++ standard doesn't *require*
conforming implementations to use twos' complement math, but I doubt
anyone will ever port Stella to any hardware old or esoteric enough to
use anything else.
Also, I've added casts to uInt8 to the debugger commands that set
registers. This also results in 6502-like handling of negative numbers:
using "a -2" to set the Accumulator will result in it having the value
$fe, which is exactly correct for a 6502. This may seem like undesirable
behaviour (and in a regular C++ program, when it happens by accident,
it IS undesired), but trust me, this is exactly what a 6502 assembly
programmer would expect.
Also also, I got rid of the distinction between commands that take a byte
or word argument. They all take words now. I had to do this to make the "a
-2" example work. A side effect is that you can now say something like "a
$1234" and the value will get truncated to $34 (due to the cast to uInt8).
What remains to be seen is whether all this behaves the way I think it
should on a big-endian platform (e.g. the Mac). My poor Mac is having
cooling issues, so I can't actually compile Stella any more :(
However, I can get it to run long enough to compile a little 5-10
line test program to see how these casts work. If I'm wrong, and they
behave differently on the Mac, I'll have to add platform-dependent
"uInt16_to_uInt8" type functions, which I'd really rather avoid...
But the debugger has GOT to treat negative and out-of-range values the
same way as a 6502 does.
git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@694 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
In the process, I've discovered a bug in the argument processing: any of
the commands that use kARG_FILE as their first argument will work *only*
if they're the first command issued after starting Stella, otherwise
they segfault. Am investigating this now
git-svn-id: svn://svn.code.sf.net/p/stella/code/trunk@691 8b62c5a3-ac7e-4cc8-8f21-d9a121418aba
stephena