@devDawg said in Copying a const complex data type:

would the best plan be to declare that data source as a C++ class

I would think so, yes

@VRonin Well apparently it is oO.
Wasn't ware of that one, I came by it when googled the warning, but gave it not much mind.

Thank you!

@CybeX said in copy file from resource to disk keeping folder structure (platform independant):

@Chris-Kawa @mpergand

Looks ok. What's wrong with it?

Well...nothing but it is an extremely tedious process...

Ok, let me change the question slightly here to help solve this using a different method.

Can (and how) am I able to get the original resource file name (e.g. below) from the QResource object.

Why don't you just give up to set alias and use the original file name in qrc?

@raven-worx Thanx for the suggestion. I think we can go a long way with this, except that we are on Windows and it seems we need some Windows-specific MIME-conversions. We'll try to tinker a bit with that.

Thanks to all of you.

I have no time to dedicate close to a day to implement and test a method to copy files little by little (although there have to be loads of code parts already implemented I'm sure). By the moment, If the user is copying a large list of files and wants to interrupt the process, the process will finish when it finishes to copy the current file at that moment, and will erase the previous files. If the current file is huge, the user is going to wait until the end of the copy.

We know now the behaviour of the Qt copy process, so in the future if it is a problem for somebody, we will have to implement the buffer...

Again, thanks!

Hi,

No, it's something you'll have to implement yourself.

You'll probably have to create an event filter that will re-send any relevant event to your other windows.

I was having this same problem, turns out I was restarting too soon. The file transfer was so slow that took over a minute to transfer a 2Mb file.

I still don't have a good solution, I am using system("cp file1 file2") for Linux as a workaround, but don't have any suggestions for a portable solution.

Hi @Lisbetti and Welcome,
AFAIK you will need some C++ API's as well for cropping the image. Once you grab the image using grapToImage call a C++ function and pass this image to it for further processing. Once you receive it on C++ side you have QImage::copy function to copy the desired part. This function too returns a QImage which you can send it to QML again for displaying.

Note: If you are a beginner C++ and QML interaction may sound a bit tedious. Pls refer the fine docs for further explanation:
http://doc.qt.io/qt-5/qtqml-cppintegration-topic.html
http://doc.qt.io/qt-5/qtqml-cppintegration-exposecppattributes.html
http://doc.qt.io/qt-5/qtqml-cppintegration-exposecppattributes.html#exposing-methods-including-qt-slots

Hmmm...okay, I think it works now.

I will create "backup.qml" dynamically with Qt.createComponent() and createObject(root, {listModel: ListModel}).

After that I access the property listModel in the created component, iterate over the current listModel which should be backuped and append that items in the listModel of the new-created component.

At the end I push the new-created component on stack to be able to backup more than one "state" of the model.