AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Lego digital designer move camera10/27/2022 I am aware of some plugins openly violating this, and in the future we may intentionally kill the app immediately when this happens, rather than have plugins introduce race conditions and re-entrancy that show up as really really mysterious crashes later that we can’t understand. #LEGO DIGITAL DESIGNER MOVE CAMERA FULL#Re: threading: the plugin SDK is absolutely not thread safe and it is illegal to call any XPLM routine from a thread OTHER than the thread we called you from, full stop. Please file bug reports for the above 3 VR bugs. This leads to strange errors when trying to draw in VR windows.Ĥ) Non-VR, please see here in the second post: ///index.php?/forums/topic/145871-question-about-thread-safety-of-xplmscheduleflightloop/ However, if you ask for the window’s geometry, it will report the restricted coordinates as if it were never resized by the user. The further away from the center, the bigger the error.ģ) If you set a resize policy on a VR window, it has no visual effect: The user can resize the window. Also, this leads to an invalid affine transformation when trying to convert mouse coordinates from boxels to pixels. This doesn’t happen for non-VR windows with decoration. This is due to the border decoration being subtracted from the geometry. The other messages get correct coordinates.Ģ) If you create a new window using the new API in VR, the actual window size as reported by GetGeometry is smaller than what you requested. Three are related to VR, the other is not:ġ) If you create a window using the new API, the mouse handler will get passed the coordinates of the real mouse instead of the VR pointer in the DRAG message. During my development of a VR plugin, I believe to have found four bugs in the API.
0 Comments
Read More
Leave a Reply. |