I eventually made it up to their "Client Resolution Expert Center" who informed me that they've been able to reproduce the issues I'm having on their side with multiple 7540's and WD19DC's and that they've have many customers having the same issue and that their engineers are working on a Firmware/BIOS update which doesn't have a firm ETA, but "should" be next month. I've been working with Dell over the past month (we ordered this laptop a week before Christmas) on trying to get this dock to work, but it's extremely intermittent. We ordered a Dell Precision 7540 for the owner of our company which we haven't been able to deploy due to docking station issues with the WD19DC. Don’t editorialize titles or submit clickbait.ĭell Global: Manuals, Drivers, Hot Topics, and Top Solutionsĭell support on Twitter: product support:.No reposts, spam, self-promotion or rehosted content.No offensive, hateful, or low-effort comments. Only submissions that are directly related to Dell & Dell Technologies are allowed.Discord Filter Out Help Posts Only Show Help Posts Dell Website Meet the Dell Family ![]() For direct contact with Dell please see the "General Support" section below. Please note this subreddit is 100% unofficial. Feel free to ask questions that are support related or otherwise on anything related to Dell Technologies & we'll do our best to help you. If some devs are reading this I hope some kind of generic component could be provided that would handle this.Welcome to /r/Dell. Let me know if something like the above works for you. Pages.put(page, Executions.createComponents(page, comp, null)) if we don't find thie page in our map we create it and save it forĬomponent comp = Path.getComponent("/mainWindow/contentHolder") Pages.get(currentPageName).setVisible(false) WSearchView = (Window) Executions.createComponents("/test/search-view.zul", divWorkspace, void openDetailView() ", page) ![]() Selectors.wireComponents(view, this, false) * The window representing the 'detail' sub-view * The window representing the 'search' sub-view Public class MainViewVM Div divWorkspace The only alternative i have found is to make the windows visible/invisible instead of detach/setParent but this is not what we want. The same functionality could be achieved easily using SelectorComposers and the old data binder. I understand that the whole thing has to do with the lifecycle of each viewmodel's binder but i cannot find anything useful in the documentation. ![]() The main-view detaches the detail-view window and re-sets the search-view with parent the workspace div.Īt this point the search-view.zul stops responding and sends all commands to the main-view generating the following message: "cannot find any method that is annotated for the command close with in MainViewVM" ![]() The detail-view sends the global command 'reattachSearchView' to the main-view. The main-view detaches the search-view window and creates the 'detail-view.zul' with parent the workspace div. The search-view sends the global command 'openDetailView' to the main-view. The main-view creates the 'search-view.zul' with parent the workspace div. The main-view.zul contains a workspace Div. Sample source code at the end of this message.ġ. We are migrating an application from MVC to MVVM and i think we are stuck. I really need help with the following scenario.
0 Comments
Leave a Reply. |