commit/galaxy-central: jgoecks: Trackster: do not subset data with a message.
1 new commit in galaxy-central: https://bitbucket.org/galaxy/galaxy-central/changeset/e23be4cf5276/ changeset: e23be4cf5276 user: jgoecks date: 2012-02-07 23:29:31 summary: Trackster: do not subset data with a message. affected #: 1 file diff -r 63319bc07b56127bcd3c44ec6e950541c2c4aa0c -r e23be4cf5276a0570d784b3ade9fbad9f9fb351c static/scripts/trackster.js --- a/static/scripts/trackster.js +++ b/static/scripts/trackster.js @@ -520,8 +520,7 @@ // Look in cache for data that can be used. Data can be reused if it // has the requested data and is not summary tree and has details. // TODO: this logic could be improved if the visualization knew whether - // the data was "index" or "data." Also could slice the data so that - // only data points in request are returned. + // the data was "index" or "data." // // TODO: can using resolution in the key enable LineTrack data to be subsetted appropriately? @@ -534,9 +533,12 @@ entry_high = split_key[1]; if (low >= entry_low && high <= entry_high) { - // This entry has requested data; return if compatible. + // This entry has requested data; return if compatible and if entry does not + // have a message. If entry has a message, then not all data available and it + // is better to fetch anew. entry = this.obj_cache[key]; - if ( is_deferred(entry) || this.track.data_and_mode_compatible(entry, mode) ) { + if ( is_deferred(entry) || + ( this.track.data_and_mode_compatible(entry, mode) && !entry.message ) ) { // TODO: for fast lookup and processing, create new entry with only data subset? // Entry is usable. this.move_key_to_end(key, i); Repository URL: https://bitbucket.org/galaxy/galaxy-central/ -- This is a commit notification from bitbucket.org. You are receiving this because you have the service enabled, addressing the recipient of this email.
participants (1)
-
Bitbucket