Pablo Rodríguez

Results 176 comments of Pablo Rodríguez

@Cimbali, here you have another sample for play when the page is entered and stop when the page is left: [uncompressed PDF file](https://github.com/Cimbali/pympress/files/7475984/uncompressed-a.pdf). The relevant PDF object reads: ``` 11...

> The auto-play is already working on your example @ousia, on v1.7.0b1. (At least if there’s a single media, on page 2 − I might be missing another one?) Many...

I wonder whether clicking on the slide to advance it could be considered as part of this issue.

> Strangely, the issue does not occur on the Ruffle extension's internal player page. Many thanks for your help, @n0samu. Do you mean https://ruffle.rs/demo/? If I drag and drop https://www.free-culture.tk/lfc-presentation.swf...

I think this regression may be a _Firefox_ issue drawing the frames. I’m not on _Windows_ now, but Chrome seems not to have any issue displaying the presentation. Thanks to...

@n0samu, playing directly https://www.free-culture.tk/lfc-presentation.swf, I get a first image such as: ![beforefullscreen](https://user-images.githubusercontent.com/203767/183971308-7c633e61-bf39-494f-97cb-eb8a8b0ac14d.png) It will be scaled perfectly fine to full screen (to the same image [I already attached](https://user-images.githubusercontent.com/203767/181077035-b9123dda-1334-4a72-affc-ef1e0c5cea45.png)). But going...

After checking myself the presentation in _Chrome_ (same computer as the original issue reported here), image is rasterized fine in both full and normal screen. So the culprit seems to...

Just it case it might help, here you have the resource info: ![ffox-img](https://user-images.githubusercontent.com/203767/184191564-429d6323-596c-4b1e-92df-9bc0d9435bf1.png) 1. Top left: _Chrome_ in full screen. 2. Top right: _Chrome_ in normal screen. 3. Bottom left:...

@Dinnerbonne, sorry for bothering you here, but I’d avoid polluting the PR with comments that may not be related. I guess that #7777 is not related to non-hardware accelerated graphics....

Even after #4273, miscalculated `Sound.duration()` is still there.