News:

Accounts with zero posts and zero activity during the last months will be deleted periodically to fight SPAM!

Main Menu

Symbols don't show

Started by nji, April 25, 2020, 03:27:41 PM

Previous topic - Next topic

nji

I just installed 20.03 (on Win7 Prof. 64).
Build the "hello world" console project.
And noticed that in "Management" pane, FSymbols tab, in the bottom pane no elements are shown.
(At last "main" should show up?)
No matter what kind of "View" I choose.
"Refresh" and "Reparse" don't help.

In existing projects it's the same.

oBFusCATed

FSymbols is for Fortran symbols. Is your project written in Fortran? If not there is a topic why the C/C++ Symbols browser is disabled.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

nji

#2
Well - thank you.

No I do not in Fortran (never did), I do in C/C++.

Up till now I used C::B v. 16, and there the symbols have been shown.

I searched for the topic you mentioned, and found this one (for CB 17):
http://forums.next.codeblocks.org/index.php/topic,22785.0.html

If I try to enable "View / Symbol browser" it says "... disabled due to wx3 crashes".
If I try to disable FSymbols (as of no use for me) it leaves it.

So ... what can be done to show the symbols in C/C++?

oBFusCATed

#3
http://forums.next.codeblocks.org/index.php/topic,23580.0.html

(note this is currently possible if there isn't someone willing to spend a lot of time to redesign the symbols browser to work well)
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

nji

That thread is very complex, with lot of detailed discussion, especially for a non-expert in C::B.

Can you please explain if there are simple steps to make symbol browser work?
Or do I have to compile C::B itself for it?

oBFusCATed

Nope. There aren't. There is a patch which might work for simple projects, but it is not a general solution.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

nji

Thanks anyhow.

So it remains to hope that a development prof will turn to that issue some times.
As it seems quite unconfortable to have to jump to the symbols by text find.
(Still I don't understand if the problem is in C::B or in wx3.x)

Greetings!

oBFusCATed

100% C::B problem, wx3.x makes this problem more obvious.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]


nji

THATS'S a good news!
Whatever the changes are I do hope the experiences will find their
way into the main project (to a 20.03a maybe?).

(BTW (OT): First time I hear about that "C::B First" project,
but I'm actually fascinated, due to all the hurdles, stumble stones
and pitfalls I experience(d) in "standard C:B", as I come from the M$ world.
As to my experience these will frighten off the beginners and also
most of the ones, that are willing to say goodbye from M$ finally.
So M$ will succeed again by drawing all of them to their convenient honeypots.
Sorry for being OT. But I really would like C::B etc. to blossom).

oBFusCATed

(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

oBFusCATed

QuoteAlthough I may not have actually fixed these bugs, Symbols Browser can work.

We clearly know that this is false statement. If it wasn't we wouldn't have disabled it. :)
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]

nji

That means that "C::B First" hadn't done anything about the bug,
but ... maybe (?) ... those crashes do not happen there (up to now?),
with their config?

Questions all over.
Half-wrong statements...

However - again - thanks for clarification.