Skip to content

Conversation

@tcardlab
Copy link
Owner

No description provided.

tcardlab and others added 30 commits November 6, 2019 15:00
Must pass cssProps to all elements utilizing transition-move.
turn 1, 9/11/19 through turn 17 9/27/2019
troubling. I want filtered and show to be seperate states. but x is calculated on show. i could make a displayed state and a show state. Then filtering just overrides displayed(setDisplayed) if its not empty?
Beware when +&- child are desplayed, but not parent. they collapse and with nothing between them, they overlap... Not much I can do atm. maybe something like:

const test = Math.abs(xConst[xConst.length-1])===1&&xConst.length>1&&!_.isEmpty(state.filtered)?Math.sign(xConst[xConst.length-1]):0
return sum+test

idk...
If zero is not present in search results, pseudoZero will add the appropriate displacement based on the sign of branch under calculation.

Additionally, if search result length is 1, then pseudoZero will not be calculated.

Fixed isActive flase-positive during search. It is now disabled.
v-model on page updates values.
watcher tracks changes and triggers updates.
updateCache() calculates new values.
I wanted to add the necessary data to this file to keep it localized and easier to access. However, mixins are not meant share data, just funtionality like  methods.
As a result they are not terribly reactive. The two solution I wish to try are making it a global mixin and adding it back to vuex perhaps as a module.
moving the slider explodes the console with hundres of nonsense function calls...
Still lots to figure out as it revives mixin/Vuex hybrid.
Will pursue both pure Vuex and hybrid.
again this is probably bad form, mixins shouldnt be used to share data.
But just wanted to try.
I have moved most dependancies to vuex.

I have had to add updateCache to multiple locations:
CollapseState.vue(onChg), Paths.vue(toggleChildren), Search.vue(filteredList), VGitGraph(created)

now pass coords attribute to VGitGraph sub-component

Paths.vue gets dispCoords from cache.

Next:
- remove DisplayMixin.js, maybe make coordinate module
- maybe try $store.watch again to remove update cache from everywhere and help centralize code.
Computed may be better if it needs to be updated when new content is added though... ?
"Computed properties are cached based on their reactive dependencies. A computed property will only re-evaluate when some of its reactive dependencies have changed." – from the docs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants