Post

Replies

Boosts

Views

Activity

GKAccessPoint view can't be accessed to lock orientation
Hi, the GKAccessPoint view can't be accessed so there's no way to override its orientation when we want to lock it into a specific one. Unfortunately the GKAccessPoint respect only the supported interface orientations set in the Info plist at build time, but what if I want to support them all at build time and then at runtime only lock in one or another based on my game settings? Unity can let me lock the orientation of the game at runtime but the GKAccessPoint only respects the supported interface orientations and so with the autorotation enabled ignore the lock set by Unity allowing the orientations to change based on the device rotation. Unity confirmed there's no way to access the GKAccessPoint view so there's no way to override its orientation and make it respect a certain lock in one of them. Is there a way to make the GKAccessPoint respect an orientation lock set at runtime? If yes how can that be done? If no what does that entail? That a game supporting all the orientations need to support them all dynamically and so it can't lock the game in one of them based on the game settings? If that's a mandatory requirement of the GKAccessPoint then can the documentation about it be amended with this important restriction? Thanks in advance for the help. Silvio
0
0
450
Mar ’21
GKAccessPoint frameInScreenCoordinates returns wrong NSPoint origin on macOS
Hi, when showing the access point on macOS 11+ the frameInScreenCoordinates property returns a NSRect which has a NSSize size of (52,52) pts and an NSPoint origin of (5,5) pts. The size is right but the position is clearly off. Besides the origin stays 0 pts on the Y axis for a while and then changes to match the X axis at 5 pts. I need pixels instead of points so at the beginning I thought it was a conversion issue and I took care to use the convertRectToScreen on the parentWindow in order to respect the high resolution guidelines of OSX. That returns me the same values in size and origin so it doesn't look to be a conversion issue. May anyone advice or check if there's any issue in this property of the GKAccessPoint API for macOS?
0
0
396
Mar ’21