search

daimajia / AndroidViewHover

An elegant way to show your menu or messages.
3.21k stars 722 forks source link

Blur behaves weird #7

Closed ghost closed 9 years ago

ghost commented 9 years ago

I've been trying to add this library to my project but I'm either too dumb to use it or there is a bug that seems to only affect my project...

This is my Code to show the HoverView:

View newView = mInflater.inflate(R.layout.card_back, null); BlurLayout oldView = (BlurLayout) mNowLayout.findViewById(id); oldView.setHoverView(newView); oldView.setBlurDuration(500); //Adding Animations oldView.showHover();

My actual problem is visible in the attached picture. As you can see there is the blurred version of the text & images underneath an unblurred version of the text & images. It might just be me doing something wrong but if that is the case I'm absolutely clueless about what I'm doing wrong.

screenshot_2014-09-20-15-18-29

daimajia commented 9 years ago

Could you send me a apk to my mailbox? I want to have a try.

ghost commented 9 years ago

I'll do it but it's currently really unstable as I've changed a lot of stuff in XML which isn't represented in the Code yet.

Basically every button on the card will lead to a crash besides the menu button which will enable the blur (Should have really gone with OnClickListeners and not the onClick function in XML^^).

daimajia commented 9 years ago

It's ok, I just want to see the effect and try to figure out the reason.

daimajia commented 9 years ago

It's really weird cause I tested in my project, it works well.

Could you please paste your layout xml here?

rrr

ghost commented 9 years ago

Okay, that's weird.

The following gist contains the xml for the card_layout. I've already tried removing the redundant RelativeLayout. But that doesn't change the behavior. So I've added it back to better track which change might actually solve the problem. If you also need the layout file for the hoverview I'll add it, too ;)

https://gist.github.com/budsmile/b1ed1c2e04585d44a30a

ghost commented 9 years ago

Forget about it. It's a bug inside my app (I'm not exactly sure why this bug lead to the behavior but it's definitely my fault). Sorry for bothering you.