Blair/Andy -
Could auto-correct be modified to accept corrections at the end of a problem (as well as previously reported - if the whole problem is selected). I ask this as a common scenario is type in an temp variable and then realise that you want to define it eg. definedTemp := 'hello'. undefinedTemp<my cursor is here - and would like to press the windows context menu key, and press C, T to define it> I'm actually thinking that it would be even cooler if you press Ctrl-Enter and it would just do the right thing for you for the closest error (probably based on heuristics - or maybe a menu that pops up if unsure). This is what makes Eclipse and InteliJ nice to use - and you parser is good enough to do this kind of thing from what I have seen. If its low on the list - with a few tips, I don't mind looing into this for you. Tim |
"TimM" <[hidden email]> wrote in message
news:dmuo5f$ic6$[hidden email]... > Blair/Andy - > > Could auto-correct be modified to accept corrections at the end of a > problem (as well as previously reported - if the whole problem is > selected). Yes, I looked at this whole issue when you previously reported it, but it would have involved too great a change at the late stage in the beta cycle. The problem is that it relies on code built to identify the parse tree node nearest the caret position rather than the selection or mouse cursor position when clicked, or some more intelligent guess at which erroneous node is nearest the caret. > > I ask this as a common scenario is type in an temp variable and then > realise that you want to define it eg. > > definedTemp := 'hello'. > undefinedTemp<my cursor is here - and would like to press the windows > context menu key, and press C, T to define it> > I've added that to the previous report, #2005. > I'm actually thinking that it would be even cooler if you press Ctrl-Enter > and it would just do the right thing for you for the closest error > (probably based on heuristics - or maybe a menu that pops up if unsure). > This is what makes Eclipse and InteliJ nice to use - and you parser is > good enough to do this kind of thing from what I have seen. > > If its low on the list - with a few tips, I don't mind looing into this > for you. Yes I like that idea, recorded as #2044, but by all means have a go at it yourself if you want to. Would be a neat goody, but might require modifiying a number of system methods. Regards Blair |
FYI -
It didn't require many system method changes at all. The next version of Intelli-Dolphin (probably release it in a few days after I've tried it a bit) will add this feature. You will be able to auto-correct if the cursor is at the beginning, end, middle, or totaly hilites the undefined variable. I also added, multiple define all missing inst-vars as well. The way you guys have done this stuff, its actually pretty easy. Cool! Tim "Blair McGlashan" <[hidden email]> wrote in message news:[hidden email]... > "TimM" <[hidden email]> wrote in message > news:dmuo5f$ic6$[hidden email]... >> Blair/Andy - >> >> Could auto-correct be modified to accept corrections at the end of a >> problem (as well as previously reported - if the whole problem is >> selected). > > Yes, I looked at this whole issue when you previously reported it, but it > would have involved too great a change at the late stage in the beta > cycle. The problem is that it relies on code built to identify the parse > tree node nearest the caret position rather than the selection or mouse > cursor position when clicked, or some more intelligent guess at which > erroneous node is nearest the caret. > >> >> I ask this as a common scenario is type in an temp variable and then >> realise that you want to define it eg. >> >> definedTemp := 'hello'. >> undefinedTemp<my cursor is here - and would like to press the windows >> context menu key, and press C, T to define it> >> > > I've added that to the previous report, #2005. > >> I'm actually thinking that it would be even cooler if you press >> Ctrl-Enter and it would just do the right thing for you for the closest >> error (probably based on heuristics - or maybe a menu that pops up if >> unsure). This is what makes Eclipse and InteliJ nice to use - and you >> parser is good enough to do this kind of thing from what I have seen. >> >> If its low on the list - with a few tips, I don't mind looing into this >> for you. > > Yes I like that idea, recorded as #2044, but by all means have a go at it > yourself if you want to. Would be a neat goody, but might require > modifiying a number of system methods. > > Regards > > Blair > |
Free forum by Nabble | Edit this page |