1. IDE bug reports
- Posted by Patrick.Barnes at transgrid.com.au Nov 29, 2002
- 456 views
Must be one of those days.... 1. In the code editor, the text window allows you to select more of the line than exists. i.e.: end procedure ------------------------------------>can select out to here, as long as you want. If you subsequently copy that selection (Ctrl+C), the program dies because the slice looks further than the bounds of the sequence. 2. Every time I press the Delete button, it deletes two chars... One in front of the caret, one behind! 3. Now, my IDE won't run. I think I changed something in the code while looking for a solution to the delete bug. Can someone send me a fresh copy pls? o_O ============================================== _______<-------------------\__ / _____<--------------------__|=== | |_ <-------------------/ \__| Patrick Barnes *********************************************************************** ***********************************************************************
2. Re: IDE bug reports
- Posted by g.haberek at comcast.net Nov 29, 2002
- 474 views
I have a problem with Popups in the IDE. When I make a popup menu, I can only have the menu and 3 items, after that I get and error: (this is a long one) C:\EUPHORIA\include\win32lib.ew:16109 in function deleteItem() subscript value 96 is out of bounds, reading from a sequence of length 95 id = 262 pos = 96'`' msg = 4353 lParam = 0 iItem = 0 ... called from C:\Euphoria\ide\ide_projectview.ew:595 in procedure deleteTreeViewNode() parent = {} child = {80'P',111'o',112'p',117'u',112'p',73'I',116't',101'e',109'm', 95'_',49'1',48'0',52'4'} t1 = {} t2 = {80'P',111'o',112'p',117'u',112'p',73'I',116't',101'e',109'm', 95'_',49'1',48'0',52'4'} idx = <no value> parentidx = -1 x = 93']' ok = <no value> i = 96'`' ... called from C:\Euphoria\ide\ide_popup.ew:460 in procedure savethepopup() treedata = {{80'P',111'o',112'p',117'u',112'p',73'I',116't',101'e', 109'm',95'_',49'1',48'0',51'3'},{80'P',111'o',112'p',117'u',112'p',73'I', 116't',101'e',109'm'}} parent = {80'P',111'o',112'p',117'u',112'p',95'_',49'1',48'0',49'1'} startAt = 70'F' i = 73'I' i = 70'F' i = 73'I' ... called from C:\Euphoria\ide\ide_popup.ew:998 in procedure PopupEditOk_Click() self = 598 event = 4 params = {} ... called from C:\EUPHORIA\include\win32lib.ew:7773 in function invokeHandler() id = 598 event = 4 params = {} lRoutines = {{232}} lCallType = 1 i = 1 j = 1 ... called from C:\EUPHORIA\include\win32lib.ew:21762 in procedure wmCommand() id = 598 hWnd = 1564 iMsg = 273 wParam = 0 lParam = 3188 event = 0 w32event = 4 parms = {} ... called from C:\EUPHORIA\include\win32lib.ew:22556 in function fDoCommand() id = 584 hWnd = 1564 iMsg = 273 wParam = 0 lParam = 3188 pReturn = -2761 lRC = {-9987} lChildId = 598 ... called from C:\EUPHORIA\include\win32lib.ew:23362 in function MessageProcessor() pSource = -2761 hWnd = 1564 iMsg = 273 wParam = 0 lParam = 3188 id = 584 lHandledEvent = 15 result = <no value> lUserReturn = 0 ... called from C:\EUPHORIA\include\win32lib.ew:23394 in function WndProc() hWnd = 1564 iMsg = 273 wParam = 0 lParam = 3188 ^^^ call-back from Windows ... called from C:\EUPHORIA\include\win32lib.ew:1086 in function w32Func() funcid = 53'5' parms = {-2143632948,3188,514,0,196641} lRC = <no value> libfunc = <no value> lFuncDef = 31 linked = <no value> memset = 0 i = 5 ... called from C:\EUPHORIA\include\win32lib.ew:23374 in function MessageProcessor() pSource = -9987 hWnd = 3188 iMsg = 514 wParam = 0 lParam = 196641 id = 598 lHandledEvent = 4 result = {-9987} lUserReturn = 0 ... called from C:\EUPHORIA\include\win32lib.ew:23400 in function SubProc() hWnd = 3188 iMsg = 514 wParam = 0 lParam = 196641 ^^^ call-back from Windows ... called from C:\EUPHORIA\include\win32lib.ew:1157 in procedure w32Proc() funcid = 21 parms = {7741544} libfunc = <no value> lFuncDef = 118'v' memset = 0 i = 1 ... called from C:\EUPHORIA\include\win32lib.ew:23570 in procedure eventLoop() id = 0 Flag = -1 msg = 7741544 hWnd = 0 getRC = 1 inc = 0 el = 1 ... called from C:\EUPHORIA\include\win32lib.ew:23705 in procedure WinMain() id = 15 style = 0 ... called from ide.exw:12250 ----- Original Message ----- From: <Patrick.Barnes at transgrid.com.au> To: "EUforum" <EUforum at topica.com> Sent: Thursday, November 28, 2002 7:57 PM Subject: IDE bug reports > > Must be one of those days.... > > 1. > > In the code editor, the text window allows you to select more of the line than exists. > i.e.: end procedure > ------------------------------------>can select out to here, as long as you want. > > If you subsequently copy that selection (Ctrl+C), the program dies because the slice looks further than the bounds of the sequence. > > > 2. > > Every time I press the Delete button, it deletes two chars... > One in front of the caret, one behind! > > > 3. > Now, my IDE won't run. I think I changed something in the code while looking for a solution to the delete bug. > Can someone send me a fresh copy pls? o_O > > ============================================== > _______<-------------------\__ > / _____<--------------------__|=== > | |_ <-------------------/ > \__| Patrick Barnes > > > *********************************************************************** > > > *********************************************************************** > > > >
3. IDE bug reports
- Posted by Patrick.Barnes at transgrid.com.au Dec 10, 2002
- 452 views
In the Code Editor module: 1. When you change the focus to another application, the hint window and the color preferences window stay in the foreground. 2. The color preferences window: If the color chosen is light or white, it is very hard to read the keywords against the white background. Maybe use something like unRgb, and get a brightness value from it to decide whether to use a black or white background. function unRgb(integer color) return { and_bits( #FF0000, color) / (256 * 256), and_bits( #00FF00, color) / 256, and_bits( #0000FF, color) } end function 3. When you type a function out, and the hint window appears, it is moveable. So, you move it away from where you are typing in order to see better. When you have finished typing the function it disappears. When you start another function call, it reappears again; not where you left it, but where it first appeared: in the way. ======================= Patrick Barnes Information Systems Group 201 Elizabeth St, Sydney Patrick.Barnes at tg.nsw.gov.au Ext: 91-3583 Ph:(02) 9284-3583 Mob: 0410 751 044 *********************************************************************** ***********************************************************************
4. Re: IDE bug reports
- Posted by Dan Moyer <DANIELMOYER at prodigy.net> Dec 12, 2002
- 472 views
Judith, I think he meant that if the user selects a font color, the IDE should automatically select a background color that will at least make sure that the text can be seen, before user selects a background color. Dan Moyer ----- Original Message ----- From: "Judith Evans" <camping at txcyber.com> To: "EUforum" <EUforum at topica.com> Subject: RE: IDE bug reports > > > Patrick.Barnes at transgrid.com.au wrote: > > In the Code Editor module: > > > > 1. When you change the focus to another application, the hint window and > > the color preferences window stay in the foreground. > > The color preferences window has been changed from TopMost. It was Modal > anyway so didn't need the TopMost style. > > I'll work on the hint window. > > > > > 2. The color preferences window: If the color chosen is light or white, > > it is very hard to read the keywords against the white background. Maybe > > use something like unRgb, and get a brightness value from it to decide > > whether to use a black or white background. > > > > function unRgb(integer color) > > return { > > and_bits( #FF0000, color) / (256 * 256), > > and_bits( #00FF00, color) / 256, > > and_bits( #0000FF, color) > > } > > end function > > I'm not sure I follow. Is your editor window also white? If so then use > the 'Background' selection and change your editor background to > something the keyword colors will show up against. > > > > > 3. When you type a function out, and the hint window appears, it is > > moveable. So, you move it away from where you are typing in order to see > > better. When you have finished typing the function it disappears. When > > you start another function call, it reappears again; not where you left > > it, but where it first appeared: in the way. > > Yeah I know. I couldn't figure out how to make it go back where you had > placed it. I think I overlooked a routine Martin Stachion sent me once > that might do the trick, however. > > > Thanks for the bug report, > --judith > > > > > ======================= > > Patrick Barnes > > Information Systems Group > > 201 Elizabeth St, Sydney > > Patrick.Barnes at tg.nsw.gov.au > > Ext: 91-3583 > > Ph:(02) 9284-3583 > > Mob: 0410 751 044 > > > > > > *********************************************************************** > > > > > > *********************************************************************** > > > > > > >