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

Panel text obscured on startup #34

Open
dizzib opened this issue Oct 24, 2014 · 22 comments
Open

Panel text obscured on startup #34

dizzib opened this issue Oct 24, 2014 · 22 comments
Assignees

Comments

@dizzib
Copy link

dizzib commented Oct 24, 2014

The panel text is obscured by subsequent widgets on startup:
panel1
Quick workaround is to enter Awesome Widget Settings then hit OK:
panel2

Also, for some reason the text becomes obscured again some time after I apply the workaround. The time can be anything from a few minutes to half an hour or so and it happens all by itself, even when I'm away from the computer. FWIW I'm on KDE 4.13.2.

When the text is obscured, a right-click to show the popup menu fails unless it's done at the extreme bottom of the panel.

@arcan1s arcan1s added the bug label Oct 24, 2014
@arcan1s arcan1s self-assigned this Oct 24, 2014
@arcan1s
Copy link
Owner

arcan1s commented Oct 24, 2014

yep there are some problems with painting interface since the latest version. I hope they will be fixed in the future releases. Sorry =)

But as for me, I have not seen to have problems with the painting after initialization. Is this effects similar to one in initialization? I can assume that it may be related to other widgets which grab all given free space.

@dizzib
Copy link
Author

dizzib commented Oct 24, 2014

No problem at all :)

Yes the after-initialization effect is identical to the first-initialization problem.

Interestingly the after-init problem hasn't happened since I switched back to running off SSD a couple of hours ago. Earlier I was running a clone of my system off a usb stick and I suspect this may have affected the disk monitor widget and caused the after-init problem. Needs further investigation.

Update: I spoke too soon, yesterday it happened a couple of times when running off SSD.

@dizzib
Copy link
Author

dizzib commented Oct 26, 2014

I'm sometimes able to make AW text disappear by clicking the panel cashew and moving the AW instance(s) around. Hopefully this might help you to reproduce the issue more easily.

Please let me know if you need any more info, but unfortunately for now this bug makes AW unworkable for me :(

@arcan1s
Copy link
Owner

arcan1s commented Oct 26, 2014

I may create hot fix (workaround) to avoid this issue. It is not clear fix, but should work. Hope I will implement this today, but you will need to build plasmoid from git.

@dizzib
Copy link
Author

dizzib commented Oct 26, 2014

Wow great! Let me know where to get it from when you're done and I'll give it a spin. I'm on Arch linux so hopefully I can simply hack the PKGBUILD.

arcan1s pushed a commit that referenced this issue Oct 27, 2014
@arcan1s
Copy link
Owner

arcan1s commented Oct 27, 2014

okay, try to build from git with the following PKGBUILD

@dizzib
Copy link
Author

dizzib commented Oct 27, 2014

That seems to be fixed now, great job!

Please forgive me for this but I find myself missing how the text used to sit with a transparent background overlaid above the other widgets since (1) it took up much less space and (2) looked really cool, so it's a pity this (accidental?) feature is no longer around.

To illustrate, here's my panel before this fix:
panel3

And after, where I've had to radically trim down the text:
panel4

Anyway this isn't a major issue just a nice to have, so closing as fixed.

btw the build didn't work until I grabbed the submodules manually but I've a feeling PKGBUILD-git could be doing this.

Thanks again!

@dizzib dizzib closed this as completed Oct 27, 2014
@arcan1s
Copy link
Owner

arcan1s commented Oct 27, 2014

Sorry about the submodules I forgot about them =) And I think that I can do the widget in foreground (hope it will be in one line patch)

@dizzib
Copy link
Author

dizzib commented Oct 27, 2014

That would be very cool indeed but no rush! Let me know if you need me to test.

@arcan1s
Copy link
Owner

arcan1s commented Oct 27, 2014

try now =)

@dizzib
Copy link
Author

dizzib commented Oct 28, 2014

Hmm no difference, AW is still taking up space as in my last pic above even after moving it around. Is there something else I need to do ?

Submodules are pulling correctly now.

@arcan1s
Copy link
Owner

arcan1s commented Oct 28, 2014

ok, I'll look at this again. But i want ask you what plasmoid is used to provide charts?

@dizzib
Copy link
Author

dizzib commented Oct 28, 2014

From left to right in my last pic there's AW instance 1, Network monitor, HW temp, CPU monitor (4 cells), AW 2, Memory status, Hard disk i/o (2 cells).

@arcan1s
Copy link
Owner

arcan1s commented Oct 28, 2014

are they default KDE charts?

@dizzib
Copy link
Author

dizzib commented Oct 28, 2014

Yes, in KDE 4.13.2

@arcan1s
Copy link
Owner

arcan1s commented Oct 29, 2014

i'm sorry, but I cannot reproduce it. It works normally for me (see the screenshot). I think that it is plasma-related issue. Did you try to add the AW after graphical monitors?
10

@dizzib
Copy link
Author

dizzib commented Oct 30, 2014

It doesn't matter where I place AW it never overlays its neighbours plus I just tried rebuilding with latest and still no joy. Out of interest what KDE version are you on ?

TBH I can live with it as-is so please don't waste too much time on this!

@arcan1s
Copy link
Owner

arcan1s commented Oct 30, 2014

latest (4.14.2)

@dizzib
Copy link
Author

dizzib commented Oct 30, 2014

Also worth noting I'm on qt4 4.8.6-1

I'll try upgrading my KDE and qt but this can't happen immediately since I'm in the middle of evaluating some other software.

@dizzib
Copy link
Author

dizzib commented Jan 9, 2015

Finally got round to upgrading to KDE 4.14.3 and qt4 4.8.6-4 but no joy I'm afraid. Even upgrading to AW 2.1.0 didn't make any difference.

@arcan1s arcan1s reopened this Jan 12, 2015
@arcan1s
Copy link
Owner

arcan1s commented Jan 12, 2015

okay

will look on it later (after/with releasing for KF5)

@dizzib
Copy link
Author

dizzib commented Jan 16, 2015

Thanks and please don't sweat it :)

I expect this to be a tough nut to crack if you cannot reproduce it so I've installed KDE/AW into an isolated virtualbox environment to help us test and diagnose it. Please let me know if you need any more info.

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

No branches or pull requests

2 participants