News:

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

Main Menu

The 08 June 2019 build (11712) is out.

Started by killerbot, June 08, 2019, 10:43:27 AM

Previous topic - Next topic

Xaviou

Hi
Quote from: oBFusCATed on June 09, 2019, 08:28:49 PM
Xaviou: Have you run the bootstrap script?
Shame on me  :-[ I didn't thought about re-running this script.
It worked : Thank you.

I also have the Linux problem reported by killerbot.
Is there a solution or do we have to wait ? (I'm on a Debian Stretch using the official wx-3.0 libs).

Regards
Xav'
My wxWidgets's stuff : [url="https://wxstuff.xaviou.fr/"]https://wxstuff.xaviou.fr/[/url]

raynebc

Quote from: oBFusCATed on June 09, 2019, 02:32:33 PM
This is probably hardcoded font and it doens't find it on your system. I suppose something in wx's font selection changed. If you want to do experiments check the ListCtrlLogger::UpdateSettings and TextCtrlLogger::UpdateSettings.

What happens if you build cb with latest wx-master?

Investigating the source code would demand more time and expertise than I have.  It's not that big a deal, just a bit annoying that it picks an ugly font and there's seemingly no way to change it.

LETARTARE

QuoteIMPORTANT : THIS IS THE FIRT BUILD THAT USES WX 311 with 2D SUPPORT.
Will this version and the following be compilable with 'wx2.8.12' ?
CB-13834, plugins-sdk-2.25.0 : Collector-2.6.5, AddOnForQt-5.1.2
1- Win7 Business Pack1 64bits : wx-3.2.8, gcc-15.2.0,
2- OpenSuse::Leap-15.6-64bits : wx-3.2.8;gtk3-u, gcc-15.2.0,
=> !! The messages are translated by 'Deepl'

oBFusCATed

LETARTARE: What do you mean by compatible? C::B still builds with wx2.8 (a minor build fix is in the works for the windows build). Generally everybody should consider moving to wx3.x releases. At least give the new version a spin to find out if anything useful for you is still working.

Dropping wx2.8 is inevitable!
(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!]

raynebc

I'm seeing the failed assertion messages at launch of this nightly that I reported with the March 9 nightly:
http://forums.next.codeblocks.org/index.php/topic,23158.msg157753.html#msg157753

Is there anything useful a person with no significant C++ knowledge like me could do to help troubleshoot this?  I'll largely be stuck on 17.12 indefinitely otherwise.

oBFusCATed

We need at least backtrace, but this requires building from source.
(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!]

raynebc

There's no other way I could get a build with debugging symbols included or something like that?

oBFusCATed

Unfortunately, yes you have to build from source.
(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!]

raynebc

I found that if I changed the OS back to US-English locale and rebooted, this hotfix seems to use the same font in the build log that 17.12 uses.  It's a really niche issue, but hopefully that narrows it down a little.