Back to Community Threads
1
open a file in the viewer and then maximize window don´t maximize
Question asked by Ralf Schiessl - 6/3/2020 at 5:33 AM
Answered
Hi,
if i dobleclick a file (e.g. PDF or Text or Image or ...) then it opens in a window. if click maximize on the richt top corner in this windot then the size is not maximized
What´s wrong?

6 Replies

Reply to Thread
0
Cem Alacayir Replied
6/4/2020 at 12:08 AM
Employee Post
We just released a new version which has some fixes related to this:

Version 7.4.2 - June 3, 2020

  • Added: Better child window management. Minimized windows will be stacked neatly at the bottom like a taskbar (no more on top of each other).
    Ensured position and size for minimized, restored, maximized states are always correct (e.g. when parent component is resized). Tooltips for long titles on minimized windows.
Note that, even with the latest, maximized size for a child window would be FileManager component's size though position is fixed now (the maximized window fits it's parent FileManager component). But we could change it to fit browser's viewport if that's what you are asking.
0
Ralf Schiessl Replied
6/4/2020 at 12:35 AM
Hi,
i think the viewport is the problem. if i maximize the window, the real size dont change, but i manually can change the size.
See in the image: this is maximized.
Thank you
Ralf
0
Cem Alacayir Replied
6/4/2020 at 1:36 AM
Employee Post
The actual problem here is the position of the maximized and v7.4.2 fixes that so it will be the same size but it will be over the FileManager component (maximizes inside its parent).

However it seems it's better to allow maximize to viewport instead of parent component in the next version.
0
Cem Alacayir Replied
6/4/2020 at 1:56 AM
Employee Post
Here is a temporary fix:

<!DOCTYPE html>

<html>
<head runat="server">
    <title>Client-side events</title>

    <script type="text/javascript">

        function fileManagerLoading(sender, e) {
            var fileManager = sender;
 
            //Temp fix for maximizing to viewport, not to parent component.
            Ext.override(fileManager, {
                createChildWindow: function () {
                    var childWindow = this.callParent(arguments);
                    childWindow.floatParent = null;
                    return childWindow;
                }
            });
        }

    </script>
</head>
<body>

    <GleamTech:FileManagerControl ID="fileManager" runat="server" 
        Width="800"
        Height="600" >
        
        <ClientEvents Loading="fileManagerLoading" />
        
    </GleamTech:FileManagerControl>

</body>
</html>
0
Ralf Schiessl Replied
6/4/2020 at 2:45 AM
Perrfect, it works - thank you
0
Cem Alacayir Replied
6/15/2020 at 2:58 AM
Employee Post Marked As Answer
FYI, with latest Version 7.4.5 - June 15, 2020, you no longer need the above workaround (remove it):

  • Improved: Child windows will always maximize to browser's viewport instead of parent component.
    Minimized windows will be stacked also vertically when they do not fit parent component's width.
    Ensured minimized windows are aligned and sized correctly after parent component is hidden and then shown.
Back to Community Threads

Reply to Thread