Search found 151 matches

by Lukappa
Wed Sep 28, 2016 4:40 pm
Forum: Help (v4.x)
Topic: BufferedRenderer breaks on sch 4.2.7 - locked cols & resize
Replies: 4
Views: 1887

Re: BufferedRenderer breaks on sch 2.4.7 - locked cols & res

:) yeah! 4.2.7... sorry too late last night
by Lukappa
Wed Sep 28, 2016 4:32 pm
Forum: Help (v4.x)
Topic: BufferedRenderer breaks on sch 4.2.7 - locked cols & resize
Replies: 4
Views: 1887

Re: BufferedRenderer breaks on sch 2.4.7 - locked cols & res

I just tested to remove stateful from window and it works.
Maybe it's not strictly related to scheduler... please let me know, I leave this post just to be sure you are OK.

Thank you
by Lukappa
Wed Sep 28, 2016 4:22 pm
Forum: Help (v4.x)
Topic: BufferedRenderer breaks on sch 4.2.7 - locked cols & resize
Replies: 4
Views: 1887

BufferedRenderer breaks on sch 4.2.7 - locked cols & resize

I've updated to 4.2.7 and I get some problem with Sch.patches.BufferedRenderer'. (I don't know if it's a scheduler or extjs related bug) It happens when I open a grid with locked columns (after resize of container) and it's similar to this one: http://www.bryntum.com/forum/viewtopic.php?f=35&t=7626&...
by Lukappa
Wed Sep 28, 2016 8:27 am
Forum: Help (v4.x)
Topic: Brytnum Scheduler 4.x State of Columns
Replies: 20
Views: 7566

Re: Brytnum Scheduler 4.x State of Columns

Just for Info, this should explain why cols need stateId: http://docs.sencha.com/extjs/6.0.2/classic/Ext.grid.column.Column.html#ext-grid-column-column_state-saving On a stateful grid, not only should the Grid have a Ext.grid.Panel#stateId, each column of the grid should also be configured with a st...
by Lukappa
Thu Sep 22, 2016 8:17 am
Forum: Help (v4.x)
Topic: Brytnum Scheduler 4.x State of Columns
Replies: 20
Views: 7566

Re: Brytnum Scheduler 4.x State of Columns

I remember that something with columns was not saved and I saw it was working only setting a stateid.
Honestly I didn't test latest version of extjs 6 without statid over cols and I'll do it asap and let you know
by Lukappa
Tue Sep 20, 2016 11:13 pm
Forum: Help (v4.x)
Topic: Brytnum Scheduler 4.x State of Columns
Replies: 20
Views: 7566

Re: Brytnum Scheduler 4.x State of Columns

Here the workaround to the workaround :roll: lockedGridConfig: { stateful: true, stateId : 'mylockedgrid', listeners: { columnschanged: function(ct) { var cols = ct.getVisibleGridColumns(), width = 0; for(var c in cols) width += cols[c].getWidth(); //min width always! if(width > 30) { ct.grid.setWid...
by Lukappa
Tue Sep 20, 2016 10:56 pm
Forum: Help (v4.x)
Topic: Brytnum Scheduler 4.x State of Columns
Replies: 20
Views: 7566

Re: Brytnum Scheduler 4.x State of Columns

The previous workaround has only 1 problem:
after showing/hidding some column, the lockedGrid will "remember" the last width, so no automatic resize of locked part! :x
by Lukappa
Tue Sep 20, 2016 10:51 pm
Forum: Help (v4.x)
Topic: Brytnum Scheduler 4.x State of Columns
Replies: 20
Views: 7566

Re: Brytnum Scheduler 4.x State of Columns

Ok, I found a quick workaround. It seems to be a state scope issue. To fix the wrong behavior just set this to the scheduler: ... lockedGridConfig: { stateful: true, stateId : 'scheduler-locked-grid-workaround' }, columns: [ { stateful: true, stateId: 'put-an-id-for-each-column-you-have', }...
by Lukappa
Tue Sep 20, 2016 10:40 pm
Forum: Help (v4.x)
Topic: Brytnum Scheduler 4.x State of Columns
Replies: 20
Views: 7566

Re: Brytnum Scheduler 4.x State of Columns

Inside my app (not the example) even leaving flex undefined and using fixed width for every col, it makes a white space when I hide some column.
by Lukappa
Mon Sep 19, 2016 8:14 pm
Forum: Help (v4.x)
Topic: Brytnum Scheduler 4.x State of Columns
Replies: 20
Views: 7566

Re: Brytnum Scheduler 4.x State of Columns

The examples uses the columnsummary example of 4.2.6 release. I added 1s of delay to ensure the provider is initialized at the time of viewport rendering. Open it with chrome, hide the 'Time allocated' column (dropdown menu of resources), reload the page: you will se the first column width is wrong,...