Latest Contributions by BenFousek

Go for it. ... View more

Here's a fiddle of your layout. Seems fine to me. The only difference is I removed the height and width from the inner border container. Perhaps there is something with your javascript. ... View more

I suspect the absolute position on the map div may have been causing the problem. Being a code guy, you may find it easier to create your layout with code rather than with markup. All my apps have nothing more than [HTML]<div id="container"></div>[/HTML] for markup. The rest is all code. Here and Here Simple examples but you get the idea. Be sure to check out the dojo docs for dijit/layout as it has good examples. I'll certainly take a look at anything you post. Cheers. ... View more

You had an unnecessary div wrapping the footer. All non-center regions should have height or width set depending on top/bottom or left/right. Alternatively you can set the doLayout property to false. This will size the region to fit the content. This is most helpful for top/bottom regions. You had set position:absolute the map div. Center regions should never have position, width or height set (no region should have position property set). Let the border container do its job and handle position and sizing. Here's your markup as I would do it: <div id="container" data-dojo-type="dijit/layout/BorderContainer" data-dojo-props="design:'headline', gutters:false, style:'width:100%;height:100%;'">     <div id="header" class="roundedCorners" data-dojo-type="dijit/layout/ContentPane" data-dojo-props="region:'top', style:'height:50px;'">       This is the header section     </div>     <div id="left" class="roundedCorners" data-dojo-type="dijit/layout/ContentPane" data-dojo-props="region:'left', style:'width:275px;'">         This is the left section     </div>     <div id="center" data-dojo-type="dijit/layout/BorderContainer" class="roundedCorners" data-dojo-props="region:'center', gutters:false">         <div id="map" data-dojo-type="dijit/layout/ContentPane" class="shadow" data-dojo-props="region:'center', style:'padding:0;overflow:hidden;'"></div>         <div id="footer" class="roundedCorners" data-dojo-type="dijit/layout/ContentPane" data-dojo-props="region:'bottom', doLayout:false">             This is the footer section         </div>     </div> </div> I added a height to the header and doLayout to the footer as examples. ... View more

Try resizing your BorderContainer after adding the region. borderContainer.resize(); Any time you change the layout at the border container level you need to resize. For good measure, I resize right before creating the map and as the last thing called during initialization. If you add regions or show/hide regions you should resize as part of those operations too. Those differences in location you're seeing are probably equal to (in pixels) the size of the region your adding. There's something about border containers with the map as center region that doesn't update when layout geometry changes. Where the map thinks it is on the screen and where it really is are different. ... View more

Call toggle() on the title pane. titlePane.toggle(); ... View more

The reference did have some errors in regard to this. I gave notice in this thread http://forums.arcgis.com/threads/101566-API-Reference-Error. It appears to me it's been fixed. ... View more

You're welcome. ... View more

It looks like your class is a utility-like class. Maybe you have more methods and such you didn't share, but you can forgo declare and just return an object. Then you don't need to create the class to use it, instead just use its methods directly: define([     "esri/tasks/QueryTask",     "esri/tasks/query" ], function (     QueryTask,     Query ) {     return {         doFind: function (featureUrl, meterId, queryString) {             //do stuff         },         doSomethingElse: function (a, b) {             //do stuff         }     }; }); require(['myClasses/utility'], function (utility) {     utility.doFind(a, b, c); }); ... View more

I'm not sure why you are iterating the results when I assume you are returning a single feature. Second queryTask.execute is a deferred. Your return meterCoor; is being returned before the task is executed. Try: queryTask.execute(query, function (results) {     return results.features[0].geometry.x + "," + results.features[0].geometry.y; }, function (e) {     console.log(e);     return e; }); You can also create your own deferred and handle results or error outside the class: doFind: function () {     var deferred = new Deferred();     var query = new Query();     var queryTask = new QueryTask(this.featureUrl);     query.where = this.queryString + " = '" + this.meterId + "'";     query.returnGeometry = true;     query.outFields = ["*"];     queryTask.execute(query, function (results) {         deferred.resolve(results);     }, function (e) {         console.log(e);         deferred.reject('something has gone wrong');     });     return deferred; } ... View more