OSX Issues
Moderator: Kyete
Re: OSX Issues
As always late, but it's now released
- Alejandro
- Alejandro
Alejandro S. Canosa
Three Minds Software
Three Minds Software
Re: OSX Issues
An excellent update with significant improvements. I am a happy camper.Kanchou wrote:As always late, but it's now released
First observations:
- Way snappier response times (highly, highly enjoyable)
- Labels work
- Distance measurement works
- Travel route, works (had one crash when tweaking Bezier curves on a world-spanning route, cannot replicate)
- Railroads now save to OWM file
- No screen flips witnessed anymore
- No spinning wheel on Feature tool
- Pinch zoom works
- Command-Z works
- All this with BetterTouch Tool turned on
- Manually entering a number in zoom % not yet accepted
Sombrero off to the Three Amigos of Three Minds.
MacBookPro 13" w/ TouchBar on MacOs High Sierra 10.13.6
Intel Core i7 3.3 GHz (2 cores) RAM 16 GB
Intel Core i7 3.3 GHz (2 cores) RAM 16 GB
Re: OSX Issues
Extremely happy to hear that!!aotte wrote:An excellent update with significant improvements. I am a happy camper.
Will fix, ty!!aotte wrote: [*] Manually entering a number in zoom % not yet accepted
Will investigate. We've had ongoing issues on Windows too for this that I think are all fixed.aotte wrote: Current main wish is a better response of mouse positioning over items at different zoom levels. It feels that the further out you zoom the more sensitive placement becomes. It feels like the strike zone for an item should be bigger. This is especially noticeable when editing points on long routes or drawing long boundaries.
Thank you!! All 3 of us appreciate it!aotte wrote: Sombrero off to the Three Amigos of Three Minds.
- Alejandro
Alejandro S. Canosa
Three Minds Software
Three Minds Software
Re: OSX Issues
OK, a few more bugs I found and one pet peeve:
Bugs:
Why is it that with every object I create it is deselected just after I created it. I create it, go and tweak some settings, only to find out that those tweaks will only apply on the next one I draw. Aaarghh. I would love to have what I just created be the thing that is currently selected. In my brain that makes total sense.
Bugs:
- Feature tool droppings on canvas
- Long Path and Fill Path feature tools do not honor transparency of the feature
- Canvas texture setting is not restored in display after opening file, the file does keep the value and the dialog shows it properly, the display simple goes to solid color only
- Maybe not a bug, or related to the above, but any travel path that starts out on a landmass, but crosses the canvas to get to another part of the same landmass does not display the sections that cross the canvas.
- Feature lists are still not sorted
Why is it that with every object I create it is deselected just after I created it. I create it, go and tweak some settings, only to find out that those tweaks will only apply on the next one I draw. Aaarghh. I would love to have what I just created be the thing that is currently selected. In my brain that makes total sense.
MacBookPro 13" w/ TouchBar on MacOs High Sierra 10.13.6
Intel Core i7 3.3 GHz (2 cores) RAM 16 GB
Intel Core i7 3.3 GHz (2 cores) RAM 16 GB
Re: OSX Issues
Thank you for the feedback!!aotte wrote:OK, a few more bugs I found and one pet peeve:
Not sure what you mean?aotte wrote: [*]Feature tool droppings on canvas
This is a known issue that we are working to resolve. It's the rasterizer we use in OSX doing it.aotte wrote: [*]Long Path and Fill Path feature tools do not honor transparency of the feature
Will fix.aotte wrote: [*]Canvas texture setting is not restored in display after opening file, the file does keep the value and the dialog shows it properly, the display simple goes to solid color only
Yes, it's by design objects get clipped outside the landmass they belong to. What you can do is copy/paste the travel path outside the landmass and it will overlap it. We'll look into this though, seens it seems for travel paths we shouldn't clip them.aotte wrote: [*]Maybe not a bug, or related to the above, but any travel path that starts out on a landmass, but crosses the canvas to get to another part of the same landmass does not display the sections that cross the canvas.
This is odd. I don't seem to have that problem in our test systems.aotte wrote: [*]Feature lists are still not sorted[/list]
Around 15% percent of our users agree with you and the rest disagree . We probably should have is as a possible setting to auto select last item. Question: Would you want that just for drawn items? Seems having that for features would be annoying rather than helpful? Let us know and we'll try to add it.aotte wrote: Peeve:
Why is it that with every object I create it is deselected just after I created it. I create it, go and tweak some settings, only to find out that those tweaks will only apply on the next one I draw. Aaarghh. I would love to have what I just created be the thing that is currently selected. In my brain that makes total sense.
Thank you again!!
- Alejandro
Alejandro S. Canosa
Three Minds Software
Three Minds Software
Re: OSX Issues
If you place a feature on a landmass so that the landmass is the parent and let the Feature peek over the landmass on top of the canvas, deleting the feature leaves dropping on the canvas.Kanchou wrote:Not sure what you mean?aotte wrote: Feature tool droppings on canvas
What I currently do is start the travel route on the canvas and then go from there, but that feels like a workaround. I like your idea. Maybe make it a setting in the options of the travel route item. [x] Display route on parent onlyKanchou wrote:Yes, it's by design objects get clipped outside the landmass they belong to. What you can do is copy/paste the travel path outside the landmass and it will overlap it. We'll look into this though, seens it seems for travel paths we shouldn't clip them.aotte wrote: Maybe not a bug, or related to the above, but any travel path that starts out on a landmass, but crosses the canvas to get to another part of the same landmass does not display the sections that cross the canvas.
Well, some are and some aren't for me:Kanchou wrote:This is odd. I don't seem to have that problem in our test systems.aotte wrote: Feature lists are still not sorted
Of course, I would land in the 15% I would love a Preferences setting for that. Although I put the distinction between items that get drawn with multiple steps before I can see the effect or a single click. E.g. stamping a single feature down? Sure, I can see that having it selected would be come annoying when building a mountain range by hand. But if I was to use the Feature|Along Path tool, I would want it to be selected after I am done. This way I can adjust its points or fill path options, now that I can see what the effect is of my original selections.Kanchou wrote:Around 15% percent of our users agree with you and the rest disagree . We probably should have is as a possible setting to auto select last item. Question: Would you want that just for drawn items? Seems having that for features would be annoying rather than helpful? Let us know and we'll try to add it.aotte wrote: Peeve:
Why is it that with every object I create it is deselected just after I created it. I create it, go and tweak some settings, only to find out that those tweaks will only apply on the next one I draw. Aaarghh. I would love to have what I just created be the thing that is currently selected. In my brain that makes total sense.
Arnoud.
MacBookPro 13" w/ TouchBar on MacOs High Sierra 10.13.6
Intel Core i7 3.3 GHz (2 cores) RAM 16 GB
Intel Core i7 3.3 GHz (2 cores) RAM 16 GB
Re: OSX Issues
Ok, I'm super happy we have you, aotte. I'm super bad at catching bugs, it seems, and I also haven't had much time to play around with OWM recently.
Re: OSX Issues
Happy to help stefanstr.stefanstr wrote:Ok, I'm super happy we have you, aotte. I'm super bad at catching bugs, it seems, and I also haven't had much time to play around with OWM recently.
If we don't tell the Three Minds, they cannot fix it. Unless they go digging deeper themselves, which our Unix compadres will not appreciate.
Arnoud
MacBookPro 13" w/ TouchBar on MacOs High Sierra 10.13.6
Intel Core i7 3.3 GHz (2 cores) RAM 16 GB
Intel Core i7 3.3 GHz (2 cores) RAM 16 GB
Re: OSX Issues
Loving it so far.
A few OSX issues:
Undo Crashes!
The second you press undo or use the shortcut key, the software crashes immediately.
Doesn't Save Water Background
When I reload a map, it forgets the colour of the background, so I always have to reset the water's colour/texture
Colligate is... Weird
I assume this isn't the intended behaviour. if I choose to colligate several features together (so I don't have loads of mountains or trees on my features lists), it becomes incredibly blocky, filled with white boxes :s Is this a bug or am I using the wrong function to combine many map features into a single object? Zoom
If I use the scroll bars on the edge and drag anywhere, it immediately autozooms back to the top of the screen.
A few OSX issues:
Undo Crashes!
The second you press undo or use the shortcut key, the software crashes immediately.
Doesn't Save Water Background
When I reload a map, it forgets the colour of the background, so I always have to reset the water's colour/texture
Colligate is... Weird
I assume this isn't the intended behaviour. if I choose to colligate several features together (so I don't have loads of mountains or trees on my features lists), it becomes incredibly blocky, filled with white boxes :s Is this a bug or am I using the wrong function to combine many map features into a single object? Zoom
If I use the scroll bars on the edge and drag anywhere, it immediately autozooms back to the top of the screen.
Re: OSX Issues
Glad to hear! And thank you for the feedback!!GrimPWG wrote:Loving it so far.
A few OSX issues:
That's really odd. Is that with any map, even a simple one with just one or two items? Undo/redo causes a crash in the demo, but it should be working for the full version.GrimPWG wrote: Undo Crashes!
The second you press undo or use the shortcut key, the software crashes immediately.
Will fix. Thank you!GrimPWG wrote: Doesn't Save Water Background
When I reload a map, it forgets the colour of the background, so I always have to reset the water's colour/texture
It's a known issue. Something odd with the raster library in OSX. We're working to fix.GrimPWG wrote: Colligate is... Weird
I assume this isn't the intended behaviour. if I choose to colligate several features together (so I don't have loads of mountains or trees on my features lists), it becomes incredibly blocky, filled with white boxes :s Is this a bug or am I using the wrong function to combine many map features into a single object?
Noted. Thank you!GrimPWG wrote: Zoom
If I use the scroll bars on the edge and drag anywhere, it immediately autozooms back to the top of the screen.
Alejandro S. Canosa
Three Minds Software
Three Minds Software