Bug 12512 - OpenTK BindBufferFrame Disparity Between iOS and Androd
Summary: OpenTK BindBufferFrame Disparity Between iOS and Androd
Alias: None
Product: Android
Classification: Xamarin
Component: BCL Class Libraries ()
Version: 4.7.x
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Radek Doulik
Depends on:
Reported: 2013-06-03 00:48 UTC by Anuj Bhatia
Modified: 2014-06-03 13:48 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Anuj Bhatia 2013-06-03 00:48:02 UTC
THe two APIs for the BindBufferFrame are different across iOS and Android. Android does not contain the FrameBufferTarget parameter option.

·         public static void BindFramebuffer(FramebufferTarget target, int framebuffer);
Comment 1 dean.ellis 2014-05-20 11:01:24 UTC

This is probably something you've fixed in the consolidation branch
Comment 2 Radek Doulik 2014-06-03 13:48:17 UTC
Yes, that is fixed. It will be in the next release.