In the final release of PB 5.72 LTS for Windows (at least in the x64 version), there is a very nasty bug in the IDE: It happens rather often here (on Windows 10) that it's not possible anymore to resize or terminate the IDE. This happened when the IDE is minimized, and also when it is maximized. Also mouse clicks at the main menu and at the toolbar don't have any effect.
I have never encountered something similar before in previous PB releases (on Windows).
[5.72 LTS] IDE not responsive
-
- Addict
- Posts: 4527
- Joined: Thu Jun 07, 2007 3:25 pm
- Location: Berlin, Germany
Re: [5.72 LTS] IDE not responsive
No problems here: Windows 10 Pro v1909, 6.3.18363.720
What are the steps to reproduce?
What are the steps to reproduce?
The nice thing about standards is there are so many to choose from. ~ Andrew Tanenbaum
-
- Addict
- Posts: 4527
- Joined: Thu Jun 07, 2007 3:25 pm
- Location: Berlin, Germany
Re: [5.72 LTS] IDE not responsive
At the moment, I don't know. It seems to happen "out of the blue".skywalk wrote:What are the steps to reproduce?
-
- Addict
- Posts: 1443
- Joined: Wed Nov 12, 2008 5:01 pm
- Location: Russia
Re: [5.72 LTS] IDE not responsive
I confirm.
In some circumstances, the IDE freezes.
In some circumstances, the IDE freezes.
Re: [5.72 LTS] IDE not responsive
I, too, have encountered this nasty problem. The IDE suddenly, for no immediately identifiable reason, just stops responding.
Is this a PB bug, or a Windows one ?
I'm running PB 5.72 in Windows 10 X64 2004, build 19041.207
As well, the IDE loads up blank. It seems to have suddenly forgotten its history, even though the files in the roaming folder (History, tools, preferences) appear intact. The list of recent files also appears accurate.
Is this a PB bug, or a Windows one ?
I'm running PB 5.72 in Windows 10 X64 2004, build 19041.207
As well, the IDE loads up blank. It seems to have suddenly forgotten its history, even though the files in the roaming folder (History, tools, preferences) appear intact. The list of recent files also appears accurate.
"That's not a bug..." said the programmer. "it's a feature! "
"Oh! I see..." replied the blind man.
"Oh! I see..." replied the blind man.
Re: [5.72 LTS] IDE not responsive
I hope this isn't a sign of things to come due to the IDE being open-source now? My fear is that people are making changes that are accidentally breaking things behind the scenes.
Re: [5.72 LTS] IDE not responsive
I haven't experience the above mentioned problems with the latest IDE release, and I also work on Win 10 x64.
The fact that it's affecting some users and not others might indicate some common hardware which might be incompatible (or trig the bug) — e.g. do you work with multiple monitors?
It could be a problem related to DPI awareness, since it's affecting window resizing/minimizing operations.
If it was an IDE bug, probably every Win user would be experiencing it. But since it only affects some machines, it might be a PB bug.
The fact that it's affecting some users and not others might indicate some common hardware which might be incompatible (or trig the bug) — e.g. do you work with multiple monitors?
It could be a problem related to DPI awareness, since it's affecting window resizing/minimizing operations.
If it was an IDE bug, probably every Win user would be experiencing it. But since it only affects some machines, it might be a PB bug.
The PureBASIC Archives:
- GitHub Repo + Wiki + Website
- https://tajmone.github.io/purebasic-archives
- PB Sourcecode Highlighters for Websites and Documents
- Dräc OOP Tutorial reprint
- Pandoc2BBCode: Post on PB Forums from Markdown, ReST, Docx, and other formats…
Re: [5.72 LTS] IDE not responsive
I never experienced that on win7 ultimate x64.
-
- Addict
- Posts: 4527
- Joined: Thu Jun 07, 2007 3:25 pm
- Location: Berlin, Germany
Re: [5.72 LTS] IDE not responsive
That's my fear, too.BarryG wrote:My fear is that people are making changes that are accidentally breaking things behind the scenes.
Re: [5.72 LTS] IDE not responsive
I guess it's a whole new process, we are also reviewing the new code before pushing it to the main branch, so we need to get better at it to avoid such issues