New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improvements for custom events in tables like visitor log #5189
Comments
thanks for feedback
If you can show me screenshot showing that it is confusing, I'm interested
PS: when you create Task / Feature requests, please put them in 2.X backlog as we try to keep current milestone for bugs only and very important feature requests we want to work on. thanks! |
Attachment: example for 1b |
Attachment: example for 2 |
the larger margin on the left for event (child) is already nearly there:
|
Attachment: left margin for events |
looks great now! |
some more feedback on custom events in tables like vistor log:
maybe on should change the separation-sign "-" between the parameters (category,
action, name and value) because it maybe confusing if you have
the same sign
a) within one of these 4 parameters
b) before the number in the value field if you are using a negative number
e.g. to track the unfolding and refolding of an element with the values
+1 for making the hidden content visible (unfolding)
-1 making the content unvisible again (refolding)
maybe one do not really need to show the blue url link in brackets at each event because the events shown should be on the same page as the "parent" page url shown above
=> to make this parent(page)-child(event)-structure more clear one could set the events with a larger margin at the left (intend).
a greater line width for the event symbol may make it look stronger and better noticeable
The text was updated successfully, but these errors were encountered: