rajkumarmardubudee / flexpaper

Automatically exported from code.google.com/p/flexpaper
0 stars 0 forks source link

Android Tablet: fist page views in Portrait, 2nd and the rest in split #400

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Load a document in the view on an Android Tablet. With InitViewMode : 
'Portrait', setting
2. First page will be a single page in Portrait mode, the next will be in split 
mode.

What is the expected output? 

All pages in single page portrait mode. 

What do you see instead?

second page in split mode. 

What version of the product are you using? 

FlexPaper_2.2.3_c_customizable

On what operating system?

Debian.

Please provide any additional information below.

config : {
                        IMGFiles : '{{ file.view_url }}/{page}.png',
                        JSONFile : '{{ file.view_url }}/pdf.json',

                        jsDirectory: "{% static 'js/vendor/flexpaper/' %}",
                        localeDirectory: "{% static 'js/locale/flexpaper/' %}",
                        key: "{% settings_value 'FLEXPAPER_KEY' %}",

                        Scale: 0.6,
                        ZoomTransition : 'easeOut',
                        ZoomTime : 0.5,
                        ZoomInterval : 0.2,
                        MinZoomSize : 0.2,
                        MaxZoomSize : 5,
                        RenderingOrder: 'html',
                        InitViewMode : 'Portrait',
                        ViewModeToolsVisible: true,
                        ZoomToolsVisible: true,
                        NavToolsVisible: true,
                        CursorToolsVisible: false,
                        SearchToolsVisible: true,
                        FitPageOnLoad: true,
                        ProgressiveLoading: true,
                        Toolbar: toolbarData,
                        WMode : 'window'
                    }   

Original issue reported on code.google.com by andrew.s...@gmail.com on 20 Mar 2014 at 10:14

GoogleCodeExporter commented 9 years ago
Can not be reproduced in our upcoming 2.2.4 release so must have been a 
regression issue in our prev. build. 

Original comment by erik.eng...@gmail.com on 23 Mar 2014 at 11:36