You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This isn't about 1.1.0 either, I tried with everything from 0.5.0 (currently in the live demos) to 1.1.0.
If you just raise all the consoles so that they're not halfway under the floor, you see that logs (1) all the logs actually start in the middle of the panel, and don't look right until they hit the bottom, (2) the black panel (panel #2 from the left) has text go off the bottom of the screen (3) that second problem seems caused by it being declared as instead of , as it's the only one that does that (4) when I try to use this in my personal project, I get text scrolling off the top and the bottom both, and get different behavior when I declare it as vs . (5) declaring with means you have to manually declare the background plane and such, which is poor user experience for the dev and unnecessary/redundant/technically not documented I think? (6) it caches errors by default, but errors also break it and cause messages to go off screen and scroll amount to be wrong
For now I can work around it, but I had to mess with it for a few hours to figure out all the quirks that were going on.
The text was updated successfully, but these errors were encountered:
kylebakerio
changed the title
log is pretty broken in a few ways
log component is pretty broken in a few ways
Dec 27, 2020
This isn't about 1.1.0 either, I tried with everything from 0.5.0 (currently in the live demos) to 1.1.0.
If you just raise all the consoles so that they're not halfway under the floor, you see that logs (1) all the logs actually start in the middle of the panel, and don't look right until they hit the bottom, (2) the black panel (panel #2 from the left) has text go off the bottom of the screen (3) that second problem seems caused by it being declared as instead of , as it's the only one that does that (4) when I try to use this in my personal project, I get text scrolling off the top and the bottom both, and get different behavior when I declare it as vs . (5) declaring with means you have to manually declare the background plane and such, which is poor user experience for the dev and unnecessary/redundant/technically not documented I think? (6) it caches errors by default, but errors also break it and cause messages to go off screen and scroll amount to be wrong
For now I can work around it, but I had to mess with it for a few hours to figure out all the quirks that were going on.
The text was updated successfully, but these errors were encountered: