Unsolved QSettings issue mingw32 vs. msvc
-
hi
Thats pretty odd!
both exe is named the same etc?Could VS make a manifest file that changes something and mingw will not?
-
Hi,
Actually have only tried compiling in debug mode and runned in debugmode from QtCreator.But I guess it will give same result in release mode.
I discovered the issue when building a DLL which should be able to access the same key. (That DLL is build with msvc)
I then tryed building the other application with msvc, and found same issue. -
@Enrico
it possible to reproduce with small sample?
Could be bug :) -
Made a simple sample, you can get i here www.daniac.dk/QSettingsTest.zip
Exact same issue here, might be a bug
-
@Enrico
hi
i tried mingw on win 10. no messages. ( as expected)then i tried
windows 7, visual studio 2013 , 32 bit
and no messages also?both Qt 5.5.1/ 5.7
let me try 5.7 in VS.
and see if it makes any difference. -
Sorry but when you say no messages.
The only messages is from qDebug()
Have changed the sample to show the results in a plaintext box - Sorry
-
@Enrico
oh, i expected some window dialog to pop up saying access denied :)so what is the sign of error im looking for ?
-
I have modified and updated the sample with a plaintextedit showwing the results - Sorry
mingw32 - Output:
Getting MyNewPort value:COM2
Setting MyNewPort=COM2 status:0 <- Success
Getting MyNewPort value:COM2msvc - Output:
Getting MyNewPort value:default <- Failed reading also
Setting MyNewPort=COM2 status:1 <- Failed writing
Getting MyNewPort value:default <- Failed reading also -
-
@mrjj status: 1 = fail
-
@VRonin
thx. need more coffee :)
so sample did fail :)Can anyone else try the sample with VS compiler
and say if they get same result before we call it a bug :) -
MSVC2013 win 7 Qt 5.5.1 and 5.7.0 both 32 and 64 bit versions all failing
-
I have filed a bug
https://bugreports.qt.io/browse/QTBUG-55257