Latest Contributions by WilliamMiller4

Hi Robert, I looked at the link you shared. From reading the article, it sounds like the resize event is the best option, but I'm having trouble implementing it. I have a modal panel, incorporating ideas from the splash widget, that works except for the screen rotation. Below are pictures of the panel (with a widget inside) upon first opening it in the orientation shown. Here is what they look like after rotation, respectively. I get the following error: Uncaught TypeError: b.call is not a function(…)     init.js:1355 I've attached my panel, along with the original modal panel that is presented in Create a new panel. Any thoughts would be appreciated and enjoy your first fall weekend of the year. William ... View more

Hi Robert, Thanks for the links. I had been planning to use the following to determine whether the device being used was mobile or not. (I think this logic is correct. I was referencing this GeoNet thread.)  if(isFullWindow()){    //true, mobile device } else {    //false, not mobile device }‍‍‍‍‍ where   function isFullWindow() {     if (window.appInfo.isRunInMobile) {         return true;     } else {         return false;       }     }‍‍‍‍‍‍‍ Now I need a way to determine if the screen orientation is portrait or landscape. Looking at the links you provided, it appears the best way to go about this is to use two media queries in the CSS. @media screen and (orientation: portrait){}, @media screen and (orientation: landscape){}‍‍ Is this the way you would go about solving the problem? I had hoped to make the changes in the JavaScript file. I see how dojo/has and dojo/sniff can help with determining the device being used, but not with screen orientation. Maybe I'm missing something... William ... View more

Thank you, Robert! ... View more

Hi Robert, I tried the code you supplied, but an uncaught reference error occurs: _openWidgetGroup is not defined I've added 'jimu/PanelManager','jimu/WidgetManager', 'dojo/_base/array' and 'dijit/_WidgetsInTemplateMixin', to define, along with their aliases. The only thing I changed in the functions was swapping 'TOC and Legend' with 'TestGroup'. I referenced the function with: _openWidgetGroup(); I'm not sure what I'm doing wrong. I'm working with WAB 2.0. Any assistance would be greatly appreciated. William ... View more

Hi Robert, Just checking: There is no support for opening a grouped widget programmatically, is there? Not just on load, but at any time. Thanks again for your help. William ... View more

Hi Robert, There's no need to reply to my last reply. I found an article​ that you commented on in June concerning the issue of opening a grouped widget on load and its unsupported nature. You might want to edit your last reply so it includes the additions I mentioned in my opening paragraph, which I'm pretty sure are needed. Thank you for your help and have a great weekend. William ... View more

Hi Robert, I was able to get the code to work after adding 'dojo/_base/array' and 'jimu/WidgetManager' to define, along with their aliases, and creating an instance of WidgetManager in the _getWidgetConfig function (this.wManager = WidgetManager.getInstance();). Standard widgets, like Legend, will open, however I get the following error when I look for a custom widget I created to open in a group: "Uncaught TypeError: Cannot read property 'id' of nullI". I added the following code to the support function to look for the widget in the groups section of the widgetPool: /*Check widgetPool.groups widgets*/ array.some(this.wManager.appConfig.widgetPool.groups.widgets, function(aWidget) {   if(aWidget.name == widgetName) {     widgetCnfg = aWidget;     return true;   }   return false; }); so the entire function reads as: _getWidgetConfig: function(widgetName){   var widgetCnfg = null;   this.wManager = WidgetManager.getInstance();   /*Check widgetPool.groups widgets*/   array.some(this.wManager.appConfig.widgetPool.groups.widgets, function(aWidget) {     if(aWidget.name == widgetName) {       widgetCnfg = aWidget;       return true;     }     return false;   });   if(!widgetCnfg){     /*Check widgetPool widgets if not found in widgetPool.groups*/     array.some(this.wManager.appConfig.widgetPool.widgets, function(aWidget) {       if(aWidget.name == widgetName) {         widgetCnfg = aWidget;         return true;       }       return false;     });   }   if(!widgetCnfg){     /*Check OnScreen widgets if not found in widgetPool*/     array.some(this.wManager.appConfig.widgetOnScreen.widgets, function(aWidget) {       if(aWidget.name == widgetName) {         widgetCnfg = aWidget;         return true;       }       return false;     });   }   return widgetCnfg; }, In the config file of my modified default layout, in my modified version of the FoldableTheme (eFoldableTheme, which also includes a new modal panel), I added the custom ModalTab Widget as follows, "widgetPool": {   "panel": {     "uri": "themes/eFoldableTheme/panels/FoldablePanel/Panel",     "position": {       "top": 5,       "right": 5,       "bottom": 5,       "zIndex": 5     }   },   "groups": [{     "widgets": [{       "uri": "widgets/ModalTab/Widget"     }],     "panel": {       "uri": "themes/eFoldableTheme/panels/ModalPanel/Panel",       "position": {         "relativeTo": "browser",         "zIndex": 102       }     }   }] }, and it generates in a new app config file as: "widgetPool": {   "panel": {     "uri": "themes/eFoldableTheme/panels/FoldablePanel/Panel",     "position": {       "top": 5,       "right": 5,       "bottom": 5,       "zIndex": 5,       "relativeTo": "map"     }   },   "groups": [     {       "widgets": [         {           "uri": "widgets/ModalTab/Widget",           "id": "widgets_ModalTab_Widget_34",           "IsController": false,           "name": "ModalTab",           "label": "ModalTab",           "index": 0         }       ],       "panel": {         "uri": "themes/eFoldableTheme/panels/ModalPanel/Panel",         "position": {           "relativeTo": "browser",           "zIndex": 102         }       },       "isPreconfiguredInTheme": true,       "id": "_33",       "visible": true,       "label": "ModalTab",       "icon": "widgets/ModalTab/images/icon.png",       "index": 2     }   ],   "widgets": [     {       "uri": "widgets/Legend/Widget",       "version": "2.0.1",       "id": "widgets_Legend_Widget_16",       "name": "Legend",       "label": "Legend",       "index": 0     },     {       "uri": "widgets/LayerList/Widget",       "version": "2.0.1",       "id": "widgets_LayerList_Widget_17",       "name": "LayerList",       "label": "Layer List",       "index": 1     }   ] }, I use 'ModalTab' when I call the _getWidgetConfig function, as follows. var pm = PanelManager.getInstance(); pm.showPanel(this._getWidgetConfig('ModalTab')); What am I doing wrong? How does one reference a custom widget in a group? As always, any help you can provide is much appreciated. William ... View more

Hi Robert, Does this code still work in Web AppBuilder 2.0? I keep getting "Uncaught TypeError: Cannot read property 'id' of undefined". I'm trying to open a widget, for example purposes the Legend widget, which is under widgetPool > widgets in my app's root config file. The "id" property has "widgets_Legend_Widget_16", so I am using your code as follows: define([... 'jimu/PanelManager'], function(..., PanelManager){   var clazz = declare([BaseWidget, _WidgetsInTemplateMixin], {     ...     onOkClick: function(){       ...       var pm = PanelManager.getInstance();       pm.showPanel(this.appConfig.widgetPool.widgets[16]);     },     close: function(){...}   });   return clazz; }); Any guidance is much appreciated. William ... View more

It's working for me too Robert. Thanks once again! William ... View more