Closed (fixed)
Project:
Simple hierarchical select
Version:
7.x-1.6
Component:
User interface
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
15 Apr 2013 at 18:01 UTC
Updated:
4 May 2013 at 16:20 UTC
Hi,
My client does not like the default fading effects. He does not like the fact that when loading the view, the filter is first hidden and then slowly appears in fade in effect. Then when selecting a parent term with children, he thinks the second select appears too slowly.
How can I modify these effects without my changes being gone when upgrading to next version in the future?
Thank you!
Comments
Comment #1
nicolas bouteille commentedI also would like to add a title to the second level select.
Comment #2
henrijs.seso commentedYou can replace
.fadeIn()with.show(), but that will not make all fields appear at the same time with other content on page.Comment #3
nicolas bouteille commentedComment #4
henrijs.seso commentedTaking in consideration that this is support request I'm going to go ahead and answer that it is impossible at this point to set such setting. Please open up two new "feature requests" about effect setting and labels, be ready to write some code and do not tell your client wants it (almost all Drupal features has this story in background). Good luck!
Comment #5
nicolas bouteille commentedHi,
I know that it is not possible to set such settings yet. I don't have time to wait for a new feature actually because I am supposed to deliver to the client next week.
My question was : is it possible to write some code in a special way such a given hook or template file or custom module so that my changes are not erased my the next SHS upgrade ? Or is the only solution to alter the js file and have to re-apply changes every-time ?
By the way, unfortunately changing fadeIn() by show() does not change the fact that the dropdown takes some time to appear which is really weird especially when the page loads and the dropdown is not there right away. (I tried the suggested solution to increase performance but could not make it work).
I think the user experience would be better if you were to use something like hook_form_alter to fill the dropdown when the page load. And then use an animated "loading..." image like the Ajax framework does to indicate that the second dropdown is being populated.
Comment #6
henrijs.seso commentedCurrently there is no alternatives to patching each version. As for time delay, it will also stay that way if js is not changed. It is because field widget is actually text field with term tid in it, js will get that tid and load siblings and all parents via ajax, build all select elements and fade them in and that is slow(er).
Comment #7
nicolas bouteille commentedOk thank you for your answers and for this very useful module too.
Comment #8
henrijs.seso commented:) I am not maintainer of this module, just a guy passing by. I am making some patches currently for "my client" (support entityrefetence and some other things) and digging inside module, so I know more or less how it is built and can help out maintainer and you keep issue queue cleaner.