News:

As usual while waiting for the next release - don't forget to check the nightly builds in the forum.

Main Menu

The 13 April 2009 build (5535) is out.

Started by killerbot, April 13, 2009, 08:34:01 PM

Previous topic - Next topic

ollydbg

Quote from: mmkider on April 20, 2009, 09:48:05 AM
Quote from: geiermeier on April 20, 2009, 09:01:46 AM
I'm experiencing the toolbar-drag crashes with the current nightly and the library versions given in the opening post under XP SP3.

Download this wxmsw2.8.10 for my patch.

http://mmkider.googlepages.com/wxmsw28u_gcc_cb_wx2810.7z


void wxAuiManager::OnFloatingPaneMoveStart(wxWindow* wnd)
{
    // try to find the pane
    wxAuiPaneInfo& pane = GetPane(wnd);
    wxASSERT_MSG(pane.IsOk(), wxT("Pane window not found"));

   //patch there.
   if(!pane.frame)
        return;
       
    if (m_flags & wxAUI_MGR_TRANSPARENT_DRAG)
        pane.frame->SetTransparent(150);
}



Wow, Thanks for sharing!
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

critic

Please, pay attention to my question http://forums.next.codeblocks.org/index.php/topic,10406.msg71709.html#msg71709
You can watch sources of this plugin in attached archive qthelper.zip.

Guys, I need your help!!!


[attachment deleted by admin]

eckard_klotz

Hello Critic.

I'm not a developer of C::B or a plug-in, so my tip may be wrong.

If I understand you right you want to change some project-adjustments but you don't have the know-how to change the application-variables of C::B in the ram of your computer.

Have you ever thought about changing the content of the xml-file that contains the project-data also? May be you have to reload your project after changing the data was changed by your plug-in to make it active. But if you can live with this solution at the moment this will be a temporary workaround until somebody can help you really.

Best Regards,
                   Eckard Klotz

stahta01

Quote from: critic on April 22, 2009, 10:15:59 AM
Please, pay attention to my question http://forums.next.codeblocks.org/index.php/topic,10406.msg71709.html#msg71709
You can watch sources of this plugin in attached archive qthelper.zip.

Guys, I need your help!!!


Please post a "new topic" in the proper group.

Tim S
C Programmer working to learn more about C++.
On Windows 10 64 bit and Windows 11 64 bit.
--
When in doubt, read the CB WiKi FAQ. [url="http://wiki.codeblocks.org"]http://wiki.codeblocks.org[/url]

critic

I posted a new topic "QtHelper plugin" in Developers forum -> Plugins development

critic


dk

#36
I've made a lot of investigation of crash when moving toolbar on my system.

There are two necessary conditions to reproduce the problem:

1. nvidia driver for xorg (when using other driver - vesa, nv or vboxvideo - there are no crashes).
2. using KDE4 as a desktop environment (when using KDE3 or Gnome there are also no crashes).

