B4A Library Floating Action Button

corwin42 · Jan 9, 2015

This library is a B4A wrapper of this Floating Action Button library. The original library is released under the MIT license. The wrapper library contains parts of the NineOldAndroids project for the show/hide animations.

See the Floating Action Button description in the Material Design Guide how to use Floting Action Buttons in your app.

Installation

Copy the jar and the xml files to your custom libraries folder.
Copy the b4a_floatingactionbutton folder to the folder where you keep your resource files for custom libraries.

The library should be compatible with Android API 7 and up. No other libraries are required (it does not depend on AppCompat).

Usage

Because the library uses resources we have to tell B4A where to find them with the #AdditionalRes attribute:

B4X:

#AdditionalRes: <Path to your Customlib resource files>\CustomLibsRes\b4a_floatingactionbutton, de.amberhome.objects.floatingactionbutton

The Floating Action Button is implemented as a CustomView for the B4A designer or you can add it by code like all other internal B4A views. Depending on the type of the Floating Action Button (TYPE_NORMAL, TYPE_MINI, see Type property) the view has a size of 56x56dip or 40x40dip.

There are several properties you can set like the color of the button or which icon to use. See the examples for better understanding.

B4X:

    Fab1.Icon = xml.GetDrawable("ic_add_white_24dp")
    Fab1.Color = Colors.RGB(30,50,190)
    Fab1.ColorPressed = Colors.RGB(50,70,210)
    Fab1.ColorRipple = Colors.RGB(90,110,250)
    Fab1.Type = Fab1.TYPE_NORMAL

    'Set the offset of hide position. This is the amount the FAB moves on hide.
    Fab1.HideOffset = 100%y - Fab1.Top
    Fab1.Hide(False)

Versions

V1.00

initial version

corwin42 · Feb 26, 2015

Which device and which android Version do you use?

I get this:

nadhiras · Feb 26, 2015

corwin42 said:
Which device and which android Version do you use?

I get this:
View attachment 32510

iam using android 4.4
i try on real device that running os 4.4 same like on emulator
my emulator use geniemotion gogle nexus 7 with 4.4 OS
and my real device samsung galaxy alpha with 4.4 Os too

corwin42 · Feb 27, 2015

Ok, I can now reproduce it.

As a workaround for now you need to disable the shadow for KitKat devices.

nadhiras · Feb 27, 2015

corwin42 said:
Ok, I can now reproduce it.

As a workaround for now you need to disable the shadow for KitKat devices.

Thanks U Corwin....

luke2012 · Feb 27, 2015

corwin42 said:
Ok, I can now reproduce it.

As a workaround for now you need to disable the shadow for KitKat devices.

Thanks for your workaround corwin42! It's in plan for a library update in order to fix the issue ?

corwin42 · Mar 16, 2015

nadhiras said:
Hi @corwin42
i tested FAB library with appcompact and ClsCheckList by informatix
the problem same like @luke2012

View attachment 32450

and this example project.. i use appcompactmenu example project.
FAB+APPCOMP+CHKLIST.zip

Ok, this took me 4 hours of my life and I was going mad while searching for this issue.

I found the problem but I didn't understand it completely.
The problem is that in your project folder under Objects/res/drawable-xxx you have a shadow.png which is write protected. The FAB uses a drawable named shadow.png which is located in the FAB resource folder. My understanding was that if I add the resources with #AdditionalRes and a package name the library will always use the resource from the resource folder with the package name. Seems I was wrong.

Maybe Erel can clarify things here how #AdditionalRes works exactly. I will ask him.

luke2012 · Mar 22, 2015

corwin42 said:
Ok, this took me 4 hours of my life and I was going mad while searching for this issue.

I found the problem but I didn't understand it completely.
The problem is that in your project folder under Objects/res/drawable-xxx you have a shadow.png which is write protected. The FAB uses a drawable named shadow.png which is located in the FAB resource folder. My understanding was that if I add the resources with #AdditionalRes and a package name the library will always use the resource from the resource folder with the package name. Seems I was wrong.

Maybe Erel can clarify things here how #AdditionalRes works exactly. I will ask him.

Probably also @Informatix that implemented clsChecklist class could help

In my projects I'm using also UltraListView class by @Informatix! I'll test FAB also on this class.

luke2012 · Mar 22, 2015

corwin42 said:
Ok, I can now reproduce it.

As a workaround for now you need to disable the shadow for KitKat devices.

@corwin42 where I can do this within the code of FAB ?
Thanks in advance!

corwin42 · Mar 25, 2015

luke2012 said:
@corwin42 where I can do this within the code of FAB ?
Thanks in advance!

There is no need for the workaround (though there is a shadow property in the fab object to disable the shadow).
The problem was a conflict with resources in the project.

luke2012 · Mar 26, 2015

corwin42 said:
Ok, this took me 4 hours of my life and I was going mad while searching for this issue.

I found the problem but I didn't understand it completely.
The problem is that in your project folder under Objects/res/drawable-xxx you have a shadow.png which is write protected. The FAB uses a drawable named shadow.png which is located in the FAB resource folder. My understanding was that if I add the resources with #AdditionalRes and a package name the library will always use the resource from the resource folder with the package name. Seems I was wrong.

Maybe Erel can clarify things here how #AdditionalRes works exactly. I will ask him.

Yes @corwin42. I agree with you that the right person for this clarification is @Erel.

