Post by nyxojaele on Jan 24, 2010 10:12:16 GMT -5
I've got a couple issues/suggestions, and 1 potential bug with the GPU debugging available in pSX.
1) Allow resizing of the split containers in the GPU window- quite often I find myself looking at the raw data (bottom right) and just want to extend it to fill most of the right side of the GPU window, but can't.
2) Fix the scrollbar of the raw data view in the GPU window. Any large amount of data in that part of the GPU window (enough to require a scrollbar) will create a scrollbar that doesn't function properly- the bottom of the scroll bar is somewhere way past the bottom of the window, so the down arrow can't be seen, and the bar can be dragged past the bottom of the window.
3) Don't un-hilite data in the raw data section of the GPU window when the pSX debugger loses focus. Quite often, I'll select a row (Ideally I'd wanna select a byte, but pSX doesn't support that!) to mark a place I'm looking at, but when I bring a different window to focus, pSX unhilites the row I had hilited, and so I find I've "lost my spot," even if I refocus the pSX debugger.
This last bit may not actually be a bug, but it appears that it could be, and it's making things quite difficult for me if it actually is~
In the GPU window, for some items on the left view, you can click on them to bring up some extended info in the top right part of the window- one piece of info being a PC address with close relation to the DMA commands set (The point where the command was set?). There are at least 2 other DMA commands (and likely more, but I only ever need these 2) where this doesn't occur, and it makes tracing stuff back quite difficult:
I'm not sure if it would be possible, but it would be extremely useful, at least for me, if I could see which PC addresses were setting these DMA commands.
1) Allow resizing of the split containers in the GPU window- quite often I find myself looking at the raw data (bottom right) and just want to extend it to fill most of the right side of the GPU window, but can't.
2) Fix the scrollbar of the raw data view in the GPU window. Any large amount of data in that part of the GPU window (enough to require a scrollbar) will create a scrollbar that doesn't function properly- the bottom of the scroll bar is somewhere way past the bottom of the window, so the down arrow can't be seen, and the bar can be dragged past the bottom of the window.
3) Don't un-hilite data in the raw data section of the GPU window when the pSX debugger loses focus. Quite often, I'll select a row (Ideally I'd wanna select a byte, but pSX doesn't support that!) to mark a place I'm looking at, but when I bring a different window to focus, pSX unhilites the row I had hilited, and so I find I've "lost my spot," even if I refocus the pSX debugger.
This last bit may not actually be a bug, but it appears that it could be, and it's making things quite difficult for me if it actually is~
In the GPU window, for some items on the left view, you can click on them to bring up some extended info in the top right part of the window- one piece of info being a PC address with close relation to the DMA commands set (The point where the command was set?). There are at least 2 other DMA commands (and likely more, but I only ever need these 2) where this doesn't occur, and it makes tracing stuff back quite difficult:
- loadimage (this only sends xy and wh info to the GPU)
- dma (immediately after a loadimage call- this would contain the "loadimage data" section)
I'm not sure if it would be possible, but it would be extremely useful, at least for me, if I could see which PC addresses were setting these DMA commands.