In the last few nightlies (not sure when it started) I have an issue with wxFlatNotebook. When opening a file and a new notebook page is created it starts to "overflow" too early. What I mean is that the leftmost page is scrolled out too early. As soon as I press the left arrow, it scrolls, the arrow gets deactivated and everything is as it should be.I have the feeling I have noticed this to.
Too early in my case means rougly when half of the available notebook tab space is filled.
If I'm not clear enough, just say so and I'll provide screenshots :)
Could anyone supply some freebsd builds? the ports collection contains 1.0rc2 :/
In the last few nightlies (not sure when it started) I have an issue with wxFlatNotebook. When opening a file and a new notebook page is created it starts to "overflow" too early. What I mean is that the leftmost page is scrolled out too early. As soon as I press the left arrow, it scrolls, the arrow gets deactivated and everything is as it should be.I have the feeling I have noticed this to.
Too early in my case means rougly when half of the available notebook tab space is filled.
If I'm not clear enough, just say so and I'll provide screenshots :)
I will notify eranif (unless he already sees this).
Revision: 3174
Date: 12:05:51, 3 November 2006
* updated wxFlatNotebook to eranifs first revision in svn :-)
In the last few nightlies (not sure when it started) I have an issue with wxFlatNotebook. When opening a file and a new notebook page is created it starts to "overflow" too early. What I mean is that the leftmost page is scrolled out too early. As soon as I press the left arrow, it scrolls, the arrow gets deactivated and everything is as it should be.
Too early in my case means rougly when half of the available notebook tab space is filled.
If I'm not clear enough, just say so and I'll provide screenshots :)
Could you give me a link to a windows binary of the latest demo compiled against head please? My development environment uses wxWidgets cvs, so it probably won't compile cleanly for me.
Ubuntu 6.10 (Edgy) build here (http://www.savefile.com/projects/1037211).
Hi!
When trying to run the C::B on a machine where C::B have never been used before the following error message appears:
"Can not enumerate files in directory: 'C:\Documents and Settings\Andrew\Application Data\codeblocks/share/codeblocks/plugins' (error 3: the system can not find the file specified.)"
This bug does not manifests itself when upgrading from the Nov. 1 nightly build (the previous NB I was using).
Thanks.
I use this build on ubuntu edgy, and it said "incomplete entry on line 40, /etc/maincap" at startup, does any one know if it is my problem or somewhere else?
application/x-emerald-theme
ext: emerald
It would be nice if this was fixed, as artoj has already given fixes for it as of January 10th.
I don't know if someone already post about this HUGE bug :
1 - I opened my main.c file.
2 - I close it.
3 - I opened the project where the main.c was.
4 - OMG empty file.
Code::Blocks erased my main.c contents wow ... luckily it was a small stuff.
It was on Ubuntu 6.10 with cstudent package.
Kurapix
When I try change editor tabs order (drag&drop), the whole GNOME & C::B is freeze. Only way to escape that CTRL+ALT+F1 and "killall codeblocks". This is a permanent bug. Linux, fedora.
This is a wxWidgets to GTK communications bug in drag&drop.This may be true, but I've only seen this on wxFlatNotebook - not on wxScintilla, for example. And I remember reading about a change to wxScintilla to improve drag&drop handling to prevent this in GTK.
Hi !!
I found a (small) GUI bug.
- Activate Script console (View->Script console must be checked)
- In Messages notebook, right-click on Script console and click on Show/hide->Script console
- Right-click on any of the messages tab, Script console is not checked.
- Click on View menu, Script console is checked. The first click on it does nothing, the second re-enable it.
Dje
This is a wxWidgets to GTK communications bug in drag&drop.
Not much CodeBlocks can do about it except turn off drag&drop on linux.
You would compile wxWidgets yourself and set the define in setup.h to 0This is a wxWidgets to GTK communications bug in drag&drop.
Not much CodeBlocks can do about it except turn off drag&drop on linux.
How can I disable drag&drop in GNOME? Please help me... :(
#define wxUSE_DRAG_AND_DROP 1
If its just wxFlatNotebook thats the problem, you could compile it with the wxFNB_NODRAG flag.
Thanks. I found the wxFNB_NODRAG but have a magic value (0x80). Therefore if I comment out lines between 1300 and 1308 in wxFlatNotebook.cpp (codeblocks source tree), it will enough?
wxFlatNotebook* m_editor = new wxFlatNotebook( this, -1, wxDefaultPosition, wxDefaultSize, wxFNB_SMART_TABS | wxFNB_VC8 );
wxFlatNotebook* m_editor = new wxFlatNotebook( this, -1, wxDefaultPosition, wxDefaultSize, wxFNB_SMART_TABS | wxFNB_VC8 | wxFNB_NODRAG );
no, you'd need to find all of the wxFlatNotebook constructors in the code::blocks source code, and pass the wxFNB_NODRAG flag in them.
example,
Never delete anything - comment it out by adding a # (hash mark) at the beginning of the lineI use this build on ubuntu edgy, and it said "incomplete entry on line 40, /etc/maincap" at startup, does any one know if it is my problem or somewhere else?
You have have a problem in that file. If I recall correctly it's actually wxWidgets that creates that error because I had the same problem with FileZilla 3 (which also uses wxWidgets).
I had a line something like this in /etc/mailcap (in the error line):Codeapplication/x-emerald-theme
ext: emerald
I removed those two lines and the error disappeared. Remember to backup the file before deleting anything from it though.
It would be nice if this was fixed, as artoj has already given fixes for it as of January 10th.
Huh? I _reported_ the bug on 10th of January. The reason why this isn't fixed yet is because we don't know what the specific problem with these toolbar images is. And the menu images... well, I think we'll have to live with that problem a long time:
Screenshot 1 (http://ajonsson.kapsi.fi/pub/codeblocks/debug/cb-vista-project-mnu.png)
Screenshot 2 (http://ajonsson.kapsi.fi/pub/codeblocks/debug/cb-vista-build-mnu.png)
(And yes, the toolbars work correctly on those images)
Could someone with proper rights to the SF.net project page close these bugs because they are now fixed:Is not this saying that the bugs are fixed?
1401383 (http://sourceforge.net/tracker/index.php?func=detail&aid=1401383&group_id=126998&atid=707416)
1401376 (http://sourceforge.net/tracker/index.php?func=detail&aid=1401376&group_id=126998&atid=707416)
Thanks for killerbot for creating the patches (and devs for applying them). :)
Huh? I _reported_ the bug on 10th of January. The reason why this isn't fixed yet is because we don't know what the specific problem with these toolbar images is. And the menu images... well, I think we'll have to live with that problem a long time:
Screenshot 1 (http://ajonsson.kapsi.fi/pub/codeblocks/debug/cb-vista-project-mnu.png)
Screenshot 2 (http://ajonsson.kapsi.fi/pub/codeblocks/debug/cb-vista-build-mnu.png)
(And yes, the toolbars work correctly on those images)
Could someone with proper rights to the SF.net project page close these bugs because they are now fixed:Is not this saying that the bugs are fixed?
1401383 (http://sourceforge.net/tracker/index.php?func=detail&aid=1401383&group_id=126998&atid=707416)
1401376 (http://sourceforge.net/tracker/index.php?func=detail&aid=1401376&group_id=126998&atid=707416)
Thanks for killerbot for creating the patches (and devs for applying them). :)