podium | Communication is the key to any high performing team | Collaboration library

Your code is passing all three members as one member. Try moving the asterisk onto members

You need to getBoundingClientRect() of the target element and then subtract that from your event.clientX position to get the proper position of your mouse within the element.

Use pointer-events: none; to allow your mouse to click through your flashlight element to the underlying elements.

Note on your second question...

Your code is looking for the event.target for the mouseover and mouseout events, so when you add pointer-events: none, this now creates an event target for the child elements when they are hovered over, which are your img tags. The issue is that now the equation subtracting the client cords with the client bounding coords will change due to the target changing. So to alleviate this, you will need logic that accommodates for the children in relation to your parent element which is the relative compartment for finding where the flashlight element is located on the page.

So a fix is to add a class to your img tags class="img" then run a conditional to make sure the elements you are firing your event on are either the parent or its img children...

So, add a conditional to check the event.target.id is gameBox or classList.contains('img') each of these conditionals will be different: The parent element when mouseover will be e.target.getBoundingClientRect() and e.clientX/Y and subtract those to get the cursor position within the parent element, while the e.target.classLists.contains('img') conditional will get the parentNode of the e.target and then e.target.parentNode.getBoundingClientRect() and subtract it from the e.clientX/Y. So no matter the mouseover event, it will get the proper coords and display the flashlight coords in the element properly, while allowing you to click through using pointer-events:none css rule.

Not sure where documentElement came from, but it definitely not belong there..

Without it it seems to be working:

It's just a parameter on the Scene object. For an explanation of how to use them, read the relevant section in the docs (https://asciimatics.readthedocs.io/en/stable/widgets.html#exceptions).

The key example is as follows.

The problem is that you're calling screen.play when you're setting up the effects for the GameController. Don't do that. Just call play once at the end.

Here is problem values for en in column tweet_text are not lists, but strings repr of lists. So is necessary converting them to list, here by ast.literal_eval:

This might help please look into it

We could use pivot_longer to reshape to 'long' format, then do the count and reshape it back to 'wide'

The problem is that even the latest kibana 7 does not support nodejs 14, and requires nodejs 10.