Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
If you set the config options at admin/config/content/qtip to Click instead of Hover, it doesn't seem to make a difference in the DnD library. Still appears on hover. Our users are annoyed by how sensitive the hover is, so changing to click was supposed to be a quick/easy solution. Any ideas?
Comment | File | Size | Author |
---|---|---|---|
#15 | add-option-to-pull-qtip-settings-from-instance-2375505-15.patch | 3.17 KB | gifad |
#4 | add-option-to-pull-qtip-settings-from-instance-2375505-4.patch | 3.6 KB | nagy.balint |
Comments
Comment #1
scotwith1tIf it's not possible to respect the settings there, can the scald implementation at least use hover intent or only show qtip on hovering on the thumbnail? It's just way too sensitive and the preview covers up content when you don't necessarily want to see the preview.
Comment #2
scotwith1tI've been able to modify the settings by adding my own config to a custom module in the Drupal.dnd.qTipSettings definition. In case someone else needs to do this, it's pretty simple.
Comment #3
nagy.balint CreditAttribution: nagy.balint commentedThanks for sharing, worked like a charm.
Comment #4
nagy.balint CreditAttribution: nagy.balint commentedHere is a patch that solves the problem, by adding an option to select an instance in the dnd settings form, and then using that instead of the default settings for qtip v2.
I've removed the deprecated code for qtip v1, as the 1.x branch is not supported for a long time now, so its time to move on.
Comment #6
nagy.balint CreditAttribution: nagy.balint commentedComment #8
gifad CreditAttribution: gifad commentedClarification may be necessary about qtip versions : I was using qtip drupal module version 7.x-1.5, with qtip jquery library version 2, and this gave php errors : Obviously, the qtip module v2 is required; After installing and enabling latest qTip 7.x-2.0-rc3, it was still stuck on :
, which I had to remove...
Or am I missing something ?
Comment #9
gifad CreditAttribution: gifad commentedSolved by :
as suggested in qtip release note.
But this is still totally obscure to me..
Comment #10
gifad CreditAttribution: gifad commentedActually, the issue was already detected : #2248337: No Libary preview , with a better workaround
Comment #11
nagy.balint CreditAttribution: nagy.balint commentedAye i had that patch applied already.
Indeed that should be specified that we need that patch, or we need to somehow push that patch in qtip :)
Comment #12
nagy.balint CreditAttribution: nagy.balint commentedThe patch got into qtip dev, so now we can continue reviewing this patch.
Likely we can make it clear in the README and other documentation that the qtip functionality needs the latest dev of the module.
Comment #13
nagy.balint CreditAttribution: nagy.balint commentedIt seems the deprecated code for qtip v1 was included due this module https://www.drupal.org/project/menu_minipanels
Which has a 2.x branch now without qtip, but not what most users are using.
So for them this would be a bad change to remove support for qtip v1... on the other hand, qtip v1 does not have support for instances, and then we would need to detect the version in php as well.
I still think its time to move on from v1 as its not supported for a long time now...
Comment #14
nagy.balint CreditAttribution: nagy.balint commentedI guess for the time being we can reintroduce compatibility by checking for function_exists('qtip_fetch_instances_field') in php, and putting back the qtip1 js code the same way it was before.
Then it will work in qtip1 just without the instances settings. And if the user wants the new capability, can switch to qtip2 with the dev release.
Comment #15
gifad CreditAttribution: gifad commentedJust made a patch which works with both legacy qtip 7.x-1.5 and latest qtip 7.x-2.0-rc3+2-dev
Comment #17
nagy.balint CreditAttribution: nagy.balint commentedThanks!
Committed.