PureBasic Forums - English

Every now and then, the menu item "Compile/Run" as well as the corresponding button in the toolbar is inactive immediately after starting the IDE. This happened with older PB versions, too. Also after writing or pasting some code into the editor, that command remains inactive:



After one (or sometimes more than one? -- I can't remember exactly) restart(s) of the IDE, the command becomes active again.

Regards, Little John

WorkAround: use Compiler / Restart Compiler.

Some background task (AV and other) slows the load of compiler down and the load is timedout.

Some background task (AV and other) slows the load of compiler down and the load is timedout.

especially Windows Defender ...

I see.
Thank you, guys.

Not sure if this is related, but go to "Preferences -> Debugger" and set the debugger startup timeout to something a bit longer, from 10000ms to 15000ms maybe?

So I came here to add that I often experienced this when running off a USB stick... then I saw:

MachineCode wrote:Not sure if this is related, but go to "Preferences -> Debugger" and set the debugger startup timeout to something a bit longer, from 10000ms to 15000ms maybe?

I never noticed that option before!

Who marked the topic as solved?

Probably little john

Would've been nice to know *how* it got solved, then.

@MachineCode

ts-soft wrote:WorkAround: use Compiler / Restart Compiler.

Some background task (AV and other) slows the load of compiler down and the load is timedout.

Who marked the topic as solved?

Probably little john

Yes, it was me.
I thought that ts-soft explained the situation (2nd post in this thread), didn't he?

Regards, LJ

Little John wrote:I thought that ts-soft explained the situation (2nd post in this thread), didn't he?

He posted a workaround, and then the next order of events was that I posted the timeout thing, and it was only after I did that, that the thread was marked as solved. So I was wondering if my post was what solved it, or his workaround. There was no definitive way to tell.

MachineCode wrote:He posted a workaround, and then the next order of events was that I posted the timeout thing, and it was only after I did that, that the thread was marked as solved. So I was wondering if my post was what solved it, or his workaround. There was no definitive way to tell.

I'm sorry, but I edited my first post and wrote "[Solved]" some hours BEFORE you posted anything to this thread.
(If you don't believe it, just look at the respective time stamps.)

I never noticed the time stamps, but that still doesn't mean it was necessarily solved by a reply given. It could have been that he worked it out himself, and just changed it to "solved". Most people reply with "Thanks, that did it" with a quote, and then mark it as solved. Since there was a total absence of this, the solve method was ambiguous. (Yeah, I know: roll your eyes at all this).

Anyway, glad it's sorted.

MachineCode wrote: Most people reply with "Thanks, that did it" with a quote, and then mark it as solved.

That's pretty much what I did.
Anyway, I'm glad that we talked about it.