1. #1
    Sencha User
    Join Date
    Apr 2010
    Posts
    7
    Vote Rating
    0
    cirkovic is on a distinguished road

      0  

    Exclamation gwt ckeditor in collapsible panel problem

    gwt ckeditor in collapsible panel problem


    I use gwt-ckeditor in layout container in window.
    When window collapse and then return to its previous size, ckeditor is inactive and all text is cleared.
    Does somebody know why this is happening and how to solve it..

    This is picture before collapsing or minimising window
    pre.jpg

    and this is after
    posle.jpg

    Thanks in advance!

  2. #2
    Sencha User
    Join Date
    Jul 2009
    Location
    Trabzon
    Posts
    99
    Vote Rating
    0
    harun is on a distinguished road

      0  

    Default


    I have the same problem. it is absolutely GXT desktop application fault. when you minimized then maximized the window new instance coming. I couldn't solve. maybe someone knows problem...

    Sven can solve this problem....
    Website: harunates.com
    Blog: blog.harunates.com
    Feel free to contact me harun@harunates.com

  3. #3
    Sencha User
    Join Date
    Apr 2010
    Posts
    7
    Vote Rating
    0
    cirkovic is on a distinguished road

      0  

    Wink


    You helped me with that information!
    Found a solution! You just need to disable ckeditor while window is inactive

    For collapse and restore (if you have collapse button on your window) add those handlers
    Code:
    addListener(Events.BeforeCollapse, new Listener<BaseEvent>() {
    
    			@Override
    			public void handleEvent(BaseEvent e) {
    				getCkEditor().setDisabled(true);
    			}
    		});
    
    
    		addListener(Events.Expand, new Listener<BaseEvent>() {
    
    
    			@Override
    			public void handleEvent(BaseEvent e) {
    				getCkEditor().setDisabled(false);
    			}
    		});
    For minimize and restore (Restore event activates only when windows was maximised, so you have to use Show)
    Code:
    addListener(Events.Minimize, new Listener<BaseEvent>() {
    
    
    			@Override
    			public void handleEvent(BaseEvent e) {
    				getCkEditor().setDisabled(true);
    			}
    		});
    
    
    		addListener(Events.Show, new Listener<BaseEvent>() {
    
    
    			@Override
    			public void handleEvent(BaseEvent e) {
    				getCkEditor().setDisabled(false);
    			}
    		});

  4. #4
    Sencha - GXT Dev Team
    Join Date
    Feb 2009
    Location
    Minnesota
    Posts
    2,640
    Vote Rating
    80
    Colin Alworth is just really nice Colin Alworth is just really nice Colin Alworth is just really nice Colin Alworth is just really nice Colin Alworth is just really nice

      0  

    Default


    The GXT 'bug' has to do with how the Window is handled when it is not shown. The hide() method on Window removes it from the dom to prevent any leaked memory, and show() adds it again, which causes the iframe to be loaded again.

    Generally, as cirkovic found, whatever you are loading should have some way of storing its state.

    If you have no such way, then hide() and show() are not for you - use styling to hide and show the window instead. You will need to manually remove the window from the dom when finished with it.

    Edit: one other option that should work is subclassing the Window and assigning removeFromParentOnHide to false. I haven't tested this, but it appears that this will prevent the window from being removed, and the frame from being reloaded.

Thread Participants: 2

Tags for this Thread

film izle

hd film izle

film sitesi

takipci kazanma sitesi

takipci kazanma sitesi

güzel olan herşey

takipci alma sitesi

komik eğlenceli videolar