Closed GoogleCodeExporter closed 9 years ago
Original comment by magreenb...@gmail.com
on 31 Oct 2011 at 6:10
[deleted comment]
Issue 420 , merged into issue 236 could also be solved by a CefApp interface. If I can give CefInitialize an interface for handling .PAK files that's ok.
The interface could be a stream interface, for example:
virtual bool Open(std::wstring filename, int OpenMode);
//Openmode 1=read, 2=write, 3=read/write
virtual unsigned __int64 GetSize();
virtual unsigned __int64 GetPosition();
virtual bool SeekBegin(__int64 position);
virtual bool SeekCurrent(__int64 position);
virtual bool SeekEnd(__int64 position);
virtual bool Read(void* data_out,int bytes_to_read, int& bytes_read);
virtual bool Write(void* data_in, int bytes_to_write, int& bytes_written);
virtual bool Close();
virtual int GetLastError();
virtual void GetLastErrorDescription(std::wstring& description);
GetLastError() returns an interface specific error. GetLastErrorDescription can
be used to build a usable error message.
Original comment by Mirco.Ba...@gmail.com
on 18 Nov 2011 at 4:10
Original comment by magreenb...@gmail.com
on 23 Nov 2011 at 7:11
Revision 394 adds a new CefApp interface that provides global handlers and gets
passed to CefInitialize.
Original comment by magreenb...@gmail.com
on 23 Nov 2011 at 10:47
Original issue reported on code.google.com by
magreenb...@gmail.com
on 31 Oct 2011 at 6:10