corwin42 · Mar 31, 2015

luke2012 said:
Yes @corwin42. I agree with you that the right person for this clarification is @Erel.

We already have the solution and the answer is here.
In short words. It is expected behavior that library resources get overwritten by local resources. Maybe I will add a prefix to the libraries resources in a future version.

omidaghakhani1368 · Apr 3, 2015

Hi.
Thank you for your library it is good but i cannot test it
it get error android.content.res.Resources$NotFoundException: Resource ID #0x0
What's problem?

Peter Simpson · Apr 3, 2015

@omidaghakhani1368 please look under Usage in the first post and don't forget to add the folder called b4a_floatingactionbutton which can be found in FloatingActionButton_1_00.zip...

omidaghakhani1368 · Apr 4, 2015

Peter Simpson said:
@omidaghakhani1368 please look under Usage in the first post and don't forget to add the folder called b4a_floatingactionbutton which can be found in FloatingActionButton_1_00.zip...

Thank you but i look usage and i do your instruction

Peter Simpson · Apr 4, 2015

Okay attach your project to this thread.

omidaghakhani1368 · Apr 4, 2015

Peter Simpson said:
Okay attack your project to this thread.

Thank you i solve it

Claudio Oliveira · Jul 19, 2015

Hi @corwin42,

I'm trying to compile and test your FABListView sample project.

I've followed all the directions from post#1.
Lib files and res folder have been copied to the right places.
My "#AdditionalRes" statement is as follows:

B4X:

#AdditionalRes: D:\Documents and Settings\Claudio\Downloads\B4X\Basic4Android\AdditionalResources\b4a_floatingactionbutton, de.amberhome.objects.floatingactionbutton

Everything seems to be ok, but I always get this error:

B4X:

B4A version: 5.02 (1)
Parsing code.    (0.00s)
Compiling code.    (0.03s)
Compiling layouts code.    (0.00s)
Generating R file.    Error
invalid resource directory name: D:\Documents and Settings\Claudio\Downloads\B4X\Basic4Android\Samples\FABListView\resource\b4a_floatingactionbutton/drawable-xxxhdpi

My device is a Samsung Galaxy S4, with Android 5.0.1, and my desktop is a Windows 7 SP1.

Any ideas?

Thank you!

ArminKH · Jul 19, 2015

Claudio Oliveira said:
Hi @corwin42,

I'm trying to compile and test your FABListView sample project.

I've followed all the directions from post#1.
Lib files and res folder have been copied to the right places.
My "#AdditionalRes" statement is as follows:

B4X:

#AdditionalRes: D:\Documents and Settings\Claudio\Downloads\B4X\Basic4Android\AdditionalResources\b4a_floatingactionbutton, de.amberhome.objects.floatingactionbutton

Everything seems to be ok, but I always get this error:

B4X:

B4A version: 5.02 (1) Parsing code. (0.00s) Compiling code. (0.03s) Compiling layouts code. (0.00s) Generating R file. Error invalid resource directory name: D:\Documents and Settings\Claudio\Downloads\B4X\Basic4Android\Samples\FABListView\resource\b4a_floatingactionbutton/drawable-xxxhdpi

My device is a Samsung Galaxy S4, with Android 5.0.1, and my desktop is a Windows 7 SP1.

Any ideas?

Thank you!

download attached zip file then unzip and move that inside your project like this

then add this code for use additional res(exactly this code)

B4X:

    #AdditionalRes: ..\CustomLibsRes\floatingactionbutton\res , de.amberhome.objects.floatingactionbutton

then compile your project
if still any error appared then you should update your build-tools to latest version from SDK Manager

Claudio Oliveira · Jul 20, 2015

Hi @arminkh
Thanks for your help!
I did exactly what you suggested. Libs in the right place, all Android SDK tools are up to date, everything looks fine but the error's still there.

B4X:

#Region  Activity Attributes 
    #FullScreen: False
    #IncludeTitle: True
    #AdditionalRes: ..\CustomLibsRes\floatingactionbutton\res, de.amberhome.objects.floatingactionbutton
#End Region

Something captured my attention, though. On the R file generating step, the compilation process inserts a forward slash ("/") in the directory name, and I just can't figure out why. This obviously raises a directory name error. It should be a backslash ("\") instead.

B4X:

B4A version: 5.02 (1)

Parsing code.    (0.00s)
Compiling code.    (0.05s)
Compiling layouts code.    (0.01s)
Generating R file.    Error
invalid resource directory name: ..\CustomLibsRes\floatingactionbutton\res/drawable-xxxhdpi

Maybe @Erel can shed some light on this...

Thanks again, mate!

Claudio Oliveira · Jul 20, 2015

Solved!
Searching the forum, I've read some posts on the same subject. One of these says that only the last version of Android Build Tools should be installed.
As I had all Android Build Tools, I've deleted all but the latest version (22.0.1), and that's it.
Everything's up'n'running now.

B4A Library Floating Action Button

Attachments

Expert

Member

Expert

Member

Well-Known Member

Expert

Well-Known Member

Well-Known Member

Expert

Well-Known Member

Expert

Well-Known Member

Expert

Well-Known Member

Expert

Well-Known Member

Active Member

Well-Known Member

Attachments

Active Member

Active Member

Similar Threads

Privacy & Transparency

Privacy & Transparency