summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--www/js/TimelineCtrl.js10
-rw-r--r--www/js/app.js4
-rw-r--r--www/templates/devoptions.html4
3 files changed, 7 insertions, 11 deletions
diff --git a/www/js/TimelineCtrl.js b/www/js/TimelineCtrl.js
index 803dc87c..f12cb077 100644
--- a/www/js/TimelineCtrl.js
+++ b/www/js/TimelineCtrl.js
@@ -311,9 +311,10 @@ angular.module('zmApp.controllers').controller('zmApp.TimelineCtrl', ['$ionicPla
console.log("*********************** TIMELINE MAIN ");
// maxItems will be ignored during timeline draw if its desktop
- // var maxItems = ($rootScope.platformOS == 'desktop') ? zm.graphDesktopItemMax: zm.graphItemMax;
+ var maxItemsConf = ($rootScope.platformOS == 'desktop') ? zm.graphDesktopItemMax: zm.graphItemMax;
+
var ld = ZMDataModel.getLogin();
- var maxItems = ld.graphSize || 200;
+ var maxItems = ld.graphSize || maxItemsConf;
ZMDataModel.zmLog("Graph items to draw is " + maxItems);
$scope.maxItems = maxItems;
@@ -493,11 +494,6 @@ angular.module('zmApp.controllers').controller('zmApp.TimelineCtrl', ['$ionicPla
var itemsPerPage = parseInt(data.limit);
var iterCount;
- // The graph seems to get very slow
- // even with 200 items. My data comes in pages from
- // the server - so to make sure I don't exceed 200 items
- // I figure out how many items the server returns per API page
- // and divide the # of items I want (currently 200) with # of items per page
// So iterCount is the # of HTTP calls I need to make
iterCount = Math.max(Math.round(count / itemsPerPage), 1);
ZMDataModel.zmDebug("TimelineCtrl/drawGraph: pages of data: " + pages + " items per page: " + itemsPerPage);
diff --git a/www/js/app.js b/www/js/app.js
index 222d14db..4c98d94d 100644
--- a/www/js/app.js
+++ b/www/js/app.js
@@ -36,7 +36,7 @@ angular.module('zmApp', [
largeHttpTimeout: 60000,
logFile: 'zmNinjaLog.txt',
authoremail: 'pliablepixels+zmNinja@gmail.com',
- logFileMaxSize: 10000, // after this limit log gets reset
+ logFileMaxSize: 20000, // after this limit log gets reset
loginInterval: 300000, //5m*60s*1000 - ZM auto login after 5 mins
updateCheckInterval: 86400000, // 24 hrs
loadingTimeout: 15000,
@@ -50,7 +50,7 @@ angular.module('zmApp', [
graphFillColor: 'rgba(151,187,205,0.5)',
graphStrokeColor: 'rgba(151,187,205,0.8)',
graphHighlightFill: 'rgba(0,163,124,0.5)',
- graphItemMax: 200,
+ graphItemMax: 2000,
graphDesktopItemMax: 2000,
monitorCheckingColor: '#03A9F4',
monitorNotRunningColor: '#F44336',
diff --git a/www/templates/devoptions.html b/www/templates/devoptions.html
index d089f7c4..2d267436 100644
--- a/www/templates/devoptions.html
+++ b/www/templates/devoptions.html
@@ -64,7 +64,7 @@
<div class="item item-input-inset">
Max. items for Timeline&nbsp;
<label class="item-input-wrapper">
- <input type="tel" placeholder="200" ng-model="loginData.graphSize">
+ <input type="tel" placeholder="" ng-model="loginData.graphSize">
<br/>
</label>
@@ -72,7 +72,7 @@
</div>
- <div class="item" style="background-color:#C8F7C5" ng-if="loginData.graphSize > 2000">
+ <div class="item" style="background-color:#C8F7C5" ng-if="loginData.graphSize > 5000">
<label class="animated fadeInDown item-text-wrap" >
A large value can affect timeline performance. If you find timeline performance slow, try reducing the value to 200 and work your way up from there.