1. Enhanced IDE
- Posted by Mike777 <anon4321 at g?ail.c?m>
Jan 21, 2008
-
Last edited Jan 22, 2008
This is primarily intended for Judith, but if anybody else has any input, that
would be fine with me.
I seem to have run into a repeatable circumstance where code is obliterated.
I'm not sure I can create a small repeatable example, but here is the code that
will do it at my end. Take a normal text box and look at the onKeyUp event.
Code it with:
w32VOID=message_box(sprintf("The value of the key is:[%14.6f]",params[1]),"",0)
Then run the program and input something which will cause a crash. On my
system, that is just typing C twice.
When you go back and look at the onKeyUp event in the IDE, it will be gone.
I mention this not because I'm losing one line of test code. I mention this
because after a crash, the routine that was in the process of executing is
sometimes obliterated. It happened to me a couple of times with a
Window/[General] code block [a BIG one]. When that happened, I was not very
happy. But since I couldn't reliably replicate it and it happened so
infrequently, I just implemented a "save the project file frequently" habit and
went about my way.
Now that I can reliably reproduce a code obliteration, I thought the least I
could do is to mention it here so that if somebody wants to spend the time to
track down the bug, they can and maybe more importantly, to encourage backing up
the prj file "just in case."
Mike
2. Re: Enhanced IDE
Mike777 wrote:
>
> This is primarily intended for Judith, but if anybody else has any input, that
> would be fine with me.
>
> I seem to have run into a repeatable circumstance where code is obliterated.
> I'm not sure I can create a small repeatable example, but here is the code
> that will do it at my end. Take a normal text box and look at the onKeyUp
> event.
> Code it with:
>
> w32VOID=message_box(sprintf("The value of the key
> is:[%14.6f]",params[1]),"",0)
>
> Then run the program and input something which will cause a crash. On my
> system,
> that is just typing C twice.
>
> When you go back and look at the onKeyUp event in the IDE, it will be gone.
>
> I mention this not because I'm losing one line of test code. I mention this
> because after a crash, the routine that was in the process of executing is
> sometimes
> obliterated. It happened to me a couple of times with a Window/[General] code
> block [a BIG one]. When that happened, I was not very happy. But since I
> couldn't reliably replicate it and it happened so infrequently, I just
> implemented
> a "save the project file frequently" habit and went about my way.
>
> Now that I can reliably reproduce a code obliteration, I thought the least I
> could do is to mention it here so that if somebody wants to spend the time to
> track down the bug, they can and maybe more importantly, to encourage backing
> up the prj file "just in case."
>
> Mike
Mike,
Really not sure if this is relevant, but maybe *how* you run the program from
within the IDE might relate to the problem? F6 (temporary run) vs F5 (run) ?
Dan Moyer
3. Re: Enhanced IDE
Dan Moyer wrote:
>
> Mike777 wrote:
> >
> > This is primarily intended for Judith, but if anybody else has any input,
> > that
> > would be fine with me.
> >
> > I seem to have run into a repeatable circumstance where code is obliterated.
> > I'm not sure I can create a small repeatable example, but here is the code
> > that will do it at my end. Take a normal text box and look at the onKeyUp
> > event.
> > Code it with:
> >
> > w32VOID=message_box(sprintf("The value of the key
> > is:[%14.6f]",params[1]),"",0)
> >
> > Then run the program and input something which will cause a crash. On my
> > system,
> > that is just typing C twice.
> >
> > When you go back and look at the onKeyUp event in the IDE, it will be gone.
> >
> > I mention this not because I'm losing one line of test code. I mention this
> > because after a crash, the routine that was in the process of executing is
> > sometimes
> > obliterated. It happened to me a couple of times with a Window/[General]
> > code
> > block [a BIG one]. When that happened, I was not very happy. But since I
> > couldn't reliably replicate it and it happened so infrequently, I just
> > implemented
> > a "save the project file frequently" habit and went about my way.
> >
> > Now that I can reliably reproduce a code obliteration, I thought the least I
> > could do is to mention it here so that if somebody wants to spend the time
> > to
> > track down the bug, they can and maybe more importantly, to encourage
> > backing
> > up the prj file "just in case."
> >
> > Mike
>
> Mike,
>
> Really not sure if this is relevant, but maybe *how* you run the program from
> within the IDE might relate to the problem? F6 (temporary run) vs F5 (run)
> ?
>
> Dan Moyer
Dan, thanks for the reply. I almost always run from F5. Is that your preferred
method? In any event, when I get a moment, I'll try reproducing the issue and
then substituting F6 to see if it presents a different result.
Mike
4. Re: Enhanced IDE
Mike777 wrote:
>
> Dan Moyer wrote:
> >
> > Mike777 wrote:
> > >
> > > This is primarily intended for Judith, but if anybody else has any input,
> > > that
> > > would be fine with me.
> > >
> > > I seem to have run into a repeatable circumstance where code is
> > > obliterated.
> > > I'm not sure I can create a small repeatable example, but here is the
> > > code
> > > that will do it at my end. Take a normal text box and look at the onKeyUp
> > > event.
> > > Code it with:
> > >
> > > w32VOID=message_box(sprintf("The value of the key
> > > is:[%14.6f]",params[1]),"",0)
> > >
> > > Then run the program and input something which will cause a crash. On my
> > > system,
> > > that is just typing C twice.
> > >
> > > When you go back and look at the onKeyUp event in the IDE, it will be
> > > gone.
> > >
> > > I mention this not because I'm losing one line of test code. I mention
> > > this
> > > because after a crash, the routine that was in the process of executing is
> > > sometimes
> > > obliterated. It happened to me a couple of times with a Window/[General]
> > > code
> > > block [a BIG one]. When that happened, I was not very happy. But since
> > > I
> > > couldn't reliably replicate it and it happened so infrequently, I just
> > > implemented
> > > a "save the project file frequently" habit and went about my way.
> > >
> > > Now that I can reliably reproduce a code obliteration, I thought the least
> > > I
> > > could do is to mention it here so that if somebody wants to spend the time
> > > to
> > > track down the bug, they can and maybe more importantly, to encourage
> > > backing
> > > up the prj file "just in case."
> > >
> > > Mike
> >
> > Mike,
> >
> > Really not sure if this is relevant, but maybe *how* you run the program
> > from
> > within the IDE might relate to the problem? F6 (temporary run) vs F5 (run)
> > ?
> >
> > Dan Moyer
>
> Dan, thanks for the reply. I almost always run from F5. Is that your
> preferred
> method? In any event, when I get a moment, I'll try reproducing the issue and
> then substituting F6 to see if it presents a different result.
>
> Mike
I haven't tried your example, but yes, I do usually use F5 myself, and if the
choice were the problem, I'd have thought F6 would have been it, so I don't
expect you'll find F6 to be a solution. Worth a try, though.
Dan
5. Re: Enhanced IDE
Mike777 wrote:
>
> This is primarily intended for Judith, but if anybody else has any input, that
> would be fine with me.
>
> I seem to have run into a repeatable circumstance where code is obliterated.
> I'm not sure I can create a small repeatable example, but here is the code
> that will do it at my end. Take a normal text box and look at the onKeyUp
> event.
> Code it with:
>
> w32VOID=message_box(sprintf("The value of the key
> is:[%14.6f]",params[1]),"",0)
>
> Then run the program and input something which will cause a crash. On my
> system,
> that is just typing C twice.
>
> When you go back and look at the onKeyUp event in the IDE, it will be gone.
>
> I mention this not because I'm losing one line of test code. I mention this
> because after a crash, the routine that was in the process of executing is
> sometimes
> obliterated. It happened to me a couple of times with a Window/[General] code
> block [a BIG one]. When that happened, I was not very happy. But since I
> couldn't reliably replicate it and it happened so infrequently, I just
> implemented
> a "save the project file frequently" habit and went about my way.
>
> Now that I can reliably reproduce a code obliteration, I thought the least I
> could do is to mention it here so that if somebody wants to spend the time to
> track down the bug, they can and maybe more importantly, to encourage backing
> up the prj file "just in case."
>
> Mike
I can reproduce the crash.
However when I return to Code Editor, I still have the statement in the
w32HKeyUp event. Depending upon your choice from Code Editor Menu Options "When
Changing Control", IDE may have switched you to another event. Please check what
event is showing in the events dropdown combo and if it is the w32HKeyUp and the
body of the editor shows nothing let me know.
Are you using IDEv1.0.3a?
judith
6. Re: Enhanced IDE
Judith Evans wrote:
>
> Mike777 wrote:
> >
> > This is primarily intended for Judith, but if anybody else has any input,
> > that
> > would be fine with me.
> >
> > I seem to have run into a repeatable circumstance where code is obliterated.
> > I'm not sure I can create a small repeatable example, but here is the code
> > that will do it at my end. Take a normal text box and look at the onKeyUp
> > event.
> > Code it with:
> >
> > w32VOID=message_box(sprintf("The value of the key
> > is:[%14.6f]",params[1]),"",0)
> >
> > Then run the program and input something which will cause a crash. On my
> > system,
> > that is just typing C twice.
> >
> > When you go back and look at the onKeyUp event in the IDE, it will be gone.
> >
> > I mention this not because I'm losing one line of test code. I mention this
> > because after a crash, the routine that was in the process of executing is
> > sometimes
> > obliterated. It happened to me a couple of times with a Window/[General]
> > code
> > block [a BIG one]. When that happened, I was not very happy. But since I
> > couldn't reliably replicate it and it happened so infrequently, I just
> > implemented
> > a "save the project file frequently" habit and went about my way.
> >
> > Now that I can reliably reproduce a code obliteration, I thought the least I
> > could do is to mention it here so that if somebody wants to spend the time
> > to
> > track down the bug, they can and maybe more importantly, to encourage
> > backing
> > up the prj file "just in case."
> >
> > Mike
>
> I can reproduce the crash.
>
> However when I return to Code Editor, I still have the statement in the
> w32HKeyUp
> event. Depending upon your choice from Code Editor Menu Options "When Changing
> Control", IDE may have switched you to another event. Please check what event
> is showing in the events dropdown combo and if it is the w32HKeyUp and the
> body
> of the editor shows nothing let me know.
>
> Are you using IDEv1.0.3a?
I'm pretty sure I am. Unfortunately, after I saved the project, exited and came
back, I can no longer replicate it. Don't worry, it will come back relatively
soon and I'll see what I can report.
Best I can tell, the problem comes up when I load a different window. Sometimes
(and I haven't identified exactly when) the loading of a different window causes
one routine or another to disappear. Once that has happened, if I don't
immediately exit I can find the problem like the one I just reported happening.
Of course, to make the system run, I have to restore the lost routine. That just
leaves me in the inconsistent state that allows the above described error,
though.
For example, I have three windows (which you know from before). When switching
from the main window to my secondary window, it will sometimes come up showing
the code for my main window's onOpen routine in the onOpen routine for the
secondary window. Complete with the first line (procedure ....) and the last
line (set handler). When that happens, I can go into a backup and get the code
for the secondary window's onOpen routine and the IDE can create an exw which
will run (not necessarily properly, but it will run). I've got enough going on
in my project now that for it to run means that almost everything is in the right
place. However, when a crash takes place I get strange results, as reported
above.
Of course, the "solution" is to exit immediately after restoring the obliterated
code and come back in, which should at least eliminate the inconsistent state.
But I want to keep the inconsistent state around long enough to give you enough
information to try and figure out what is going on! A definite catch 22, huh?
BTW, I couldn't find "CODE EDITOR MENU OPTIONS". Did you mean "Options
Configure IDE"?
Thanks
Mike
7. Re: Enhanced IDE
Mike777 wrote:
SNIP
> > Are you using IDEv1.0.3a?
>
> I'm pretty sure I am.
Go to IDE "About" Menu. The third line shows the version of IDE you are using.
Also when you start IDE the splash screen shows the version. The latest released
IDE is v1.0.3a.
> Unfortunately, after I saved the project, exited and
> came back, I can no longer replicate it. Don't worry, it will come back
> relatively
> soon and I'll see what I can report.
>
> Best I can tell, the problem comes up when I load a different window.
> Sometimes
> (and I haven't identified exactly when) the loading of a different window
> causes
> one routine or another to disappear.
Do you mean while Code Editor is in view you add a different window to Design
and lose data in Code Editor or do you mean when switching, say Window1 to
existing window Window2?
Either way I'll make some tests.
> Once that has happened, if I don't immediately
> exit I can find the problem like the one I just reported happening. Of
> course,
> to make the system run, I have to restore the lost routine. That just leaves
> me in the inconsistent state that allows the above described error, though.
>
> For example, I have three windows (which you know from before). When
> switching
> from the main window to my secondary window, it will sometimes come up showing
> the code for my main window's onOpen routine in the onOpen routine for the
> secondary
> window. Complete with the first line (procedure ....) and the last line (set
> handler).
OK, I'll check this also.
> When that happens, I can go into a backup and get the code for the
> secondary window's onOpen routine and the IDE can create an exw which will run
> (not necessarily properly, but it will run). I've got enough going on in my
> project now that for it to run means that almost everything is in the right
> place. However, when a crash takes place I get strange results, as reported
> above.
>
> Of course, the "solution" is to exit immediately after restoring the
> obliterated
> code and come back in, which should at least eliminate the inconsistent state.
> But I want to keep the inconsistent state around long enough to give you
> enough
> information to try and figure out what is going on! A definite catch 22, huh?
>
> BTW, I couldn't find "CODE EDITOR MENU OPTIONS". Did you mean "Options
> Configure
> IDE"?
No. In Code Editor there is a Menu "Options" and when clicked one of the
menuitems is "When Changing Controls." Your selection (or default option,
determines which event to go to when changing controls from the List next to the
editing panel.
>
> Thanks
>
> Mike
judith
8. Re: Enhanced IDE
Judith Evans wrote:
>
> Mike777 wrote:
> SNIP
> > > Are you using IDEv1.0.3a?
> >
> > I'm pretty sure I am.
> Go to IDE "About" Menu. The third line shows the version of IDE you are using.
> Also when you start IDE the splash screen shows the version. The latest
> released
> IDE is v1.0.3a.
> > Unfortunately, after I saved the project, exited and
> > came back, I can no longer replicate it. Don't worry, it will come back
> > relatively
> > soon and I'll see what I can report.
> >
> > Best I can tell, the problem comes up when I load a different window.
> > Sometimes
> > (and I haven't identified exactly when) the loading of a different window
> > causes
> > one routine or another to disappear.
> Do you mean while Code Editor is in view you add a different window to Design
> and lose data in Code Editor or do you mean when switching, say Window1 to
> existing
> window Window2?
> Either way I'll make some tests.
The latter.
> > Once that has happened, if I don't immediately
> > exit I can find the problem like the one I just reported happening. Of
> > course,
> > to make the system run, I have to restore the lost routine. That just
> > leaves
> > me in the inconsistent state that allows the above described error, though.
> >
> > For example, I have three windows (which you know from before). When
> > switching
> > from the main window to my secondary window, it will sometimes come up
> > showing
> > the code for my main window's onOpen routine in the onOpen routine for the
> > secondary
> > window. Complete with the first line (procedure ....) and the last line
> > (set
> > handler).
> OK, I'll check this also.
Great.
> > When that happens, I can go into a backup and get the code for the
> > secondary window's onOpen routine and the IDE can create an exw which will
> > run
> > (not necessarily properly, but it will run). I've got enough going on in my
> > project now that for it to run means that almost everything is in the right
> > place. However, when a crash takes place I get strange results, as reported
> > above.
> >
> > Of course, the "solution" is to exit immediately after restoring the
> > obliterated
> > code and come back in, which should at least eliminate the inconsistent
> > state.
> > But I want to keep the inconsistent state around long enough to give you
> > enough
> > information to try and figure out what is going on! A definite catch 22,
> > huh?
> >
> > BTW, I couldn't find "CODE EDITOR MENU OPTIONS". Did you mean "Options
> > Configure
> > IDE"?
>
> No. In Code Editor there is a Menu "Options" and when clicked one of the
> menuitems
> is "When Changing Controls." Your selection (or default option, determines
> which
> event to go to when changing controls from the List next to the editing panel.
I can't imagine that setting being anything other than Find Event from Prior
Control. It is most useful to me with that setting.
Mike
9. Re: Enhanced IDE
Mike777 wrote:
>
> Judith Evans wrote:
> >
> > Mike777 wrote:
> > SNIP
> > > > Are you using IDEv1.0.3a?
> > >
> > > I'm pretty sure I am.
> > > Best I can tell, the problem comes up when I load a different window.
> > Either way I'll make some tests.
I've been testing this case and so far I have not been able to reproduce the
situation you experience. Does this happen to you all the time? And using any
project file with multiple windows?
> > > Once that has happened, if I don't immediately
> > > exit I can find the problem like the one I just reported happening. Of
> > > course,
> > > to make the system run, I have to restore the lost routine. That just
> > > leaves
> > > me in the inconsistent state that allows the above described error,
> > > though.
> > >
> > > For example, I have three windows (which you know from before). When
> > > switching
> > > from the main window to my secondary window, it will sometimes come up
> > > showing
> > > the code for my main window's onOpen routine in the onOpen routine for the
> > > secondary
> > > window. Complete with the first line (procedure ....) and the last line
> > > (set
> > > handler).
> > OK, I'll check this also.
Can't reproduce this either.
> I can't imagine that setting being anything other than Find Event from Prior
> Control. It is most useful to me with that setting.
I have no idea what most people use but each option under "When Changing
Controls" was specifically requested by one person or another.
> Mike
It seems to me the behavior you are experiencing is going to be difficult to
track down. I've looked at the code and don't see anything. There is one
correction I've made for the next release that was recently pointed out to me by
another user. Changes made to coding using Find/Replace were lost.
If anyone else is experiencing loss of prior data in Code Editor, I'd like to
know. The more cases I can test the better chance I'll find the problem.
judith
