Any news on this bug???
Type: Posts; User: hpet
Any news on this bug???
I have a fiddle here: https://fiddle.sencha.com/#fiddle/5uo
If you drag "card-schedule south panel", it should preaty much act like parent container splitter. Should not act on "card-schedule...
Hm. I want splitter to be constrained, but not by container it is rendered to, but by some parent container - allowing me to be dragged beyond its own container - kind of absolutely positioned...
I have center and south region.
South region also has center and south region with splitter.
By default splitter in south panel in south region is constrained to container it is rendered to.
I am looking for a way to manage in-line editing where editor is a bit more complex than one field.
More specificaly I am using rowexpander and within rowxpander I have template. When user clicks...
I checked field types again and they are all working if I disable mouseover menu handler.
If you try the fiddle with different extjs versions and different field types as cell editors you should...
Turns out this is a layout issue. Field MUST be wrapped in container component which handles field layout properly. Complex fields like Time, Date, etc. depend heavly on.
I am having render difficulties while extending DatePicker component.
I would like to add "timefield" bellow days table.
Problem is that timefield renderes with default width, ignoring my settings....
No, not like this.
Try this fiddle to reproduce: https://fiddle.sencha.com/#fiddle/511
1. when you enter cell editor, it gets focus as expected, but as soon as you...
For simplicity and usability issues I decided to put editable grid (small two column, max 3 rows) into a menu container.
Everything apears to be ok except mouse movement seems to take focus away....
My end solution was without using extra dataview's inside rowexpander. I found a way to do it with simple templates and all is well - so far :)
Thanks. Didn't know about rowwrap before. As it is...
Maybe something changed in versions. Wouldn't know.
Is it working now?
what is your store and grid config?
This is most likely your css error. Try using "background-repeat: none;" on your icon style.
Be sure to have correct root element, field names and dataIndex.
It is preaty standard stuff, so it is most likely a silly thing like this.
I am trying to setup some "lightweight" tabular data inside rowexpander body.
Using template and overwrite would be lightest I guess, but I do need some mouseover control. I guess next most...
Sorry, I will try to explain again.
I have one XTemplate that I want to use on a two different places (containers).
Basicly these two containers show the same data, but I would like...
I would like to use one XTemplate in multiple components with minor difference - how could I determine in which component template runs? ...like if (component1) then show this, else show that.
Yeah, I figured it out.
What I am trying to do is to render form into a custom html wrapper.
Is there any easy way to define custom component wrapper in component config?
I read about renderTpl,...
I have a closable tab panel with west center and east regions.
In "afterrender" event of an east region container I create a new form component and render it to the html fragment...
I think this might be browser issue.
I was trying to prepare a simple case and I hit something I think it could be bug in Chrome (Windows).
Plain grid with remote autoLoad store.
1. Loading mask automaticaly shown with default loading message "Loading...".
2. When store loads records:
- loading message is hidden: display:none
Extjs 4.2.1 - this could be related to mask not adjusting itself when browser is resized:
Example: Basic grid with remote data using autoLoad... LoadMask appears and dissapires as expected - at this...
Sorry, maybe I was a bit unclear. It is most likely not a leak in extjs, but in the app it self. So my question is how do you usually search for this? Stripping everything out and slowly putting it...
I have "tabbed" interface and just recently I've noticed that opening/closing new tab leaves me 2 orphans somewhere. Checking with alert(Ext.ComponentMgr.all.length) I get 2 components being left...