https://ci.appveyor.com/project/zebastian/mandelbulber2-s84yl/build/job/t5t44qr23djgnji6 can anyone of you reproduce this issue with runnning mandelbulber --test on windows?
...because appveyor tried to run the test on its own, failed, and did not export the artifact :D. I deactivated the test again in latest commit, should be available in 30-60 minutes here: https://ci.appveyor.com/project/zebastian/mandelbulber2-s84yl
(ClCompile target) ->
C:\projects\mandelbulber2-s84yl\mandelbulber2\src\audio_track.cpp(207): error C2131: expression did not evaluate to a constant [C:\projects\mandelbulber2-s84yl\mandelbulber2.vcxproj]
C:\projects\mandelbulber2-s84yl\mandelbulber2\src\audio_track.cpp(210): error C3863: array type 'double [fftSize*]' is not assignable [C:\projects\mandelbulber2-s84yl\mandelbulber2.vcxproj]
C:\projects\mandelbulber2-s84yl\mandelbulber2\src\audio_track.cpp(211): error C3863: array type 'double [fftSize*]' is not assignable [C:\projects\mandelbulber2-s84yl\mandelbulber2.vcxproj]
C:\projects\mandelbulber2-s84yl\mandelbulber2\src\audio_track.cpp(222): error C2440: 'initializing': cannot convert from 'double [fftSize*]' to 'double' [C:\projects\mandelbulber2-s84yl\mandelbulber2.vcxproj]
C:\projects\mandelbulber2-s84yl\mandelbulber2\src\audio_track.cpp(223): error C2440: 'initializing': cannot convert from 'double [fftSize*]' to 'double' [C:\projects\mandelbulber2-s84yl\mandelbulber2.vcxproj]
770 Warning(s)
5 Error(s)
thats inside the
this line fails to compile
since
calculateFFT in the new cAudioTrack:this line fails to compile
double fftData[fftSize * 2];since
fftSize is not recognizable as a constant expression
msvc needs it as a constant, or the array has to be dynamically allocated with new
http://stackoverflow.com/questions/33423502/expression-did-not-evaluate-to-a-constant-c
http://stackoverflow.com/questions/33423502/expression-did-not-evaluate-to-a-constant-c
maybe best to always use the constant cAudioFFTdata::fftSize?
but the aplication starts properly with gui and NetRender can be used with this compilation
however program is no so stable. Hangs sometimes when material is edited (probably problems with threads) and crashed one time after rendering
it doesn't happen when I use mingw version
compiles and runs like a charm :)
it was 9 and a half hours. It was no clean make, but used 20 precompiled classes from last build in 2016.
So overall it would take probably 11 hours for a full compile on a raspberry model b single core, thats only half the time of a full render of the example aexion fract file, which estimated to ~24 hours :)
So overall it would take probably 11 hours for a full compile on a raspberry model b single core, thats only half the time of a full render of the example aexion fract file, which estimated to ~24 hours :)
By the way, adding of saved window layouts doesn't work with Gnome desktop
probably menus which are on the top of the screen doens't allow to have QActionWidgets
What about psyriccios
...Pull request buddhi1980/mandelbulber2#214 ?
btw: what do you think about using qInfo()? This can be an output channel like qWarning() but will not display misbehaviour, but rather occasional happening things that may be interesting for the user (like "Cancelled window removing")
These are messages which are not qDebug() since they will stay longterm in the code and the user should not be notified in a hard way (popup), but have it in the logs, if he is interested to know...
I forgot about this functionality
It's already handled by myMessageOutput
shoudl be Get<int>()
also put the slotPlayPositionChanged back in seekto, (ping pong issue is fixed with bool updateSlider