| Summary: | Code is always being generated for VE but shouldn't | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Justin Spadea <jspadea> |
| Component: | EDT | Assignee: | Huo Zhen Zhong <huozz> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | chenzhh |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Justin Spadea
Is this the same behavior as in RBD? Hi, Justin It works as in RBD, I think it is reasonable. Think about one scenario, if we generate different code for design tab and preview tab, when user switch from one tab to another, we need to regenerate the code, that will make VE slow. So I think that's why in RBD, the egl.setWidgetLocation() is always generated. That function is NOT always generated in RBD. It is only generated for the VE and not for the file written to disk (which is used by debug). When the VE is generating JS on the fly, it should pass some parameter to the generator that indicates "enable egl.setWidgetLocation() generation". It has indirectly fixed by 358855, in which the egl.setWidgetLocation() will only been generated in the temp file. Verified |