@SourceSlayer Did you figure out some solution for this ? I'm in need to the same thing.

Unfortunately, it doesn't seems to work... actions() returns me an empty list. I think I'll go for QTextEdit::createMimeDataFromSelection() because otherwise I won't be able to deal with drag & drop (I didn't think about it :/ ) Thanks anyway!

@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!

//copy whole <from> directory to the folder <to> void copyDirectoryNested(QString from,QString to) { QDirIterator it(from, QDirIterator::Subdirectories); while (it.hasNext()) { QString file_in = it.next(); QFileInfo file_info = QFileInfo(file_in); QString file_out = file_in; file_out.replace(from,to); if(file_info.isFile()) { //is file copy qDebug() << QFile::copy(file_in, file_out); qDebug() << file_in << "<----" << file_out; } if(file_info.isDir()) { //dir mkdir QDir dir(file_out); if (!dir.exists()) qDebug() << "mkpath"<< dir.mkpath("."); } } } then use above function : copyDirectoryNested(":/<qrc_folder_location>",<writing_location>); copyDirectoryNested(":/DefaultAppData",app_data_location);

@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, Your question reminds me of a real-time "zoom" feature that clones part of a component that I've just developed using ShaderEffectSource. ShaderEffectSource allows to select, in real time and with high performance, a part of a component and display it in another larger rectangle for zooming in. // To add to your "source" component. MouseArea { id: iMouseArea anchors.fill: parent hoverEnabled: true propagateComposedEvents: true onPositionChanged:(mouse) => { // Allow events to be transmitted to components below. mouse.accepted = false iShaderEffectSource.sourceRect = Qt.rect(mouse.x-75, mouse.y-50, 150, 100) } } ... Rectangle { id: iRectDest width: 300 height: 200 anchors.right: parent.right ShaderEffectSource { id: iShaderEffectSource anchors.fill: parent sourceItem: iRectSrc /* Preserve visual quality. */ textureSize: Qt.size(iRectDest.width, iRectDest.height) }

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.