Forums › Forums › SIMPOL Programming › IDE is aggrevating
- This topic has 4 replies, 3 voices, and was last updated 11 years, 2 months ago by Jean Vallee.
- AuthorPosts
- March 6, 2013 at 2:15 am #148Jean ValleeParticipant
I just hate when I think I’ve solved a problem and the IDE crashes half way thru startup. But the most aggrevating part is that it wipes out my breakspoints. I usually don’t know it until it’s too late. I know the project will crash after the breakpoint. That’s why it’s there in the first place. I need to see why it’s crashing. But because I restarted immediately after crashing… with a heavy sigh… I don’t check the breakpoints. I want to get to what’s wrong. And besides that, the IDE now takes 30 sec each time I compile to complain about type or variable blah blah blah.. I wish there was a way to turn the warnings off. 30 sec x 100 rebuilds a day adds up. Jean Vallee
March 6, 2013 at 4:05 am #2166Jim LockerMemberIf you remember to do a "save all" after setting your breakpoints, then
they will be set when you restart the IDE after it crashes.
..
When compile time is getting to be too long, then it is time to break your
project up into separate libraries so that you don't have to recompile
every time. You might also consider the possibility of obtaining a faster
system to develop on.
..
Slow compiles on Simpol (although, I must confess, it was on a virtual
machine…and still is) was one of several factors that motivated my last
major hardware upgrade (almost exactly three years ago). Of course, since
I run Linux and only have Windows available in virtual machines, hardware
changes for me are a LOT easier than they are for you native Windows users.My project is presently broken up into 16 libraries. Compiles seldom take
more than 5 or10 seconds.March 6, 2013 at 2:39 pm #1579Jean ValleeParticipantOn 3/5/2013 11:05 PM, Jim wrote:
> If you remember to do a "save all" after setting your breakpoints, then
> they will be set when you restart the IDE after it crashes.
> .
> When compile time is getting to be too long, then it is time to break your
> project up into separate libraries so that you don't have to recompile
> every time. You might also consider the possibility of obtaining a faster
> system to develop on.
> .
> Slow compiles on Simpol (although, I must confess, it was on a virtual
> machine…and still is) was one of several factors that motivated my last
> major hardware upgrade (almost exactly three years ago). Of course, since
> I run Linux and only have Windows available in virtual machines, hardware
> changes for me are a LOT easier than they are for you native Windows users.
>
> My project is presently broken up into 16 libraries. Compiles seldom take
> more than 5 or10 seconds.
>
I got out of the habit of save all once I set the option to save before
build…Compile itself only take a few seconds… it's the warnings that go on
and on (30 sec at present)I will start to make libraries in about a month or so. I'm still
building core stuff so I'm editing pretty much every file every day
right now.March 6, 2013 at 10:11 pm #2167JD KromkowskiParticipantWhat I have found (possible spurious, although as the bud light
commercial says "it's not weird if it works" which Neil may or may not
get), is that if you keep the cursor NOT over any part of the IDE window
when you rebuild/build (or when you debug and the IDE rebuilds for you)
the IDE does not crash.I've gone week without a crash.
If it's not just dumb luck, then there is some kind of conflict between
a mouse trapping function in the IDE and the build functions.March 7, 2013 at 12:01 am #2168Jean ValleeParticipantOn 3/6/2013 5:11 PM, kromkowski wrote:
> What I have found (possible spurious, although as the bud light
> commercial says "it's not weird if it works" which Neil may or may not
> get), is that if you keep the cursor NOT over any part of the IDE window
> when you rebuild/build (or when you debug and the IDE rebuilds for you)
> the IDE does not crash.
>
> I've gone week without a crash.
>
> If it's not just dumb luck, then there is some kind of conflict between
> a mouse trapping function in the IDE and the build functions.GREAT TIP!! THANKS!!!
Also, I stumbled over the Document/Compile in the menu.. I have been
working on this HUGE function and could not find the missing end if.I commented it all out then uncommented matching if / end if 's…
Document / Compile only compiles the current file and WITHOUT ALL THE
WARNINGS so it was just what I needed. I wasn't completely sure that's
what's intended so I would do a rebuild every once in a while just to be
sure. I spent all day debugging this so 30 secs of wait time while the
debugger complains with each rebuild adds up to at least an hour a day
of wasted time for me. - AuthorPosts
- You must be logged in to reply to this topic.