The 09 December 2017 build (11246) is out.

[killerbot]

IMPORTANT : THIS IS THE FIRST BUILD THAT USES WX 303 AND IS A 64 BIT APPLICATION.



Get quick announcements through the RSS feed http://www.codeblocks.org/nightly/CodeBlock_RSS.xml

Before you use a nightly make sure you understand how it works.

A link to the unicode windows wxWidget dll(s) for Code::Blocks : http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/Prerequisites/wxmsw30u_gcc_cb_wx303_gcc510-TDM-2.7z


The 09 December 2017 build is out.
  - Windows :
   http://sourceforge.net/projects/codeblocks/files/Binaries/Nightlies/2017/CB_20171209_rev11246_win64.7z
  - Linux :
   none

The current SDK version is : 1.32.0

Resolved Fixed:

• BrowseTracker - fix shutdown assert on linux wx30

Regressions/Confirmed/Annoying/Common bugs:

[killerbot]

- NOTE SDK version is still 1.32.0, but it should be 1.33.0 (it was already bumped on the RC branch, but not on trunk).

[Xaviou]

Hi.

Win32 and an OS X version of this rev can be downloaded from my Google Drive.

The win32 7z archive also contains the needed wxWidgets and mingw10 dlls.

Regards
Xav'

[damorin]

Hi,

no problem until I closed a file and got this error window (see attachment).

Running Win 7 64-bit.
CodeBlocks svn 11246, wx3.0.3 - 64-bit.

[oBFusCATed]

Is this reproducible?

[damorin]

Nope but while trying I found something else:

- When selecting a variable, usually it's highlighting all other occurrences but now it's only doing it if I scroll up or down.

Example: Open CodeBlocks source file "src/associations.cpp" and go to "DoCheckAssociation" and double-click on "BaseKeyName". Other occurences are only highlighted when moving the scroll bar up or down.

[oBFusCATed]

Can you report this on the tickets page on sf.net?

[DirtyBlasion]

Hello! I have a little problem, it doesn't auto-complete ... in: #include <...>
I looked on internet, and I've found "Is Settings->Editor...->Code completion "Enable headers code-completion" checked?" well, it doesn't has Enable headers code-completion at all.

[Xaviou]

Hi

On OS X, toolbars doesn't have drop-down lists (build target selection, Code Completion, ...).

I've already reported this here, but when I've done it, I wasn't able to test the wxWidgets samples with hte same verison of the libs.

This is now done : the samples (AUI or classic toolbar) works as expected (see attached screenshots).

Does this needs a ticket on SF ?

Regards
Xav'

[oBFusCATed]

No, they don't work as expected in the samples. This bug is already reported here: https://trac.wxwidgets.org/ticket/17972

This is the reason we won't have an osx release soon...

[DirtyBlasion]

Ohhh, I've mistaken the place of enabling header completion.
But still have a problem with this, in project settings when I set search directories, it doesn't search in there, why?

[Xaviou]

Hi

No, they don't work as expected in the samples.

Why do you say this ?
Have a look at the screenshot I've provided : the wxAui sample have the dropdown list (the list is opened and shows the "menu" with "One choice, another choice" entries on the top-right).
I've just built the wx-3.0.3 sample "as-is".

Regards
Xav'

[oBFusCATed]

Because the sample is using wxauitoolbar and cb is using wxtoolbar. If you change the sample to use wxtoolbar it fails the same as in cb... But this is explained in my bug report...

[Xaviou]

I apologize : I've not read the ticket's text correctly 

And I confirm it doesn't work with your patch applied.
I've also tested with a wxComboBox (as in the toolbar sample) and it doesn't work either.

Regards.
Xav'

[damorin]

Hi,

another bug that is present since a really long time and I was finally able to reproduce it:

- 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.

[BlueHazzard]

- 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?

[oBFusCATed]

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...

[ambarj2009]

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.

[stahta01]

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.

[ambarj2009]

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.

[oBFusCATed]

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.

[oBFusCATed]

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

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();
 }
-- 

[Xaviou]

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

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):

• An archive containing the original build
• An archive containing the pathced build

Regards
Xav'

[oBFusCATed]

It is not a good job, just a workaround...
Is this 64bit or 32bit you're testing?

[Xaviou]

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'