You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm pretty new to this, but I found that I couldn't get XBPageDragView to init properly when referenced from my root viewcontroller's view in the app storyboard. The problem was that when the NIB loader calls setViewToCurl, the frame of the viewToCurl has not yet been set (perhaps this is because I'm using auto layout?).
I managed to establish that calling refreshPageCurlView from viewDidAppear will work around this, but we do then have a bunch of false init where the frame is 0,0,0,0 and hence the OGL framebuffer inits fail.
It still works, but I'm thinking that the setter for viewToCurl should not be calling refreshPageCurlView and we should be doing this from somewhere else instead.
The text was updated successfully, but these errors were encountered:
That might be because of auto layout since I didn't face this issue and I also didn't test it with auto layout before. What I think that should be done is to recreate the mesh in -[XBCurlView layoutSubviews] if the size changes, and the frame buffer and the mesh should not be created if the size is zero. layoutSubviews must be called after the view gets its actual size then this should work.
Hi,
I'm pretty new to this, but I found that I couldn't get XBPageDragView to init properly when referenced from my root viewcontroller's view in the app storyboard. The problem was that when the NIB loader calls setViewToCurl, the frame of the viewToCurl has not yet been set (perhaps this is because I'm using auto layout?).
I managed to establish that calling refreshPageCurlView from viewDidAppear will work around this, but we do then have a bunch of false init where the frame is 0,0,0,0 and hence the OGL framebuffer inits fail.
It still works, but I'm thinking that the setter for viewToCurl should not be calling refreshPageCurlView and we should be doing this from somewhere else instead.
The text was updated successfully, but these errors were encountered: