Search Type: Posts; User: eirik.lorentsen
Search: Search took 0.02 seconds.
Yes. In the demo there is a button called "BR - reuse" demonstrating exactly how to do this.
In short you store the pointer to the notification when you create it. This can be done in advance as...
Pass the following parameter to the constructor and the notification will not go anywhere:
View the source from the demo page:
Great idea. I wouldn't mind at all!
If I understand it right, then close() is just an alias for hide() or destroy(), depending on what closeAction is set to. In previous versions I always destroyed the Notifications, but in the last...
Previous versions can be found here:
Just pick the license that suits you. Meaning you are completely free to use it in any commercial application under the MIT license.
That is correct. The new 2.1 version should be backwards compatible with the previous 2.0 version. Just replace the Notification.js file with the one in the link and the changes will take effect.
hpsam, dmurat, idonofrio:
I have sorted out the problem with destruction and reuse. The notifications now destroy their dom by default unless closeAction is set to 'hide' in which case the...
I'll have a look at this as soon as I can find some spare time ;)
Yes. Efattal has authored a 3.x Notification extension:
This was the inspiration for the 4.x version.
The wait is over! Version 2.0 is here!
The new features/improvements are as following:
Renamed some properties ending with "Delay" to the more correct: "Duration".
Moved the hiding animation...
I have been working on a new version with all the suggested improvments including center alignment. I'm expecting to have it ready pretty soon!
I tried with 'component[floating=true]' and it worked on windows but didn't catch tooltips. Which are used for error messages in forms that may reside inside a alwaysOnTop window. So I used...
Good point! That was also my original idea. But i wasn't sure how to format the ComponentQuery to match all floating panels.
I looked further into it and I think this would be...
I have created a alwaysOnTop controller that you can use to keep the notifications always on top.
Always On Top extension for Ext JS 4.x
I have created a 4.x controller adding alwaysOnTop feature to floating components.
NOTE: I changed the name of the extension to Ext.ux.util.AlwaysOnTop to...
20 Dec 2011 3:06 PM
The documentation (4.0.7) lists 'quicktip' as xtype for
to the right of the title
However in the sourcecode...
I'm sorry but I haven't applied the styling to any 3.x code.
But if you set the config of the window to:
and add a cls where you use the...
Nice suggestion adding center alignment. It shouldn't be too difficult to add it in a future version.
Meanwhile it should be possible to fake it relatively easy by overriding the paddingX...
Minor changes on how the component is destroyed.
I have created a new version 1.2 including your feature suggestion.
There are now two new config options: stickOnClick and stickWhileHover
They both default to true.
Thanx for reporting that bug! The Array.indexOf method that I was using is not universally implemented and failed in older IE versions. I replaced my array manipulations with the...
30 Aug 2011 7:47 AM
Since there has been no reply here for a while i'm taking the liberty to promote my port/rewrite of the efattal version:
It has some improvements making it similar to this one in...
I have ported / rewritten a 4.x version of this extension that can be found here:
I placed it in the Ext.ux.window.Notification namespace.
Results 1 to 25 of 27