On sábado, 27 de julho de 2013 21:15:08, Guido Seifert wrote:
> Hi,
> what happens when I compile a Qt (version 4) with one of those options:
> MMX/3DNOW/SSE/SSE2/SSE3/SSSE3/SSE4.1/SSE4.2/AVX
> and then deploy the libs on a machine, which does not support one or more of
> them. Will I see this at o
Make sure any of your own libraries you are linking (if any) are
built using the same Qt configuration (DEBUG vs. RELEASE) as your app
you are compiling.
Karl
On 2013-07-27 09:41, Hector Gordon wrote:
> I have been getting the following message when running some new code
"The program has u
On sábado, 27 de julho de 2013 15:09:24, Alexander Syvak wrote:
> > Do not use QtGui again. If an
> > exception unwound the stack in QtGui, then QtGui is now in an undefined
> > state,
> > which means your application could do worse things than crash.
>
> How would you then handle std::bad_alloc in
I have been getting the following message when running some new code "The
program has unexpectedly finished." I have been unable to trace the reason
and would appreciate any suggestions as to what may have caused the message.
___
Interest mailing list
Int
> Do not use QtGui again. If an
> exception unwound the stack in QtGui, then QtGui is now in an undefined
> state,
> which means your application could do worse things than crash.
>
How would you then handle std::bad_alloc in case there're a new widget made
during an event clicked()?
__