I've attached three screenshots of my desktop:
1. codeblocks-KDE4-nvidia.gif - before crash, using KDE4 and nvidia driver (it wasn't too ease to make such screenshot!)
2. codeblocks-KDE4-nv.gif - no crash, using KDE4 and nv driver
3. codeblocks-KDE3-nvidia.gif - no crash, using KDE3 and nvidia driver.

On the first picture you can see blue solid rectangle - it is the final position for toolbar, when moving it. On the other pictures this rectangle isn't solid, it is the shaded blue-white rectangle.

So, when I see the shaded rectangle, there is no crash, when I see solid blue rectangle, there will be crash.

Can anybody reproduce the bug?


[attachment deleted by admin]

stahta01

Patch needed for NON-PCH Windows Build.
Tim S


Index: src/plugins/contrib/codesnippets/codesnippets.cpp
===================================================================
--- src/plugins/contrib/codesnippets/codesnippets.cpp (revision 5562)
+++ src/plugins/contrib/codesnippets/codesnippets.cpp (working copy)
@@ -30,6 +30,7 @@
#include <wx/string.h>
#include "sdk_events.h"
#include "manager.h"
+ #include "configmanager.h"
#include "projectmanager.h"
#include "personalitymanager.h"
#include "cbworkspace.h"
C Programmer working to learn more about C++.
On Windows 10 64 bit and Windows 11 64 bit.
--
When in doubt, read the CB WiKi FAQ. [url="http://wiki.codeblocks.org"]http://wiki.codeblocks.org[/url]

killerbot


dk

#39
I can't compile SVN5535 by gcc4.4 because of the error in src/src/prefix.cpp:

prefix.cpp: In function 'char* br_extract_dir(const char*)':
prefix.cpp:396: error: invalid conversion from 'const char*' to 'char*'
prefix.cpp: In function 'char* br_extract_prefix(const char*)':
prefix.cpp:432: error: invalid conversion from 'const char*' to 'char*'
make[3]: *** [prefix.o] Error 1


suggested patch:
--- codeblocks-8.02/src/src/prefix.cpp.orig 2008-02-27 16:15:26 +0300
+++ codeblocks-8.02/src/src/prefix.cpp 2009-05-08 01:30:03 +0400
@@ -393,7 +393,7 @@ br_extract_dir (const char *path)

br_return_val_if_fail (path != (char *) NULL, (char *) NULL);

- end = strrchr (path, '/');
+ end = (char*) strrchr (path, '/');
if (!end) return strdup (".");

while (end > path && *end == '/')
@@ -429,7 +429,7 @@ br_extract_prefix (const char *path)
br_return_val_if_fail (path != (char *) NULL, (char *) NULL);

if (!*path) return strdup ("/");
- end = strrchr (path, '/');
+ end = (char*) strrchr (path, '/');
if (!end) return strdup (path);

tmp = br_strndup ((char *) path, end - path);

Jenna

Quote from: dk on May 08, 2009, 12:06:23 AM
I can't compile SVN5535 by gcc4.4 because of the error in src/src/prefix.cpp:

prefix.cpp: In function 'char* br_extract_dir(const char*)':
prefix.cpp:396: error: invalid conversion from 'const char*' to 'char*'
prefix.cpp: In function 'char* br_extract_prefix(const char*)':
prefix.cpp:432: error: invalid conversion from 'const char*' to 'char*'
make[3]: *** [prefix.o] Error 1


I can not reproduce this error, neither when buidling from cbp-file, nor with make.

Quoteg++ -v
Es werden eingebaute Spezifikationen verwendet.
Ziel: x86_64-linux-gnu
Konfiguriert mit: ../src/configure -v --with-pkgversion='Debian 4.4.0-4' --with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared --enable-multiarch --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.4 --program-suffix=-4.4 --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-mpfr --enable-objc-gc --with-arch-32=i486 --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread-Modell: posix
gcc-Version 4.4.1 (Debian 4.4.0-4)

inside C::B:
Quote
g++-4.4 -Wall -g -I/usr/lib/wx/include/gtk2-unicode-release-2.8 -I/usr/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D_LARGEFILE_SOURCE=1 -D__WXGTK__ -pthread  -fmessage-length=0 -fexceptions -Winvalid-pch -Ulinux -Uunix -fPIC -DcbDEBUG -DCB_PRECOMP  -DENABLE_BINRELOC    -Iinclude -Isrc/wxAUI -Iinclude/wxFlatNotebook/include -Iinclude/scripting/include -Iinclude/scripting/sqplus -Iinclude/wxscintilla/include  -c /home/jens/codeblocks-build/codeblocks.trunk/src/src/prefix.cpp -o .objs/src/prefix.o

with make:
Quoteg++ -DHAVE_CONFIG_H -I. -I../../src/include -I/usr/lib/wx/include/gtk2-unicode-release-2.8 -I/usr/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D_LARGEFILE_SOURCE=1 -D__WXGTK__ -pthread -I../../src/include/wxscintilla/include -I../../src/include -I../../src/include/scripting/include -I../../src/include/scripting/sqplus -I../../src/include/wxFlatNotebook/include -I../../src/src/wxAUI -DENABLE_BINRELOC -DAPP_PREFIX="\"/home/jens/codeblocks-tmp\"" -Ulinux -Uunix  -O2 -ffast-math -DCB_AUTOCONF -g -O2 -DCB_PRECOMP -Winvalid-pch -fPIC -DPIC -fexceptions -MT prefix.o -MD -MP -MF .deps/prefix.Tpo -c -o prefix.o prefix.cpp

afb

- Mac OS X: (10.4 up, Universal)
  http://prdownload.berlios.de/codeblocks/CB_20090413_rev5535_mac2810.zip

Leopard compatibility and Mac/wxWidgets/D project templates still need work.

Grom

Is project still alive? What about the next relize?
gcc+winXP+suse.

MortenMacFly

Quote from: Grom on May 13, 2009, 10:23:16 PM
Is project still alive?
Check the svn commit log. If there are commits within the last month we are still alive. Otherwise we all died suddenly... probably due to the swine flu.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]

stahta01

Quote from: MortenMacFly on May 14, 2009, 08:46:35 AM
Quote from: Grom on May 13, 2009, 10:23:16 PM
Is project still alive?
Check the svn commit log. If there are commits within the last month we are still alive. Otherwise we all died suddenly... probably due to the swine flu.

I won't believe Code::Blocks project is dead till I see pigs fly.

Tim S

PS: When pigs fly, we will all remember bird dropping as back in the good olde days.
C Programmer working to learn more about C++.
On Windows 10 64 bit and Windows 11 64 bit.
--
When in doubt, read the CB WiKi FAQ. [url="http://wiki.codeblocks.org"]http://wiki.codeblocks.org[/url]