Note that there are some explanatory texts on larger screens.

plurals
  1. POSencha touch 2 list inside a panel
    primarykey
    data
    text
    <p>Have a pretty common task to do where I need a search form above a list to display the results, the problem is that the list is not showing the results, the store and the proxy work correctly because when I use firebug to locate the list items the list always have height of 0px.</p> <p>I have already searched and the common ways to workaround this is to use a fit layout, but using that on the parent panel makes all look small as if the width used was 10px.</p> <p>I cant set a fixed height because I want the list to fill the remaining space, and neither the flex option cause that stretches the search form when I want that to use the default size of the buttons and input fields.</p> <p>Here is the config Im using on the view</p> <pre><code>Ext.define('MyApp.view.search.Search', { extend:'Ext.navigation.View', xtype: 'search_view', config:{ items:[ { fullscreen:true, scroll:false, xtype:'panel', title:'Search', items:[ { xtype:'searchfield', name:'search', label:'Search', }, { xtype:'container', layout:'hbox', width:'100%', margin:'3 0 0 0', defaults:{ flex:1 }, items:[ { xtype:'selectfield', options:[ {text:'Option 1', value:'opt1'}, {text:'Option 2', value:'opt2'} ] }, { xtype:'button', text:'Search', action:'search' } ] }, { xtype:'list', itemTpl:['{title}'], onItemDisclosure:true, plugins:[ { xclass: 'Ext.plugin.ListPaging' } ] } ] }, ], } }); </code></pre> <p>This image describes what Im trying to achieve, I took this screenshot by setting manually a height to the list container, as you can see it works the problem is that the list height doesn't fill the space below the form by default.</p> <p><img src="https://i.stack.imgur.com/UFpnA.jpg" alt="goal"></p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload