In message <[EMAIL PROTECTED]>, Ralf Reköndt <[EMAIL PROTECTED]> writes
>Hi Malcolm, > >I know about hard coding, but the code was written to be most universal for >output in channels. Perhaps not so "clean" ;-). The lines are linked lists >in memory. The lines marked as blocks get a flag, and the output routine >reads the flag from memory and sets the ink by itself. At QL times, black >paper and white ink was the most used colors in editors, so there was no >need to make it configurable. > >To make a quick&dirty solution, I can assemble a version for you with the >supposed colors, no problem. Until I find a safe and clean way to let the >user configure it. There are a lot of other things, I want to do, ie use >Menu Extensions if present, a bar at the left side to let the user see, >where he is navigating, user defined x and y position at start-up and Resize >in steps (it is no pointer program). > >Cheers...Ralf R. OK, thanks for the "quick and dirty" solution ... send me a zip file whenever you can. Yes, adding the Menu Extensions is of course the other "opus" that can work on ... :-) >----- Original Message ----- >From: "Malcolm Cadman" > >Thanks, Ralf. > >When you get time to think about it .... :-) > >Hard coding values always has its drawbacks as well as advantages. > >The editors that I use regularly are the Editor 2000 and MicroEmacs v4, >both of which are set up with a black background, green ink, and the >cursor is red. > >All of this with a QPC2 window in Windows. > >MicroEmacs is the most impressive, as its uses the full screen, has >drop-down menus with the pointer environment, and its active with >FileInfo2. > >Although, it too is showing its age, and could do with a GD2 colour >re-vamp and other features ... > >Sedit is nice too, and as I get used to it more it will get used. -- Malcolm Cadman _______________________________________________ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
