MacOS timeline is overwriting map canvas

[djhoese]

Users (including @sjoro and @rayg-ssec) have found that on some MacOS systems (all?) the Qt GUI is not behaving properly. The timeline QML widget seems to be "copied" where the map canvas (the vispy canvas) is and makes SIFT unusable. @rayg-ssec included this screenshot on an older copy of SIFT 2.0.0a0 where the entire window is placed inside the map:

It looks like napari has noticed this issue too and as suspected by Ray and others this is likely an issue with GL context sharing between Qt and VisPy:

napari/napari#2584

[gendjole24]

Hi, is there any news on this front? Pretty much the same issue on the MacOs 14.3.1 Sonoma. Looking forward to using SIFT on macbook. Thanks

[ScottLindstrom]

I can ask around. One of the SIFT developers is at present on leave, and I do not use Mac products. Thank you for alerting us to the issue with Sonoma Scott

…

________________________________ From: gendjole24 ***@***.***> Sent: Sunday, March 17, 2024 8:33 AM To: ssec/sift ***@***.***> Cc: Subscribed ***@***.***> Subject: Re: [ssec/sift] MacOS timeline is overwriting map canvas (Issue #377) Hi, is there any news on this front? Pretty much the same issue on the MacOs 14.3.1 Sonoma. Looking forward to using SIFT on macbook. Thanks — Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https://github.com/ssec/sift/issues/377*issuecomment-2002473217__;Iw!!Mak6IKo!MYAIGw9vo7IAAzcZghMb_bgViigEu4soHgrR7CT8uU_rJt-RFtU_hyGnIeJgvmK6Zaks2oVnn6igH-rdR_daPyVzot4$>, or unsubscribe<https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AD3IMP7QFDH43LN7FHURMVDYYWLUFAVCNFSM6AAAAAAZO2CGQOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMBSGQ3TGMRRG4__;!!Mak6IKo!MYAIGw9vo7IAAzcZghMb_bgViigEu4soHgrR7CT8uU_rJt-RFtU_hyGnIeJgvmK6Zaks2oVnn6igH-rdR_daFNoXylY$>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[djhoese]

I don't have a mac to be testing this and I also don't have any funding (or time) to be debugging this. Someone with a mac and the desire to have this fixed will need to dive down the debugging. It is possible that newer versions of mac, Qt, and/or vispy will automatically fix this.