Replies: 2 comments
-
@TyHol , hey, sounds like you guys are doing interesting things here, I'd love to hear more about it! I think the problem here is that - slightly confusingly I'll admit - what you download from QFC is a packaged version of what you upload to QFC from your local cloud project folder. The packaging process will only include datasets that are tied to project layers, as well as a sidecar .qml plugin file and the attachments folder you have defined in your project properties' QField panel. Nothing less, nothing more :) So for example, say you have this file structure:
You will end up with a packaged project downloaded by QField from QFC that only includes:
The way to work around that is to add any additional resources used by your plugin inside a subfolder to your project, and add it into the attachments directories list here: You'll need to tweak your plugin code's relative path to the image/search logic qml file, but then you should be good to go! |
Beta Was this translation helpful? Give feedback.
-
@nirvn Thanks - Done as you've suggested added folder & changed QML
and Thanks for the encouragement! — we're trying to put together hopefully very striaghtforeward cloud-based project for a local Mountain Rescue team to help us keep track of our members on the hill (and when synched allow members on the hill to keep track of each other) & now you've add the ability to track in the background it's opened up a world of possibilities for us.....so thanks for that! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
When attempting to integrate a custom plugin into a project stored in QFieldCloud, custom icons are not displayed the and search function does not work.
The project is uploaded to QFieldCloud and also stored locally in the default QField folder. The relevant files for the plugin are moved into the project folder and synchronised, the main.qml file for the plugin has been renamed to match the project name.
When the project is opened from the cloud—both on PC (QField 3.5.1) and on Android (v3.5.4)—the loading popup appears and the plugin is loaded:
However, when the same project is opened directly from the local default QFieldCloud folder on the PC (rather than through the QFieldCloud interface), the plugin works as expected: the custom icon is displayed, and the search function operates correctly.
The same lack of 'search' integration occurs in the Nominatim plugin.
Native icons (such as the camera icon used in the SNAP plugin) work correctly.
The images below compare the behavior when the project is loaded from QFieldCloud (left) versus from the local default QFieldCloud folder (right) on PC. Top in custom plugin, below in the nominatim-locator-v1.2 plugin packaged for cloud:
https://app.qfield.cloud/a/tyhol/Main
https://app.qfield.cloud/a/tyhol/Simple_nominatim
Beta Was this translation helpful? Give feedback.
All reactions