On Sat, Feb 02, 2002 at 02:38:24PM -0700, Micah Dowty wrote: > On 2002.02.02 03:10 Dave Poirier wrote: > >I haven't been with PicoGUI for long, but I must say I really > >appreciate > >the way it works and its current status, very nice small product :) > > Glad you like it :) > > > > >The terminal is though, quite strange. I seem to have a 300 lines > >terminal, whatever what I do. This means that if I start up vim, the > >status line will be displayed on the 300th line and if I press page > >down > >it gets down 297 lines. Problem is, that only like 40 or so lines can > >be displayed at any one time in the visual graphic window. > > Um... yeah, this is a known bug in the terminal widget. I just haven't > had time to fix it. Right now it implements scrollback by setting the > terminal height to 300 lines and attaching a scrollbar to it. What > really needs to happen, is instead of setting PG_WP_LINES on the > scrollbar we set a new property that sets just the scrollback lines, > not the total lines. > > > > >terminals have, by history, had scrollback buffers, but never was the > >entire scrollback buffer space been seen as an entire viewable > >terminal. > > right > > > > >is there any option to control how many lines are viewable on screen, > >set this number of lines to best fit the current window size and > >control > >how many lines are kept in the buffer? > > Yep, we need a new widget property for that > > > > >ls and most other ocmmand line utility don't suffer from this, but any > >ncurset tool will most likely suffer, including mutt, vim, cftp and a > >couple of others. > > For now, you can comment out the line of code in pterm that sets > PG_WP_LINES. What we actually need is to turn that 'font' button on the > panelbar into a menu, where the user can set the scrollback length and > font. > > You'll also notice that the VT-100 emulation on the terminal is > generally in need of some help. It will run simple things, like > busybox's 'vi', but ncurses apps almost always break it due to > unimplemented escape codes. There's a debug option in pgserver to have > the terminal print all unknown escapes.
Ok, it was more of knowing the status on that than any urgent dev. If I ever get bored of working on my current project I might look into that and try to give you guys a hand. Thanks for the detailed answer :) -- EKS - Dave Poirier ([EMAIL PROTECTED]) "may the hairs on his toes never fall out" http://uuu.sf.net/ _______________________________________________ Pgui-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/pgui-devel
