You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dear Developer,
jSignature calculates with it's container's size at initialization time.
In my case, dynamic content is prepared former, but showed at a later time with animation.
Because of the animation, the dynamic content is hidden until the animation begins.
So, there are "initializing" phase and "showing" phase.
Setting up the signature panel's parameters belongs to the initializing.
At initialization time, the signature panel's dimensions are 0 x 0, and therefore it doesn't work later.
I can call jSignature's onParentResized event, but it isn't public:
$("#"+pageName+"-signaturePad").jSignature('globalEvents').topics["jSignature.parentresized"][0]0;
Could you please make a public function for re-rendering the jSignature's canvas with keeping all the settings?
Maybe jSignature's initialization could wait for the container gets visible with MutationObserver.
Best Regards,
Gabor
The text was updated successfully, but these errors were encountered:
Dear Developer,
jSignature calculates with it's container's size at initialization time.
In my case, dynamic content is prepared former, but showed at a later time with animation.
Because of the animation, the dynamic content is hidden until the animation begins.
So, there are "initializing" phase and "showing" phase.
Setting up the signature panel's parameters belongs to the initializing.
At initialization time, the signature panel's dimensions are 0 x 0, and therefore it doesn't work later.
I can call jSignature's onParentResized event, but it isn't public:
$("#"+pageName+"-signaturePad").jSignature('globalEvents').topics["jSignature.parentresized"][0]0;
Could you please make a public function for re-rendering the jSignature's canvas with keeping all the settings?
Maybe jSignature's initialization could wait for the container gets visible with MutationObserver.
Best Regards,
Gabor
The text was updated successfully, but these errors were encountered: