- Posts: 1123
- Thank you received: 73
Microsoft Windows Phone 8.1 support ends (13 Jul 2017)
Microsoft has ended support for Windows Phone 8.1
Questions about iOS development and PDF
addAnnotBitmap doesn't work in 2.2.0
IP: 192.168.0.71
11 years 8 months ago #6539
by radaee
Replied by radaee on topic addAnnotBitmap doesn't work in 2.2.0
try this:
Code:
struct PDFV_POS pos;
[m_view vGetPos:&pos:x:y];
if(pos.pageno>=0)
{
PDFVPage *vpage = [m_view vGetPage:pos.pageno];
PDFPage *page = [vpage GetPage];
PDF_RECT rect;
rect.bottom = 300;
rect.left = x;
rect.right = y;
rect.top = 100;
if( page != NULL )
{
CGImageRef ref = [image CGImage];
PDFMatrix *mat = [vpage CreateInvertMatrix:self.contentOffset.x * m_scale :self.contentOffset.y * m_scale];
[mat TransformRect : &rect ];
BOOL result = [page addAnnotBitmap: ref :YES :&rect];
Matrix_destroy(mat.handle);
[m_view vRenderSync:pos.pageno];
[m_doc save];
[self refresh];
}
}
IP: 192.168.0.71
11 years 8 months ago #6544
by Rossi
Replied by Rossi on topic addAnnotBitmap doesn't work in 2.2.0
No, it doesn't work. It's the same before, the first insert is ok but the others crashes the app.
IP: 192.168.0.71
11 years 7 months ago #6773
by Rossi
Replied by Rossi on topic addAnnotBitmap doesn't work in 2.2.0
Hi, there is news about this problem? I use the latest beta release but the problem persist.
IP: 192.168.0.71
11 years 7 months ago #6776
by radaee
Replied by radaee on topic addAnnotBitmap doesn't work in 2.2.0
Page object obtained from PDFVPage are not persist object.
you shall always get Page object from PDFVPage every time.
Page object obtained from PDFVPage will freed after vRender invoked.
you shall always get Page object from PDFVPage every time.
Page object obtained from PDFVPage will freed after vRender invoked.
IP: 192.168.0.71
11 years 7 months ago #6814
by Rossi
Replied by Rossi on topic addAnnotBitmap doesn't work in 2.2.0
Well, I do understand this but, the point is a crash in accessing m_cache status after I had a bitmap annotation.
It seems that the problem is connected with this line of code:
Matrix_destroy(mat.handle);
Commenting it out, we have no immediate crash with EXC_BAD_ACCESS, but I guess this could cause memory problems later?
It seems that the problem is connected with this line of code:
Matrix_destroy(mat.handle);
Commenting it out, we have no immediate crash with EXC_BAD_ACCESS, but I guess this could cause memory problems later?
Time to create page: 0.363 seconds