Marble Declarative Data Layers , wich has decrared in QML, does not show any dynamic changes in the its model. All changes in the model will be showed on the MarbleWidget after you restart your application (with MarbleWidget ). For example: You add new item to the model (which has binding with DataLayer in QML) and this item should be immidiantly showed on the map. But the item will be showed only if you restart the application. If you change any item propertyes: coordinates, color, text, size, etc. all you changes will be showed also after you restert your application On the branch "sok-2012-plasma-active" all works ok (MarbleWidget shows all changes in the DataLayes ' s model immidiantly) Reproducible: Always Steps to Reproduce: 1. Get marble from branch KDE/4.13 2. build as QTONLY and install it 3. build and run DynamicLayer.qml from marble/examples/qml/data-layers Actual Results: The item adding and removing to the EarthquakesModel is happening, but the map is empty. Expected Results: Added to the model items should be shown on the map. On the branch "sok-2012-plasma-active" all works OK. My application where I found the Bug works very similar, that the examle "DynamicLayer"
Sorry, I have make many mistakes... Marble Declarative Data Layers , which were declared in QML, do not show any dynamic changes in their model. All changes in the model will be shown on the MarbleWidget after you restart your application (with MarbleWidget ). For example: You add new item to the model (which has binding with DataLayer in QML) and this item should be immediately shown on the map. But the item will be shown only if you restart the application. If you change any item properties: coordinates, color, text, size, etc. all your changes will also be shown only after restarting your application On the branch "sok-2012-plasma-active" everything works ok (MarbleWidget shows all changes in the DataLayes ' s model immediately)
Git commit f32b0ec976f350b025f0a0dda93f98afa2476fc7 by Dennis Nienhüser. Committed on 06/06/2014 at 18:29. Pushed by nienhueser into branch 'master'. geonames now requires a username parameter M +1 -1 examples/qml/data-layers/EarthquakesModel.qml http://commits.kde.org/marble/f32b0ec976f350b025f0a0dda93f98afa2476fc7
With the commit above the DataLayers.qml example works fine here. Is there any similar easy example to reproduce the problem? If it's related to changing properties of existing items the earthquake model might not show the bug because it only adds new items but does not modify existing ones.
Git commit ee8e347055e405ec7b81448ae38c0bde52edb9c7 by Dennis Nienhüser. Committed on 06/06/2014 at 18:29. Pushed by nienhueser into branch 'KDE/4.13'. geonames now requires a username parameter (cherry picked from commit f32b0ec976f350b025f0a0dda93f98afa2476fc7) M +1 -1 examples/qml/data-layers/EarthquakesModel.qml http://commits.kde.org/marble/ee8e347055e405ec7b81448ae38c0bde52edb9c7
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!