Fix double click card enlarge #500
Labels
No labels
_CRITICAL_
API
app
backEnd
Blocked, waiting for further changes
bug
cleanup
close
design
duplicate
enhancement
feature request
frontEnd
help wanted
invalid
low priority
needs input
needs review
project documentation
question
research
reviewed
script
security
SQL
style
testing
topLevel
wontfix
No milestone
No project
6 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Andras/BoundlessFlowCampus2K#500
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This functionallity caused issues and where removed, it is now implemented with some minor flaws. When resizing, the card gets "wrong" size, it also covers other cards on the grid.
The function was added to the file "SaveGrid.js".
Could I be assigned to this? I created the first version.
#488 #489
@b24hugst I think that they wanted to create the team branches before fixing the function and I am certain that you will be assigned the issue!
Relevant issue: #270
Be sure to close this once it works as intended.
team_1_week_3to #500-fix-card-enlargementI saw after the merge that the vertical compactor got removed. The one that automatically pushes cards up the top when there's space.
How important is it that we have no compactor? Because it becomes much harder to implement this with no compactor because a lot of manual "pushing away" logic must be done to not have any overlap. Unless we could revert back to having vertical again.
If it's very important that we have no compactor I can try to do some manual logic, otherwise the function works again as shown in the video, and it now only works while in edit mode.
Although there is a small problem where when expanding a card that's positioned in the far-right, it will switch one position to the left when shrinking (I show this at the end of the video).
Since we are not the team that removed vertical compactor i would like to have a discussion with the other team to see how important that feature is, i personally love the double click expansion feature.
I think a meeting is for the best. I've seen it removed, added and rebranded. I think it is fine, if it would work as intended, but when I see people interacting with it, it seems to have weird side effects.
I remember a issue that when selecting the URL in the schedule view it would enlarge because when marking the url field in the View one would double click to select all. What I'm getting at is that it sometimes is in the way. I don't really know what a solution to that would be, but maybe it could only be possible to enlarge outside of edit mode? If we have a problem that it behaves weirdly on the right side of the page, maybe we could remember the position of when it is small and revert back to that? Maybe we could make the card take the entire page, kinda like a modal? How often do we think people would enlarge several cards?
I'm just spitballing here but it might be worth to take a step back and reevaluate what we need or want.
I believe that having no compactor is necessary, since the "dashboard" feeling is somewhat lost without it. If we find that we lose a lot of functionality because of this I think it would be fine adding vertical compacting, but not specifically and only to support this.
I 100% agree with Tim!
I like the idea of a card taking up an entire page because I see this feature more as a simple quality-of-life tool used on the spot, rather than something for structuring cards. As the resizing function already handles that purpose much better.
Very good points! if i have interpreted this discussion correctly i would say that we are leaning towards having a pause to this issue, right? We are also figuring out how to grid is going to dynamically change to be responsive towards mobile devices and i feel like that is more in the focus as for now.
I can't reproduce the error. I close this issue.