Yi Zhang wrote: > As I editing patches in Patch Edit window, I found 2 bugs in the editor > window.
Only ? :-) Here's more: 3) Open the patch editor on a new file. Hit Enter until you have more than 20 lines. The cursor will happily vanish under the bottom of the window. (Most editor will adjust the scroll bar to keep the cursor visible at all times.) 4) Likewise, when adjusting the scroll bar after 3) and then pressing the up arrow, the cursor will vanish at the top. Same problem. 5) Tabs are shown as little arrow characters, not as tabs. While we're at it, the following usability improvements in the GUI would be nice to have as well: - killing the Performance (compilation progress) window doesn't stop compilation. It continues invisibly and FN goes to performance mode when done, just as if the window was never closed. Such a degree of stubbornness is generally unexpected :-) - a patch with lots of images won't move the progress bar for a good while. Perhaps we can make the progress bar alternate at a few Hz between width(t) and width(t+1). Not sure whether the visual effect would be "right". But it's the least intrusive I could think of. - when starting performance mode and a patch fails to compile, we're informed which patch didn't compile, but not why. One has to go to the patch editor for this bit of information. - in such a situation, it would be nice to be offered the option of skipping the offending patch. E.g., when doing a demo and that last second change didn't go so well. The last four items should only need changes to Flickernoise. The others probably involve changing MTK. - Werner _______________________________________________ http://lists.milkymist.org/listinfo.cgi/devel-milkymist.org IRC: #milkymist@Freenode
