-
Notifications
You must be signed in to change notification settings - Fork 7
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
Responsiveness #292
Comments
I wonder what circumstances cause what they describe, for me it's never been that bad ever. Flutter or React Native will probably help. A new backend won't or better routing won't. |
Better routing doesn't work?
I feel this has a lot to do with rendering multiple screens on top of each
other and not 'destroying activities' which according to John.
…On Thu, Sep 23, 2021 at 9:09 AM zond ***@***.***> wrote:
I wonder what circumstances cause what they describe, for me it's never
been that bad ever.
Flutter or React Native will probably help. A new backend won't or better
routing won't.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#292 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABXURGLHPH5KXRE76FO2ASDUDLHCPANCNFSM5ES7LUAQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
Hey yeah I think generally improving the react code base will help a lot. It is probably doing an insane amount of rerendering all the time. You can optimize the hell out of it. Just gotta get it cleaned up and well tested before doing proper optimization work. I don't think it has much to do with the wrapper hack that we are using. Mainly just messy React components constantly rerendering. |
I don't think they rerender that much - but they do retain a lot memory from being rendered on top of each other. But after you have cleaned up the code we'll see :) |
Feedback from the people over at "Legendary Tactics" is valid:
We gave the Cold War variant a try and I have to say that the experience was not good. We're playing on our PC's, and when we launched the game, it wouldn't respond to any amount of clicking around. When we choose a unit, the options for commands doesn't come up. We had to switch to phone mode (inspect) to be able to input orders. I was only able to view the map on a tiny window, which made it difficult to see the entirety of the map. As I was dragging the map around to see other parts, it was calling up the orders menu unintentionally. I didn't know what unit I'd accidentally clicked on, and so I ended up canceling orders that I'd already inputted. Have we done something wrong that we can't play on a PC from a web browser in normal viewing mode? If you can work out some of these issues, I think the barrier to entry on Diplicity would encourage more players in, and we could then create a video to support your platform.
The text was updated successfully, but these errors were encountered: