1. Cuny's Text GUI minor cosmetic bug
- Posted by "JesusC - (Jesus Consuegra)" <jconsuegra at REDESTB.ES> Dec 30, 1997
- 648 views
When using a 50 line screen, after running a program from inside the EE editor, the message asking for a key to continue, does appear at the 24 (or 25) line, and should be at the bottom of screen. (Not new, neither annoying, but I've thought I should report it...). Jesus. (Again, twice today!).
2. Re: Cuny's Text GUI minor cosmetic bug
- Posted by David Cuny <dcuny at DSS.CA.GOV> Dec 30, 1997
- 627 views
Thanks, I just saw that the other day. It'll go on my 'to do' list. Most of the time, I stay out of alternate screen resolutions, so I tend not to see bugs associated with that. The fix is trivial (just check the screen resolution, and use that value). I should be posting a number of fixes some time after New Year's. -- David Cuny
3. Re: Cuny's Text GUI minor cosmetic bug
- Posted by David Cuny <dcuny at DSS.CA.GOV> Dec 30, 1997
- 630 views
I just took a look at my code, and it already checks for screen resolution. Apparently, Euphoria is unable to detect the screen resolution unless it has been set by the current program. I ran into a similar problem with trying to save screen shots when the screen was left in graphics mode. Apparently, Euphoria does not actually ask the VGA what the current graphics state is - it just checks an internal flag. So if the Euphoria program that you've shelled to changes the screen resolution, the calling Euphoria program is unable to detect the change, and thus incorrectly reports the current screen mode. Is this correct, Robert? Or am I being dense here? The only "fix" I can think of under these circumstances is to put the "Press a Key" message at the top of the screen... -- David Cuny
4. Re: Cuny's Text GUI minor cosmetic bug
- Posted by Robert Craig <rds at EMAIL.MSN.COM> Dec 30, 1997
- 616 views
David Cuny writes: > So if the Euphoria > program that you've shelled to changes the screen resolution, > the calling Euphoria program is unable to detect the change, > and thus incorrectly reports the current screen mode. That's true. It's due to something in WATCOM's graphics library. I can't easily fix it. That's why system() has a second argument that allows you to restore your original graphics mode after running a program that might change the mode. To avoid problems, system("xxx", 0) or system("xxx", 1) should be used whenever xxx might possibly change the graphics mode. If you are sure that xxx will not change the mode then use system("xxx", 2). Regards, Rob Craig Rapid Deployment Software
5. Re: Cuny's Text GUI minor cosmetic bug
- Posted by "JesusC - (Jesus Consuegra)" <jconsuegra at REDESTB.ES> Dec 31, 1997
- 655 views
I've found something on this: I run Euphoria under Win/NT 4.0. If I configure the DOS box as 80x50 (both scroll buffer and window) permanently, and I also configure EE to 50 lines, everything is okay. If I only configure the DOS box is when the problem arise. I've got another problem with EE. (I use it bound as EE.EXE, with bind, not bindw, and EE.EXE is in %EUDIR%\BIN). I was trying the nice ModeX demo from Pete Eberlain (that will hopefully solve my Screen Saver problem, thanks to everybody...). I edit Demo.ex to change parameters, (i.e. # of balls). If I try to run or bind it from inside EE, I get an error: "Attempt to subscribe an atom" on one early line: "constant spheres = virtual_screen(length(bmp[2][1]), length(bmp[2]))" that is okay, since the program runs well outside EE... Best wishes for 1998, 1999, 2000.... JesusC-Euphorian-forever. ---------- > De: JesusC - (Jesus Consuegra) <jconsuegra at REDESTB.ES> > A: Multiple recipients of list EUPHORIA <EUPHORIA at MIAMIU.ACS.MUOHIO.EDU> > Asunto: Cuny's Text GUI minor cosmetic bug
6. Re: Cuny's Text GUI minor cosmetic bug
- Posted by Pete <xseal at HARBORSIDE.COM> Dec 31, 1997
- 629 views
JesusC - (Jesus Consuegra) wrote: > > I was trying the nice ModeX demo from Pete Eberlein (that will hopefully > solve my Screen Saver problem, thanks to everybody...). > I edit Demo.ex to change parameters, (i.e. # of balls). If I try to run or > bind it from inside EE, I get an error: > > "Attempt to subscribe an atom" > > on one early line: > > "constant spheres = virtual_screen(length(bmp[2][1]), length(bmp[2]))" Whoops. My fault here. I am very lazy when it comes to error checking. The problem is a few lines earlier when I try to read in the bitmap "spheres.bmp". I made no check to see if bmp is actually loaded, in the case that it isn't bmp is an atom, not a sequence. "spheres.bmp" needs to be in the same directory that "demo.*" is executed in. Sorry about this. > that is okay, since the program runs well outside EE... > > Best wishes for 1998, 1999, 2000.... > > JesusC-Euphorian-forever. -- _____ _____ _____ ________ /\ \ /\ \ /\ \ / \ \ / \____\ / \____\ / \____\ / _ \____\ / / ___/_ / /____/ / / ___/_ / / \ |____|/ / /\____\ / \ \ / / /\____\ \ \_/ / / \ \/ / ___/_\ \ \ \ \/ / ___/_ \ /____/ \ / /\ \\/\ \ \ \ / /\ \ \ \ \ \ \/ \____\ \ \ \ \ \/ \____\ \ \ \ \ / / \ \____\ \ / / \ \____\ \ / / \ / / \ / / \ / / \ / / \/____/ \ / / \/____/ \/____/xseal at harborside.com\/____/