Skip to content
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

Top Bar Icons Float to the Right After Resuming from Suspend #103

Open
golamrabbiazad opened this issue Aug 18, 2023 · 1 comment
Open

Comments

@golamrabbiazad
Copy link

When my computer wakes up from suspend mode, I've noticed a recurring problem with the extension. Despite my system settings being configured to display the top bar icons on the left side, they consistently shift to the right side of the top bar after resuming from suspend. This behavior is unexpected and contrary to my preferred layout.

For example, A picture of the issue would be more understandable.
topbar-icon-float-to-the-right

The extension position should be on the left side and the other icons on the right side. I have configured this on the shell settings but resuming from suspend makes reset the configuration.

If any additional information or logs are needed to diagnose the problem, please let me know and I'll be happy to provide them.

@golamrabbiazad
Copy link
Author

I have figured out this issue and found a hard-coded solution. The TopHat extension mounts early before all other GNOME shell extensions are loaded. This issue is valid when the TopHat extension position is on the "RIGHT" side. We don't need to worry about other mount positions.

I solved it by waiting 7 seconds for the tophat.addToPanel() method only when the extension position is on the "RIGHT" side. So, this shouldn't be solved this way because If I have more GNOME shell extensions, the hard-coded 7 seconds will not be valid. This approach is not precise and might lead to issues if the timeout is too short.

tophat.addToPanel() method to wait dynamically until the signal determines when all extensions are loaded.

To analyze if anyone has experience with gnome-shell development. How can we solve the issue dynamically?

Everyone's guidance and feedback are highly valued.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant