Recent Posts

Pages: 1 2 3 4 5 [6] 7 8 9 10
51
Development / Re: Change things in CB 20.03 back to the way it was in CB 16.01
« Last post by hbcpp on September 18, 2020, 04:29:42 am »
Thanks for the info.

I created a ticket for this.
52
Development / Re: Change things in CB 20.03 back to the way it was in CB 16.01
« Last post by stahta01 on September 18, 2020, 03:53:34 am »
Option 1: Build the version you liked
Option 2: Give information needed to try to fix the problem.

The Devs will likely need wxWidgets version and Operating System information to work on a fix.

Reverting the code is almost always *not* an option the Devs will take after 4 years has passed.

Tim S.
53
Development / Change things in CB 20.03 back to the way it was in CB 16.01
« Last post by hbcpp on September 18, 2020, 02:36:54 am »
I just finished building the latest CB trunk version. Up until now I was using CB 16.01.

 I am just starting using it and see how it feels and I noticed some related details that I would like to change.

In 20.03 when I am typing a header the autocomplete popup shows and it doesn't show the whole header name but instead it just show the first 2 letters and the ellipsis mark.

There are times when I use a std::vector variable, per say, after starting typing a method the autocomplete popup shows and just cover the entire code and it a little annoying.

These are the first 2 things that I have noticed so far that I would like it like it was in CB 16.01.

So, is there a way to do that. Change the source code and revert those specific codes to make those specific changes.
I am guessing there is, so where are those files, what exactly need to be changed in the code.
Thanks.

In the attachment there is a screenshot showing the autocomplete popup in CB20.03 with ellipsis.

54
Using Code::Blocks / Re: Code::Blocks Freezes for 15 seconds on typing parentheses ()
« Last post by oBFusCATed on September 17, 2020, 10:52:15 pm »
The callstack/backtrace would tell us where the problem happens. I don't see one in your screenshot.
55
Using Code::Blocks / Re: Code::Blocks Freezes for 15 seconds on typing parentheses ()
« Last post by Sasha on September 17, 2020, 02:29:45 pm »
Yes sure, I can do it.
56
Help / Re: Codeblocks on MAC OS Catalina
« Last post by anb on September 17, 2020, 11:29:00 am »
Copying to the clipboard is not working at all.  This is a big problem for me.  I have tried the standard shortcut keys, which were not assigned to be begin with, also tried the Copy menu item from the Edit menu, as well as Copy from the context menu.  None of them copy the selection to the clipboard.
57
Help / Re: Codeblocks on MAC OS Catalina
« Last post by anb on September 17, 2020, 10:59:36 am »
Whilst build 12198 is running and I can happily edit files, and it seems far more stable, I unfortunately cannot build/compile anything.  When I do so the command line appears in t he Build Log window but then nothing happens, and C::B thinks it is still building.  I cannot abort it either.  I have to completely kill the app.

Copying and pasting the command line to a Terminal runs fine, so the command line is correct.

This is happening on every file I try to build.  Any ideas?

If we can get my source building correctly then I can at least look in to some of these issues.  I can also use the very latest code too (12201).
58
Help / Re: Codeblocks on MAC OS Catalina
« Last post by anb on September 17, 2020, 10:21:11 am »
Shipping a version for mac requires Paid Apple developer account. Without it we cannot apply the new hardening required in the latest OS.

Yes, that is a pain.  My work need to port some Windows apps to Mac and it is proving to be a painful process.

Our development environment for the Mac is on Mojave.  It's a long story.  So I am fine running the builds from Xaviou.

But this is the least of our concerns, we need someone to use this software on a daily basis and fix the problems which are macOS specific.
I use it from time to time, but I don't plan to spend too much fixing macOS issues.

I'll be pretty much the same, to be honest.  I just need to use it to port our Windows apps and libraries to the Mac.  But I imagine we'll end up doing more and more work on the Mac as time passes.

I can certainly report issues, etc.

Using the latest wx dev release and the latest code from trunk should work fine. If it doesn't please post the build steps/commands you're using and the build log. I'll try to help you.

As I said yesterday, it built fine and ran fine.  Although, when I came to use it this morning it wouldn't open a project.  It moaned about turning off the compiler, or something like that.  I built C::B with no plugins so I assumed that was the cause so tried to build it with all plugins but that failed to build.  At that point I saw your post about Xaviou builds so I downloaded one of those and that is working fine so far.

If issues do crop up then I may be able to look in to them but it depends if I have time.  I spent far too long messing with this yesterday that I had to find another app.  I ended up using CodeLite but that is nowhere near as good as C::B, but at least it wasn't crashing constantly for me.

My configure command line is:

Quote
./configure --prefix=/Volumes/Mac_USB_2TB/MacStuff/CodeBlock_Trunk/ --enable-unicode --enable-debug --disable-shared --disable-mediactrl

With this, it builds fine and runs but I can't open any project.  It also never asks me about compilers when launching.
59
Using Code::Blocks / Re: Code::Blocks Freezes for 15 seconds on typing parentheses ()
« Last post by oBFusCATed on September 17, 2020, 02:13:15 am »
Can you use a debugger break the program and show us what is doing at the time of the freeze?
60
Using Code::Blocks / Re: Problem with relative file path
« Last post by sodev on September 16, 2020, 11:38:51 pm »
Set the Execution working dir to the directory where the files reside, this way you dont need to copy them around.
Pages: 1 2 3 4 5 [6] 7 8 9 10