Galaxy provides you with a total of three events and procedures that can toggle if a component is clickable or long clickable. The only reason I came up with this small extension is because long clicking on components you never want to long click on causes your device to vibrate if enabled.
* Excluded from my open-source policy.
ComponentClick
Delegated when a component that was registered as clickable, was clicked.
ComponentGenericClick
Delegated when a component that was registered as being “fully clickable,” was clicked.
ComponentLongClick
Delegated when a component that was registered as long clickable, was long clicked.
SetClickListener
Set whether the given component is clickable.
SetGenericClickListener
Set whether the given component is “fully clickable.”
SetLongClickListener
Set whether the given component is long clickable.
If you have version 0.1.1 or are starting with Galaxy, it is recommended to download Galaxy 1.0.1! The minimum API is 21.
You are mistake. User has the rights to suggest or ask if they found similar. If not no issue. Let the painter paint. You know your algorithm. As a user when we see outside the both extension it seems to be similar. I am not good in Java or extension development.
Mods will decide whether i am promoting the extension or asking
It doesn’t matter if you’re advanced in either of these… The blocks look completely different.
It doesn’t matter if you’re asking… It you are promoting, people are going to click on your link. There was no need to ask, it’s nowhere close to the extension you promoted.
Still you mis read my post.No issue.
Your extension is free, the extension i asked about (found it while searching for another extension) is paid one. If so users will prefer yours or paid one?. If you ask me i will say free only.
But then if you knew developers would choose the “free” over “paid,” then why’d you even “ask” about it. There’s nothing similar, it’s clear in their screenshots of the blocks.
SetGenericClickListener – This is similar to the “Full Clickable” property for card views.
Setting enabled to true will result in only the arrangement being clickable, not it’s children views. The “Clickable” property for the arrangement doesn’t have to be true.