Bug 378156 - GeoDataPlacemarks are not repainted properly after setStyle()
Summary: GeoDataPlacemarks are not repainted properly after setStyle()
Status: RESOLVED WORKSFORME
Alias: None
Product: marble
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: marble-bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-27 13:17 UTC by Rafał Kozik
Modified: 2022-12-04 05:15 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Bug reproduction (1.90 KB, text/x-csrc)
2017-03-27 13:17 UTC, Rafał Kozik
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Rafał Kozik 2017-03-27 13:17:49 UTC
Created attachment 104758 [details]
Bug reproduction

Hi,

Marble branch: Applications/17.04
Platform: Ubuntu 16.10

I create two or more placemarks and later I update their icons by providing new, unique QImage objects. I expect all placemarks to have those unique icons but they are all the same.

This is how I update the icons:

QSharedPointer<GeoDataStyle> style(new GeoDataStyle(*place->style()));
auto image = QImage("/path/to/image");
style->iconStyle().setIcon(image);
place->setStyle(style);
widget->model()->treeModel()->updateFeature(place);

There is a workaround for this bug - add this line with a fake, unique path for each image:
style->iconStyle().setIconPath("/fake/unique/path/");

See the whole code in the attachment.

Best regards,
Rafał
Comment 1 Olle Lundin 2017-04-10 05:41:35 UTC
Seems to be the same problem as I reported in https://bugs.kde.org/show_bug.cgi?id=378188
Comment 2 Justin Zobel 2022-11-04 03:10:19 UTC
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!
Comment 3 Bug Janitor Service 2022-11-19 05:13:34 UTC
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!
Comment 4 Bug Janitor Service 2022-12-04 05:15:09 UTC
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!