New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Map25: VTM0.15 #321
Map25: VTM0.15 #321
Conversation
telemaxx
commented
Apr 6, 2021
•
edited by wolfgang-ch
edited by wolfgang-ch
- VTM 0.15 - using commit ef2d2dd197e5395b200c6e68a03c3b0805140914
- scaled photos on/off (off is default for reduced resources) (menu item is not localized up to now)
main2master
main2main
main2main
…nal thumb but this was not the reason to remove it, this image was NEVER disposed -> SWT was running very fast out of handles when moving the tour chart slider as this would create a new image for every new slider position, discovered this issue with SWT sleak" This reverts commit d3e09e3.
main2main
main2main
main2main
main2main
many changes in Libs... ItemizedLayer Mutable marker
avoid nullpointer when photolist is empty
and avoiding nullpointer again. 1sr try was nor working.
main2main
seems so there is a tour import bug. When i have a fresh MT workspace and imported and saved a tour, tourbook stays empty Edit: problem of nattable. |
NatTable 2.0 should solve the problem |
NatTable 2.0 solved the problem |
Is the released version 0.15 c0d5f4a0cabe7cc6e8ea6cfbf30a1e39e0433984 used? |
no, I cloned the master from vtm. state yesterday. So it's a bit newer. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no, I cloned the master from vtm. state yesterday. So it's a bit newer.
You should write the commit ID which is used into the PR comment, that it could be verified. It is the same as when you get a stacktrace and do no know which version it was used because the code lines could be different.
* Copyright 2019, 2020, 2021 Wolfgang Schramm and Contributors | ||
* Copyright 2019, 2020, 2021 Thomas Theussing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of adding all years, just write the first and last year
2019, 2020, 2021
-> 2019, 2021
You can keep the current years until you update the file (and not forget it, which happens also to me)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i saw that already as i got the conflicting error while merging ;-)
vtm commit
ef2d2dd197e5395b200c6e68a03c3b0805140914
import net.tourbook.map25.Map25App; | ||
import net.tourbook.map25.Map25ConfigManager; | ||
import net.tourbook.map25.Map25View; | ||
|
||
/** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wolfgang, did you remember this problem:
d3e09e3#commitcomment-41469693
There you removed the scaling part. but that looks not good on my two W10 laptops and in my VMWare Linux.
Not sure where this depends on.
With scaling on, it looks good everywhere but shows more used resources in "sleak"
with scaling off, it is like in the last version.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wolfgang, did you remember this problem:
d3e09e3#commitcomment-41469693There you removed the scaling part. but that looks not good on my two W10 laptops and in my VMWare Linux.
Not sure where this depends on.With scaling on, it looks good everywhere but shows more used resources in "sleak"
with scaling off, it is like in the last version.
I tried to understand the photo painting, but giving up for now, why it isn't painted with a larger (not scaled) image.
Can you set the missing text, afterwards I will merge it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes of coarse.
should i call it :
"scaled photos"
or better
"force scaled photos"
because sometimes, like in you're case its always scaled.
should i add this line only to messages.properties and Messages.java or also in messages_de.properties?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should not call it scaled, because scaled could be larger OR smaller.
Also, I think we should look over the "Tellerrand" (don't know if there is an english word for it) and the user should be able to set/select the image size.
There may be fixed sizes, e.g. 160, 300, ... and a variable size.
When you are not yet implementing this sizing feature, then the checkbox label could be "Small photo" which you can also translate into german (very difficult task :-)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
checkbox and text is not ready yet
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is OK
* notSelectedTooltip = MAP_ACTION_SHOW_PHOTO_IN_MAP; | ||
* } | ||
* @Override | ||
* protected ToolbarSlideout createSlideout(final ToolBar toolbar) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Comments which are outside of a method are moved around by the code formatter, but not always.
I wanted to comment on your answer but now my prepared review comments are also commited, however I was finished with the review. |
* Revert "removed scaled thumb image, it had the same size as the original thumb but this was not the reason to remove it, this image was NEVER disposed -> SWT was running very fast out of handles when moving the tour chart slider as this would create a new image for every new slider position, discovered this issue with SWT sleak" This reverts commit d3e09e3. * reverted 'reverted "removed scaled image"' * Starting with upgrading VTM 0.15 many changes in Libs... ItemizedLayer Mutable marker * before deactivating some red code * ItemizedLayer<> removing <> for vtm 0.15 * reactivating changed mapbookmarklayer and avoid nullpointer when photolist is empty * photolayer modified to work with vtm 0.15 and avoiding nullpointer again. 1sr try was nor working. * Photoscaled On/Off * run save actions for modified files * Debug off * cleanup some codelines * latest vtm 0.15 updates * Map25: VTM0.15 (#321) * Revert "removed scaled thumb image, it had the same size as the original thumb but this was not the reason to remove it, this image was NEVER disposed -> SWT was running very fast out of handles when moving the tour chart slider as this would create a new image for every new slider position, discovered this issue with SWT sleak" This reverts commit d3e09e3. * reverted 'reverted "removed scaled image"' * Starting with upgrading VTM 0.15 many changes in Libs... ItemizedLayer Mutable marker * before deactivating some red code * ItemizedLayer<> removing <> for vtm 0.15 * reactivating changed mapbookmarklayer and avoid nullpointer when photolist is empty * photolayer modified to work with vtm 0.15 and avoiding nullpointer again. 1sr try was nor working. * Photoscaled On/Off * run save actions for modified files * Debug off * cleanup some codelines * latest vtm 0.15 updates Co-authored-by: top <top@MB14> * Map25: PhotoLayer-> Starting with Adjustable PhotoSize and save and restore state * Map25 Photoresize with working save and restore need some cleanup * resolving one confict * resolving conflicts... * solving more conflicts * Delete org.eclipse.jdt.ui.prefs Co-authored-by: top <top@MB14>