Vibrator

Corona Marketplace Corona Community Plugins
#21

It’s clearly the vibrator plugin and not the texttospeech plugin.

I removed the vibrator plugin from the app ->NO SUCCESS

I removed the vibrator plugin from build settings ->SUCCESS

I have tried both this:

 plugins = { ["plugin.vibrator"] = { publisherId = "com.spiralcodestudio", supportedPlatforms = { iphone=false, android=true } }, },

And this:

 plugins = { ["plugin.vibrator"] = { publisherId = "com.spiralcodestudio", supportedPlatforms = { iphone=true, android=true } }, },

Both fails. I have to remove the line completely for the app to build.

#22

This fails as well:

 plugins = { ["plugin.vibrator"] = { publisherId = "com.spiralcodestudio" }, },

Corona Simulator 2016.2980, freshly deauthorized/reautorized.

#23

Thanks, for reporting. I am looking into that since yesterday. The problem is that I use same utility files in many plugins, which collide with each other when app is built using several of them. It should be easy to fix, just need to find the right solution.

#24

Ok, thanks!

#25

Try now.

#26

Hi,

I’ve just tried again. With 2980. Deauthorized and logged in again to be sure to get the latest version of the plugin.

Unfortunately I still get a linker error (log attached).

#27

runewinse, thanks, I’ll fix soon.

#28

runewinse, please try now.

#29

Lerg, now it seems to link ok! Haven’t tried if the vibrator functionality works though… But I will, when I get my hands on some iOS devices.

Thanks!

#30

Hmm… I’m getting the same linking error again. Is it somehow related to the recent fixes in texttospeech?

Corona SDk 2987, and Sierra MacOS

#31

runewinse, yes! Will fix asap.

#32

Fixed, please test.

#33

Tested ok. Thanks!

#34

Hi Lerg!

I’m thinking about using the plugin but just wanted to know what happens if I call .vibrate() on a device that can’t vibrate. Does the plugin handle those situations without additional measure like .hasVibrator()?

Also, I’m curious if those functions could be used like haptic feedback on Android devices if I keep the duration short?

#35

Hi!
It won’t vibrate if you call .vibrate() on a non supported device.

The minimal duration and it’s feel highly depends on the device, generally I wouldn’t recommend using vibration for haptic feedback.

#36

Just to be sure, it won’t cause a runtime error or anything that would break the game, right?

#37

It didn’t break my game, but you should check vibrator.hasVibrator() nevertheless

Some of my players (very, very small percentage) get the following message:

Runtime Error

java.lang.NullPointerException: Attempt to read from field ‘android.os.VibrationEffect com.android.server.Vibrator Service$Vibration.mEffect’ on a null object reference

I don’t really know what that message wants to tell me, as I am just calling “vibrator.vibrate(int between 1 and 10)”

And I know that these players have already had a few vibrations, so it should work in general.

#38

Updated the plugin with a fix for Android 8.0 crash. Please update your apps.

Google deprecated a method I was using and apparently broke it.

#39

Congrats on the release Lerg!

#40

Thanks for a great plugin!

Is there any example code to use the Haptic feedback feature? I would love an example to show what’s possible