Author Topic: The 09 December 2017 build (11246) is out.  (Read 12651 times)

Offline BlueHazzard

  • Lives here!
  • ****
  • Posts: 1981
Re: The 09 December 2017 build (11246) is out.
« Reply #15 on: December 20, 2017, 10:39:15 pm »
- Open Code:Block project.
- Select a file in the "Projects" tab and quickly click inside the newly opened file (like cbeditor.cpp)

Result:

- The filename is added to the file where the mouse was clicked:

   C:\Download\gnu\codeblocks-code-10924-trunk\src\sdk\cbeditor.cpp

Running Win 7 64-bit.
CodeBlocks svn 11246, wx3.0.3 - 64-bit.
i can not reproduce this win7 64bit wx2.8 wx3.0 wx3.1
Are you using the middle mouse button?

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 11053
    • Travis build status
Re: The 09 December 2017 build (11246) is out.
« Reply #16 on: December 21, 2017, 12:10:04 am »
Nope. The left button is enough to reproduce it. But it happens with default settings and there is a way to prevent it changing settings. I don't know which setting causes it yet...
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline ambarj2009

  • Single posting newcomer
  • *
  • Posts: 6
  • ambar...j
Re: The 09 December 2017 build (11246) is out.
« Reply #17 on: January 05, 2018, 12:09:13 pm »
Hi.

I am testing this compilation (11246), the first thing I noticed in the editor is that the cursor does not respond at times. It often disappears and is not shown. Other times, there is a fixed mark of the cursor in a place through which it passed, although it is no longer there.

Regards.
Ambarj2009.
Let life take its course.

Offline stahta01

  • Lives here!
  • ****
  • Posts: 6298
    • My Best Post
Re: The 09 December 2017 build (11246) is out.
« Reply #18 on: January 05, 2018, 03:21:21 pm »
Hi.

I am testing this compilation (11246), the first thing I noticed in the editor is that the cursor does not respond at times. It often disappears and is not shown. Other times, there is a fixed mark of the cursor in a place through which it passed, although it is no longer there.

Regards.
Ambarj2009.

Since, you failed to post your Operating System (OS) name and version; it is likely your post will be ignored.

Tim S.
C Programmer working to learn more about C++ and Git.
On Windows 7 64 bit and Windows 10 32 bit.
On Debian Testing, compiling CB Trunk against wxWidgets 3.0.2.
--
When in doubt, read the CB WiKi FAQ. http://wiki.codeblocks.org

Offline ambarj2009

  • Single posting newcomer
  • *
  • Posts: 6
  • ambar...j
Re: The 09 December 2017 build (11246) is out.
« Reply #19 on: January 05, 2018, 07:38:49 pm »
Hi.

I am testing this compilation (11246), the first thing I noticed in the editor is that the cursor does not respond at times. It often disappears and is not shown. Other times, there is a fixed mark of the cursor in a place through which it passed, although it is no longer there.

Regards.
Ambarj2009.

Since, you failed to post your Operating System (OS) name and version; it is likely your post will be ignored.

Tim S.


411/5000
Oh, all right, it's a Windows 10 Home 64 bit computer.

The fact is that I read the rules and I did not see where he said such a thing. I did not bother looking to see if this problem already exists or is detected. I'll have to read more and ask less.

I go back to my previous version until I solve it.

By the way, this problem started to appear since I started using Code::Blocks 64 bits versions.

Regards.
Let life take its course.

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 11053
    • Travis build status
Re: The 09 December 2017 build (11246) is out.
« Reply #20 on: January 05, 2018, 08:38:51 pm »
Yes, it is known problem with wx3.0 based nightlies. It will be fixed sometime in the future. When I don't know. If someone can debug it, then it will be best.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 11053
    • Travis build status
Re: The 09 December 2017 build (11246) is out.
« Reply #21 on: January 29, 2018, 09:10:20 pm »
Would it be possible for windows people building wx3.x+64bit builds to test if the patch below resolves the problem with the editor redraw?
Code: [Select]
diff --git a/src/src/main.cpp b/src/src/main.cpp
index 0ed4811..4707aa0 100644
--- a/src/src/main.cpp
+++ b/src/src/main.cpp
@@ -4321,7 +4321,15 @@ void MainFrame::OnEditorUpdateUI(CodeBlocksEvent& event)
     }
 
     if (Manager::Get()->GetEditorManager() && event.GetEditor() == Manager::Get()->GetEditorManager()->GetActiveEditor())
+    {
+#if defined(__WXMSW__) && wxCHECK_VERSION(3, 0, 0)
+        // Execute the code to update the status bar outside of the paint event for scintilla.
+        // Executing this function directly in the event handler causes redraw problems on Windows.
+        CallAfter(DoUpdateStatusBar);
+#else
         DoUpdateStatusBar();
+#endif // defined(__wxMSW__) && wxCHECK_VERSION(3, 0, 0)
+    }
 
     event.Skip();
 }
--
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline Xaviou

  • Regular
  • ***
  • Posts: 276
    • X@v's wxStuff
Re: The 09 December 2017 build (11246) is out.
« Reply #22 on: January 30, 2018, 03:15:22 pm »
Hi
Would it be possible for windows people building wx3.x+64bit builds to test if the patch below resolves the problem with the editor redraw?
Code: [Select]
diff --git a/src/src/main.cpp b/src/src/main.cpp
index 0ed4811..4707aa0 100644
--- a/src/src/main.cpp
+++ b/src/src/main.cpp
@@ -4321,7 +4321,15 @@ void MainFrame::OnEditorUpdateUI(CodeBlocksEvent& event)
     }
 
     if (Manager::Get()->GetEditorManager() && event.GetEditor() == Manager::Get()->GetEditorManager()->GetActiveEditor())
+    {
+#if defined(__WXMSW__) && wxCHECK_VERSION(3, 0, 0)
+        // Execute the code to update the status bar outside of the paint event for scintilla.
+        // Executing this function directly in the event handler causes redraw problems on Windows.
+        CallAfter(DoUpdateStatusBar);
+#else
         DoUpdateStatusBar();
+#endif // defined(__wxMSW__) && wxCHECK_VERSION(3, 0, 0)
+    }
 
     event.Skip();
 }
--
Well done : seems to do the job.

If one want to test, I've uploaded the corresponding build to my Google Drive (rev 11278):

Regards
Xav'
The french wxWidgets site : http://www.wxdev.fr
My wxWidgets's stuff : https://wxstuff.xaviou.fr/

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 11053
    • Travis build status
Re: The 09 December 2017 build (11246) is out.
« Reply #23 on: January 30, 2018, 07:06:05 pm »
It is not a good job, just a workaround...
Is this 64bit or 32bit you're testing?
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

Offline Xaviou

  • Regular
  • ***
  • Posts: 276
    • X@v's wxStuff
Re: The 09 December 2017 build (11246) is out.
« Reply #24 on: January 30, 2018, 11:04:18 pm »
It is not a good job, just a workaround...
Is this 64bit or 32bit you're testing?
I've tested with wxWidgets 3.0.3 - 64 bits built with MinGW-TDM-5.1.0.

And I confirm that that problems I was talking about in this post disappeared.

Regards
Xav'
The french wxWidgets site : http://www.wxdev.fr
My wxWidgets's stuff : https://wxstuff.xaviou.fr/