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
fix for location udig bug-166 #235
Conversation
(https://bugs.locationtech.org/show_bug.cgi?id=166) related to Map restoration from file Signed-off-by: Nikolaos Pringouris <nprigour@gmail.com>
It seems that the provided commit fixes the problem in windows OS. |
See my comments on the BUG 166 |
Hi @fgdrf,
|
@nprigour I tested today again and I was wondering that my build was quite fast :) Now I found out that I started an older compiled product than expected because I missed to use Finally I can confirm, that your fix works on MacOSX. Therefore I'm going to squash commits soon |
Just to clarify : Whenever a project resource (e.g. a Map) is deleted using the context menu in the layers view the resource on the filesystem is not deleted. Files of deleted resources are still present and are not removed closing uDig application. This is possible another issue .. |
@fgdrf shouldn't we also check it in a linux environment before accepting it? Concerning the deletion of resources in the file system it is another thing which however is to a large extend related to the solution we provide to this one. I have filed a seperate bug report on that (see https://bugs.locationtech.org/show_bug.cgi?id=168) and will soon provide a fix via a pull request provided that the present pull request is tested in all major platforms (windows, macOS, linux). |
Fix verified successfully also in Linux (Ubuntu) environment. |
fix for location udig bug-166
(https://bugs.locationtech.org/show_bug.cgi?id=166) related to Map
restoration from file