Resource path for non-qt functions
-
@JonB said in Resource path for non-qt functions:
Just use QFile to open the ":/..." file for read
I do not need read that, i need only it's path in string type so i could pass that as the parameter for OpenCV functions :) Which will read/write/anything to it.
@JonB said in Resource path for non-qt functions:
Write that to a physical, external file (also probably via a QFile) to export to file for outside world.
Seriously, i still don't get it, what exactly should i do with that? As far i understand that i should copy file from resources, paste it's copy somewhere in app's folder "buffered files or smth", then get absolutePath using QFileInfo and use that copy in the runtime of app?
@JonB said in Resource path for non-qt functions:
But a while ago I thought you were saying you were giving up on resource files and switching over to physical files anyway?
I did such stuff before, and i understand the simplicity of dumb folder creation, but never used QFiles and started to be interested, plus, tired of seeking answer what is correct way to write relative path in qt.
Ah, and QFileInfo gives zero info about the file path, same QString what i provided in the code(res directory), it gives in the runtime as a result :/myFiles/files/lego.jpg when this function absoluteFilePath() should return actual place of the file on the computer, but it does not.
@Engelard
I have explained, I don't know how to explain it any clearer.If you ship a resource, it isn't an external file, you can't pass it to OpenCV anything.
A resource is addressed via
:/...path. That is not a real file. The only thing that can open it isQFile.Use that to open its content for read. Read its whole content, writing that to a real, external file. [EDIT @SimonSchroeder shows later on that you can simply use
QFile::copy()to do this in one line.] Pass the path of that extracted file to your external OpenCV.If you don't understand this, you can't use a resource file for your purpose of passing it to OpenCV. In that case give up on resources and supply the file as an external file, not a resource.
-
@Engelard
I have explained, I don't know how to explain it any clearer.If you ship a resource, it isn't an external file, you can't pass it to OpenCV anything.
A resource is addressed via
:/...path. That is not a real file. The only thing that can open it isQFile.Use that to open its content for read. Read its whole content, writing that to a real, external file. [EDIT @SimonSchroeder shows later on that you can simply use
QFile::copy()to do this in one line.] Pass the path of that extracted file to your external OpenCV.If you don't understand this, you can't use a resource file for your purpose of passing it to OpenCV. In that case give up on resources and supply the file as an external file, not a resource.
@JonB said in Resource path for non-qt functions:
If you ship a resource, it isn't an external file, you can't pass it to OpenCV anything.
But how can it be? It exists somewhere in app folder... at least i was expecting that i could reach it. Thanks for explaining all this.
@JonB said in Resource path for non-qt functions:
In that case give up on resources and supply the file as an external file, not a resource.
seems it will be easier, but can you please clarify what is the right syntax for writing relative directories in qt? "/files/lego.jpg" is not working, and bunch of other ways i found in google.
-
@JonB said in Resource path for non-qt functions:
If you ship a resource, it isn't an external file, you can't pass it to OpenCV anything.
But how can it be? It exists somewhere in app folder... at least i was expecting that i could reach it. Thanks for explaining all this.
@JonB said in Resource path for non-qt functions:
In that case give up on resources and supply the file as an external file, not a resource.
seems it will be easier, but can you please clarify what is the right syntax for writing relative directories in qt? "/files/lego.jpg" is not working, and bunch of other ways i found in google.
@Engelard
/files/lego.jpgis not a relative path. It starts with a/, so it's absolute.Relative paths do not start with
/.lego.jpg,files/lego.jpgand../lego.jpgare all relative paths. They are relative to whatever the current directory is.These relative/absolutes have nothing to do with Qt. The only "special" path in Qt is
:/..., which Qt alone treats as referring to a file in its resources, not accessible to the outside world. -
@Engelard
/files/lego.jpgis not a relative path. It starts with a/, so it's absolute.Relative paths do not start with
/.lego.jpg,files/lego.jpgand../lego.jpgare all relative paths. They are relative to whatever the current directory is.These relative/absolutes have nothing to do with Qt. The only "special" path in Qt is
:/..., which Qt alone treats as referring to a file in its resources, not accessible to the outside world.@JonB said in Resource path for non-qt functions:
They are relative to whatever the current directory is.
okay, so folder "files" is relative to my .exe and other stuff in the debug folder of my project, but none
"../files/lego.jpg"or
"files/lego.jpg"is not working...
P.S. how do you highlight some text with red in your posts?)
-
@Engelard
I have explained, I don't know how to explain it any clearer.If you ship a resource, it isn't an external file, you can't pass it to OpenCV anything.
A resource is addressed via
:/...path. That is not a real file. The only thing that can open it isQFile.Use that to open its content for read. Read its whole content, writing that to a real, external file. [EDIT @SimonSchroeder shows later on that you can simply use
QFile::copy()to do this in one line.] Pass the path of that extracted file to your external OpenCV.If you don't understand this, you can't use a resource file for your purpose of passing it to OpenCV. In that case give up on resources and supply the file as an external file, not a resource.
@JonB said in Resource path for non-qt functions:
Read its whole content, writing that to a real, external file.
you mean - make a copy of that file from resources? Even if i'll do that, i should create folder for that .jpg file, so it would'nt be messy, and then i should delete that copy when my program is about to be closed. Am i right?
-
Problem "resolved". From this topic i understand that i can't acces .res files of my qt app, it's okay. But then i found that i'm not able to simply use relative path's in my app for some strange qt reason.
So i found such wonderful static function - QString QCoreApplication::applicationDirPath(); which returns directory of running app, then simply add desired "relative" path QString and here we go!
-
What OpenCV functions are you planning to use with the image files?
If you only use cv::imread you can try to replace that with QFile + cv::imdecode or create a cv::Mat directly from a QImage. -
Bonnie, you just saved the day. Because of your hint i found this golden
answerwork of art: https://stackoverflow.com/a/33923407 Everything tested and well explained, conversion from QFile as he mentioned 10 times faster then from QImage. -
Problem "resolved". From this topic i understand that i can't acces .res files of my qt app, it's okay. But then i found that i'm not able to simply use relative path's in my app for some strange qt reason.
So i found such wonderful static function - QString QCoreApplication::applicationDirPath(); which returns directory of running app, then simply add desired "relative" path QString and here we go!
@Engelard said in Resource path for non-qt functions:
So i found such wonderful static function -
QString QCoreApplication::applicationDirPath();which returns directory of running app, then simply add desired "relative" path QString and here we go!Which is why I wrote to you earlier on:
When you open files at runtime you would be best making a full path to them. If you plan to pass this path to an external program, you may be advised to pass the full path. There are Qt methods to provide strings for the path, e.g. https://doc.qt.io/qt-5/qcoreapplication.html#applicationDirPath.
-
@Engelard said in Resource path for non-qt functions:
So i found such wonderful static function -
QString QCoreApplication::applicationDirPath();which returns directory of running app, then simply add desired "relative" path QString and here we go!Which is why I wrote to you earlier on:
When you open files at runtime you would be best making a full path to them. If you plan to pass this path to an external program, you may be advised to pass the full path. There are Qt methods to provide strings for the path, e.g. https://doc.qt.io/qt-5/qcoreapplication.html#applicationDirPath.
-
@JonB said in Resource path for non-qt functions:
Which is why I wrote to you earlier on:
Yeah, back then i did'nt give it serious attention, was thinking that using relative path's it is the only right way for program to use it's own files.
@Engelard said in Resource path for non-qt functions:
Yeah, back then i did'nt give it serious attention
Yeah, that's nice to hear ;-) I'll bear it mind for my future replies to you :D :D [<-- For the avoidance of any misinterpretations: winks/smileys!]
-
@Engelard One thing to consider – as you have mentioned that OpenCV might also be writing (to) files – is that if you distribute your app and people install it properly they might not be able to write into the applications folder. Usually, these folders are only writeable for administrators/root. Have a look at https://doc.qt.io/qt-5/qstandardpaths.html to figure out where to put which kind of files. Furthermore, there is
QTemporaryDirandQTemporaryFileif the data is supposed to only exist until you close your software.BTW: If you provide something inside your resources and need to have a copy inside the real filesystem, a simple
QFile::copy(":files/lego.jpg", "/some/tmp/path/files/lego.jpg")is sufficient. You don't need to open the file and read it in. (Though your solution you found on StackOverflow is also valid.)
