Re: small gpsim feature requests

"Scott Dattalo" <[email protected]>
Newsgroups gmane.comp.hardware.microcontrollers.gnupic
Message-ID <[email protected]>
On Fri, 2005-09-02 at 10:34 +1200, David McNab wrote:

> Hi Scott et al,
>
> Firstly, thanks again for fixing the 'over' command so that it now works
> with 'call'.

David,

Sorry for the late response - I received this just before going out of
town last weekend and have been busy/pre-occupied since.


> Now, a couple of smaller requests:
>
>  - in the source display window, any chance of you adding a handler
>    for mouse wheel events in the main pane, so I can scroll using the
>    wheel without having to position the mouse cursor over the right-hand
>    scrollbar widget?

This bug appeared when gpsim started linking against gtk-2.X. This used to
work in gtk-1.2.X. I've only briefly looked into the cause, but I'll give
it some more priority.


>  - in the register display window:
>
>      - among the bottom edge labels/fields for 'PC', 'status', 'W'
>        and 'bsr', please consider adding additional labels/fields
>        for the STATUS bits 'Z', 'N', 'C', 'OV' and 'DC'. (Yeah, I
>        know, I should have memorised all the status bit positions
>        by now, sorry)

Yes, I've thought about this - though not the way you're suggesting. A
while back I made the status bar a dynamically configurable (at compile
time) widget. This is how the BSR get's placed there for the 18f devices.
I was thinking about creating bit field items for the status bar and
placing the STATUS register bits in there.


>      - please reinstate the left-edge labels showing the register
>        addresses - the 0x00, 0x10, 0x20 etc

This bug is due to gtk-extra. I've contacted Adrian (the maintainer og
gtk-extra) but he hasn't/can't fix this.


>      - the blue highlighting of register cells upon a write to that
>        register is great - but it would be really nice if this
>        wasn't limited to cases where register has changed value.
>        It's often helpful to know when a register with value 0x00
>        has been overwritten with 0x00 (eg, when watching stack
>        usage).

Would another color perhaps be useful to differentiate change vs. access?

Scott
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.