PDF-XChange Editor crashes when double clicking on opened image with Select text tool.
Can anyone confirm?
Crashing on images
Moderators: TrackerSupp-Daniel, Tracker Support, Paul - Tracker Supp, Vasyl-Tracker Dev Team, Chris - Tracker Supp, Sean - Tracker, Ivan - Tracker Software, Tracker Supp-Stefan
- Tracker Supp-Stefan
- Site Admin
- Posts: 17929
- Joined: Mon Jan 12, 2009 8:07 am
- Location: London
- Contact:
Re: Crashing on images
Hello Logilink,
Thanks for the report, but I will need to ask a few questions first so that we can better understand the problem.
Where is that 'image' open? Is it an image inside the Editor? Is it a stamp or part of the base content?
Can you provide a sample file with which you manage to reproduce this, so that we can try at our end too?
Also - please make sure that you are using the current latest build of our products (332).
Regards,
Stefan
Thanks for the report, but I will need to ask a few questions first so that we can better understand the problem.
Where is that 'image' open? Is it an image inside the Editor? Is it a stamp or part of the base content?
Can you provide a sample file with which you manage to reproduce this, so that we can try at our end too?
Also - please make sure that you are using the current latest build of our products (332).
Regards,
Stefan
Re: Crashing on images
Actually it's triple click on image in the document. It can be inside a document or just opened directly (jpg/png). Triple click on the left image or the right one. Not crashing on stamps. Test file attached. Tested on b332.
- Attachments
-
- image crash test.pdf
- (162.8 KiB) Downloaded 46 times
- Tracker Supp-Stefan
- Site Admin
- Posts: 17929
- Joined: Mon Jan 12, 2009 8:07 am
- Location: London
- Contact:
Re: Crashing on images
Thanks Logilink,
Managed to reproduce, so asking our devs to check asap!
P.S. Seems like this has already been discovered and fixed - and the fix will be in build 333 due for release later this week!
Regards,
Stefan
Managed to reproduce, so asking our devs to check asap!
P.S. Seems like this has already been discovered and fixed - and the fix will be in build 333 due for release later this week!
Regards,
Stefan