I noticed the core binaries (codeblocks.exe and codeblocks.dll) in this release are more than twice the size of Ceniza's snapshot from a few days ago. My guess was that they're compiled with debugging symbols, and some poking around with my hex editor seems to confirm that.
- Single file compile (not belonging to a project).
It seems you forgot to put the sources in the .tar.gz package...
I was trying to compile under Linux when I got a...problem ^^
void wxDockWindow::addBorder() {
// move the windows contents in by an amount
wxSizer * sizer = GetSizer();
wxSizerItemList& sizerList = sizer->GetChildren();
wxwxSizerItemListNode * pNode = sizerList.GetFirst();
wxASSERT(pNode);
wxSizerItem * pSizerItem = pNode->GetData();
wxASSERT(pSizerItem);
pSizerItem->SetBorder( BORDER_SIZE );
pSizerItem->SetFlag( pSizerItem->GetFlag() | wxALL );
Layout();
}
I say Yiannis give us the link to the files and we test them. Only with approval of at least 2 people he'll release the files. What do you say?
Warning - while you were typing a new reply has been posted. You may wish to review your post.Hehe, cool!
I dropped the sources from the homepage (don't have sourceforge access, tho). Later we can find out what went wrong.Do you reffer to the fact sf is down ATM, or that you arent allowed to upload/delete/modify file releases in the project (I guess its not the case)
The Wiki talks about a "patch" to wxGTK2; should I apply it to my freshly downloaded wxWidgets tarball? I don't know, I'm trying without this.
But the main problem is wxDockIt;
I wish the Linux installation procedure is simplified in the next release, because it's nearly impossible for a poor human guy to make it work :(
Can not find an entry point to _ZN7Manager3GetEP7wxFrameP10wxNotebookP8wxWindow in codeblocks.dll libraryand
Failed to load shared library <code blocks path>/plugins/help_plugin.dll" (Error 127: Can not find procedure)
I tested the background color (in syntax highlighting for c++ files) and i think it works.
Regarding the trailing space issue, we'd need help: We don't know how to do it! :shock: I mean, it COULD be implemented when saving files, but not after editing each line (which I think would be the main problem). Anyway feel free to post the issue in the developer forums to see if anyone can help.
I don't know how it happens, but I always seem to end up wth a ton of whitespace behind my lines, like 3 tabs worth. It gets messy, in DevC++ there is an option to kill this trailing whitespace. I'm not sure if it happens per line of on save.
Has the helper box thing been imporved? At the moment it pops up whenever I press '.'(with nothing usefull) and steals my keyboard focus.
I tested the background color (in syntax highlighting for c++ files) and i think it works.
Just a little sugestion: wouldn't it be better if we had a way of closing tabs from the tabs itself? Like a context right-click menu with Close this tab stuff or a little close button right the tabs to close the active one?That would be nice, but notice right-clicking the editor belonging to that tab works. So for the active tab it's just as easy, if a little less intuitive: aim lower :). For other tabs, you'll have to open them and then aim lower. Not ideal, but it works :roll:.
Please! Submit bugs and feature requests at sourceforge!
but notice right-clicking the editor belonging to that tab works.I didn't noticed that. Tnx for the info. It'll sure help 'til the little close button arrives ;)
And sorry for the feature request on wrong place, rickg22. I promisse to do it on the right place, from now :D
I noticed the core binaries (codeblocks.exe and codeblocks.dll) in this release are more than twice the size of Ceniza's snapshot from a few days ago. My guess was that they're compiled with debugging symbols, and some poking around with my hex editor seems to confirm that.
Until 1.0 is finalized, we don't build optimized versions.
Also, ceniza's binaries are UPX'd IIRC.
Yiannis.
I tested the background color (in syntax highlighting for c++ files) and i think it works.
Regarding the trailing space issue, we'd need help: We don't know how to do it! :shock: I mean, it COULD be implemented when saving files, but not after editing each line (which I think would be the main problem). Anyway feel free to post the issue in the developer forums to see if anyone can help.