Sencha arquitect bug when setting the bind store config for a pagingToolbar

[lombardo]

When i set the store bind property to a pagingToolbar component, the design canvas goes blank, and i'm not able to see any other component

My workaround is to use the processConfig property like this:

processMyPagingToolbar: function(config) {
config.bind = {
store : '{myStore}'
};
return config;
}

[joel.watson]

I tried this in Sencha Architect 3.2.0.193 and it seems to be working as expected. Are you still experiencing this issue?

Thanks!
Joel

[marc.fearby]

Seems I have the same problem as described above. Coincidentally, I just posted a thread about the same symptom (I didn't know the cause then, though).

If I delete and unbind the store config for both my grid and paging toolbar, the form stays rendered properly.

[andersonjf]

This is happening to me as well. If I remove the store bind from the paging toolbar everything works as expected. This is a pretty serious issue because my project is large and has paging toolbars everywhere.

[andersonjf]

One more thing, this only seems to happen to stores that are not auto-loaded with data. If I auto-load the store or generate mock data for it everything works ok. Problem is these stores are not supposed to auto-load nor do I want them to have mock data in them. So it's still an issue that needs to be addressed.

Edit: Generating mock data that doesn't actually get exported also fixes the issue. I think that is the best work-around for now. Just make sure you set "show in design view only" when generating the mock data.

[marc.fearby]

I don't have my stores set to auto-load in Architect because each and every one of them pesters me for a username and password whenever I go to build the app. I wish we could turn off auto-loading in Architect.

[petr.felzmann]

I cannot reproduce it. Could you describe the issue with as simple as possible project, please? Or past here such simple fake project where it happens? Thanks!

[andersonjf]

This is still happening in Architect 3.5. Every single grid that uses a PagingToolbar must have the store bind defined in the processConfig otherwise all rendering for that view breaks in Architect. This is a terribly frustrating bug. As mentioned before, I think it has to do with the stores not being auto-loaded with any data.

[andersonjf]

Update: Architect 3.5 shows an error message when this happens.

Framework Error: Uncaught TypeError: store.getTotalCount is not a function

So it definitely seems to be related to Architect not being able to deal with an empty store having a PagingToolbar tied to it. Can this please be fixed? Architect should not require stores to have dummy data.

[petr.felzmann]

We are able to reproduce it and can confirm this is bug. Thanks for the report!