showMessageBoxAsync broken on windows8


#1

Hello all,

showMessageBoxAsync seems to be broken on win8:

win7:

win8:

  • bram

#2

Works fine for me on Windows 8 :?

[attachment=0]Mystery.png[/attachment]


#3

Ah… I guess we’ll have to try with the dev tip…

  • bram

#4

Ah, um, if you wouldn;t mind could you try with version f862392da8daacfdc54595e83d39cfb9349c9efd ?

  • bram

#5

Sure!

…I’m getting the same result as I had before - still working fine! Did you change stuff in an AlertWindow’s LookAndFeel that could’ve messed with it?

And just checking; I reverse engineered your AlertWindow gitup, so does this resemble what you have to set the window up?

juce::AlertWindow::showMessageBoxAsync (juce::AlertWindow::InfoIcon, "Using \\n", "Line1\nLine2\nLine3\n", "ok");

#6

Yup:

Would you mind trying my build?

https://dropbox.samplesumo.com/public/NewlineMessageBoxTest.exe

As a final test?

  • bram

#7

Done:

[attachment=0]Borked.png[/attachment]

If you’re using VS; try a clean/rebuild, if you haven’t already… Can you share the code for that exe?


#8

I suspect that one is using Direct2D and the other not , no ?


#9

Hmmm, very weird!

The app does nothing: what you see is the only thing it does.
I could do a clean build, but I don’t think that will change anything.
The only thing I can think about is that you are probably running your app built on win8 and the one I’m giving you was built on win7…
Could that be it?!

  • bram

#10

Had to mess with the modules path, and upgrade the project to a VS2012 one - but works fine for me!

I don’t see anything related to Direct2D being enabled in there - so that can’t be your issue…

[quote]The only thing I can think about is that you are probably running your app built on win8 and the one I’m giving you was built on win7…
Could that be it?![/quote]

That must be it - I’ve no way to test it right now though… :expressionless:


#11

Ohdear…
So this means that if you statically link to the 2010 runtime, you might get into trouble running your app in win8.
Anyone else already experience this?

  • bram

#12

[quote=“bdejong”]Ohdear…
So this means that if you statically link to the 2010 runtime, you might get into trouble running your app in win8.
Anyone else already experience this?

  • bram[/quote]

I very much doubt that - Windows is always good at backwards compatibility.


#13

Any other ideas, Jules?

Bram


#14

I fixed something like this recently… Are you sure you built with the latest version?


#15

(In case this information is useful - I tried your project on Win7 64-bit with VS2010 - and it works fine)


#16

But… did you try running the binary built in win 7 on win8? Because that is what we are doing…

Bram


#17

Ah no I haven’t - doh! I’ll try it when I get the chance


#18

Just ran Win7 debug/release builds on Win8 - and I didn’t see the issue… (built with VS2010)
Likewise, created debug/release builds on Win8, ran fine on Win7… (also built with VS2010)

But, what really got me this time was that I built and ran the Introjucer on Windows 8, went to modify your project, and this happened:
[attachment=0]Just built and ran - Win8 VS2010.png[/attachment]

Very peculiar mystery here…


#19

Updating JUCE and rebuilding the Introjucer seems to have made the issue disappear…


#20

Why is the text so fuzzy in your screenshot?

…runs…