Menu
▾
▴
dynapi-dev — List related to the current DynAPI Core development
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(75) |
Nov
(252) |
Dec
(418) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(659) |
Feb
(1039) |
Mar
(870) |
Apr
(235) |
May
(329) |
Jun
(251) |
Jul
(123) |
Aug
(119) |
Sep
(67) |
Oct
(194) |
Nov
(535) |
Dec
(133) |
| 2002 |
Jan
(122) |
Feb
(24) |
Mar
(29) |
Apr
(28) |
May
(16) |
Jun
(20) |
Jul
(11) |
Aug
(12) |
Sep
(13) |
Oct
(14) |
Nov
(23) |
Dec
(19) |
| 2003 |
Jan
(28) |
Feb
(170) |
Mar
(288) |
Apr
(211) |
May
(126) |
Jun
(166) |
Jul
(131) |
Aug
(102) |
Sep
(211) |
Oct
(301) |
Nov
(22) |
Dec
(6) |
| 2004 |
Jan
(14) |
Feb
(16) |
Mar
(7) |
Apr
|
May
(8) |
Jun
(25) |
Jul
(21) |
Aug
(2) |
Sep
(7) |
Oct
|
Nov
(2) |
Dec
(1) |
| 2005 |
Jan
(4) |
Feb
(2) |
Mar
(14) |
Apr
(24) |
May
(3) |
Jun
(7) |
Jul
(30) |
Aug
(5) |
Sep
(1) |
Oct
(3) |
Nov
|
Dec
(1) |
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(4) |
Oct
|
Nov
|
Dec
|
|
From: Doug M. <do...@cr...> - 2001-02-25 21:14:18
|
How about a compramise? A SlimDynLayer? it would have addchild, moveto, setsize and such.. but would not have sethtml,setcontent,getcontentwidth.. ect.. Just a super-basic object that can be used for 'lightweight' widgets ----- Original Message ----- From: "Pascal Bestebroer" <pa...@dy...> To: <dyn...@li...> Sent: Sunday, February 25, 2001 4:40 AM Subject: RE: [Dynapi-Dev] a few hours for only 2 lines of code.. damn! > > DynLayer IS the root component (that's what I've been trying to say) > Every widget needs the graphical functionality of a DynLayer, that's why it > IS the base object. > > Ofcourse TComponent is Delphi only, because Windows internally probably > doesn't have anything like it.. just graphics functions to draw canvas's. > But that's what we're doing here as well, DynLayer is the canvas object to > do all "graphical" interface tricks (this is DHTML, not windows, so mostly > used for visual development of websites) > > If you want a widget without any graphicall functionality then don't base if > on the DynLayer (never seen one, but it might happen). > > But as it is now, all widgets will always function the same they always > have: moveTo, setSize, setHTML, etc,etc,etc > This makes creating widgets that interact with each other alot easier > because you don't have to check for these methods to be available, they are > simply available.. so take a toolbar widget, you can add ANY other widget on > it, without having to prepare them or checking there class type. > > If you want your widgets using another model, go ahead but most (not all > though, but majority) people involved agreed that this was the way to do > widget inheriting: it's simple, short, and standard Javascript inheriting. > And I for one will stick to this way of widgets.. use your own model if you > like, just make sure there fully compatible. > > Pascal Bestebroer > pa...@dy... > http://www.dynamic-core.net > > > No, > > Delphi TComponent (been reading about this because of the Kylix) > > is a basic > > component that wraps the calls to the API. > > > > I don't care if we make a TComponent or TWidget but I just perfer > > this over > > using the DynLayer itself. > > > > 8an > > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-dev --- Outgoing mail is certified Virus Free by AVG Free Edition Download at: http://www.grisoft.com/html/us_index.cfm Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.231 / Virus Database: 112 - Release Date: 2/12/01 |
|
From: Doug M. <do...@cr...> - 2001-02-25 21:07:49
|
um, that would make two function calls instead of one..
With an interpreted language that can add up over several objects to
noticeably slow down the whole application.
----- Original Message -----
From: "Eytan Heidingsfeld" <ey...@tr...>
To: <dyn...@li...>
Sent: Sunday, February 25, 2001 2:24 AM
Subject: Re: [Dynapi-Dev] a few hours for only 2 lines of code.. damn!
> A wrapper function would be added to myWidget that would look like this:
> myWidget.prototype.moveTo = function(x,y){
> this.dynlayer.moveto(x,y);
> }
>
> 8an
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
---
Outgoing mail is certified Virus Free by AVG Free Edition
Download at: http://www.grisoft.com/html/us_index.cfm
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.231 / Virus Database: 112 - Release Date: 2/12/01
|
|
From: Doug M. <do...@cr...> - 2001-02-25 21:04:34
|
I most whole heartedly agree. The inheriting model makes so much of what I do possible. Withou one you loose the most integral part of the API. (IMHO of course) Dogu ----- Original Message ----- From: "Robert Rainwater" <rra...@ya...> To: "DynAPI Development List" <dyn...@li...> Sent: Sunday, February 25, 2001 1:08 AM Subject: Re[2]: [Dynapi-Dev] a few hours for only 2 lines of code.. damn! > > As much as I liked DynAPI 1, I don't want to go back to those days :) > > I think the widget model as it is now, is much more extensible than by > not using any type of inheriting. > > -- > // Robert Rainwater > > On 2/25/2001, 3:48:41 AM EST, Pascal wrote about "[Dynapi-Dev] a few hours for only 2 lines of code.. damn!": > > > man, now your gonna get it :) > > > leave the inheriting model alone! > > > serious though, currently widgets really inherit from the dynlayer, so that > > all dynlayer methods are available without any extra code (or memory) > > > if you make it a property of the widget, all these things are gone and you > > would need to call the dynlayer property to access dynlayer functionality > > (sizing,moveto) which should be simple widget methods. > > > I think there has been already ALOT of discussion about this (see archives > > :) and I for one am against any widget model changes (always have been, > > always will :) > > > > Pascal Bestebroer > > pa...@dy... > > http://www.dynamic-core.net > > >> -----Oorspronkelijk bericht----- > >> Van: dyn...@li... > >> [mailto:dyn...@li...]Namens Eytan Heidingsfeld > >> Verzonden: zaterdag 24 februari 2001 23:02 > >> Aan: dyn...@li... > >> Onderwerp: RE: [Dynapi-Dev] a few hours for only 2 lines of code.. damn! > >> > >> > >> The only thing I still want to change is the way that all widgets inherit > >> from DynLayer. Why don't we just make them have a dynlayer object > >> then it is > >> easier to free mem. (Taking care of DynLayer is a hassle but the object > >> isn't). > >> 8an > >> > >> > >> _______________________________________________ > >> Dynapi-Dev mailing list > >> Dyn...@li... > >> http://lists.sourceforge.net/lists/listinfo/dynapi-dev > >> > > > > _______________________________________________ > > Dynapi-Dev mailing list > > Dyn...@li... > > http://lists.sourceforge.net/lists/listinfo/dynapi-dev > > > ---------------------- > DynAPI Snapshots: http://dynapi.sourceforge.net/snapshot/ > DynAPI Homepage: http://dynapi.sourceforge.net/ > > > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-dev --- Outgoing mail is certified Virus Free by AVG Free Edition Download at: http://www.grisoft.com/html/us_index.cfm Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.231 / Virus Database: 112 - Release Date: 2/12/01 |
|
From: Henrik V. <hv...@ya...> - 2001-02-25 20:18:20
|
Heh, I was just about to post this as something similar was suggested = from others. Well, I guess it might add to the current turns as-is... --- I think that there's at least one occation when its useful of using an = object other than simply the dynlayer OR dyndocument - managers. With = managers I mean a toplevel object that holds value for multiple = instances of a certain widget (or other object?). Most could be included = with the widget they handle, but there's a couple of standalone managers = I would like to see.=20 * a window manager; I know Jordi might have something in the works here = (right?) * a focus manager; mainly to make alternative key navigation possible * a keymode manager; to toggle between control and normal(write) mode - = since modifier keys doesn't capture well together with char keys, but = works induvidually * a formmanager; for use and interface with servertasks as well as = clientside methods towards files (and databases?) I'm to code them myself, if nobody else will, it's just that I'm such a = messy a scripter that it takes me forever to finish off something :( Henrik V=E5glin [ hv...@ya... ] _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |
|
From: Robert R. <rra...@ya...> - 2001-02-25 20:08:56
|
The only JIT (Just-in-time) compiler I've ever heard of was for Java. But, I guess it MS could have one for JScript, but I've never heard of it. -- // Robert Rainwater On 2/25/2001, 2:57:17 PM EST, Erik wrote about "[Dynapi-Dev] JIT JavaScript (was My JS Optimization Site)": > What made you think that MS has a JIT for JScript? Personally I thought this > was one of the good news about .Net and JScript.Net. (Getting the same > performance as from all other languages.) > IE3+ has been using MS JVM which uses JIT but this does not mean that > JScript benefits from this? > Any proof / hints really apreciated. Same goes for Netscape Navigator 4 and > Mozilla 5. > Erik Arvidsson - WebFX.nu > er...@ea... > ----- Original Message ----- > From: "Raides J. Rodríguez Domínguez" <ra...@te...> >> Well. It's not exactly a better loop optimization, but the fact that IE >> has, by default, JIT optimization turned on. JIT stands for "Just In >> Time" compilation, which means that code is precompiled the first time >> it's executed and then just the compiled version is executed. After the >> first pass, no more JavaScript code is executed in those loops. Hence >> the speed-up. Of course, loop optimization is done in the JIT phase. > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-dev ---------------------- DynAPI Snapshots: http://dynapi.sourceforge.net/snapshot/ DynAPI Homepage: http://dynapi.sourceforge.net/ |
|
From: Erik A. <er...@ea...> - 2001-02-25 20:06:50
|
What made you think that MS has a JIT for JScript? Personally I thought this was one of the good news about .Net and JScript.Net. (Getting the same performance as from all other languages.) IE3+ has been using MS JVM which uses JIT but this does not mean that JScript benefits from this? Any proof / hints really apreciated. Same goes for Netscape Navigator 4 and Mozilla 5. Erik Arvidsson - WebFX.nu er...@ea... ----- Original Message ----- From: "Raides J. Rodríguez Domínguez" <ra...@te...> > Well. It's not exactly a better loop optimization, but the fact that IE > has, by default, JIT optimization turned on. JIT stands for "Just In > Time" compilation, which means that code is precompiled the first time > it's executed and then just the compiled version is executed. After the > first pass, no more JavaScript code is executed in those loops. Hence > the speed-up. Of course, loop optimization is done in the JIT phase. |
|
From: Eytan H. <ey...@tr...> - 2001-02-25 19:38:02
|
I'm trying to write a widget your way and am getting elm.style is undefined does anyone know why this would happen or do I have to track it? 8an |
|
From: nobody <no...@so...> - 2001-02-25 13:54:22
|
Artifact #223612, was updated on 2000-11-27 10:14 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=105757&aid=223612&group_id=5757 Category: None Group: None Status: Open Priority: 5 Submitted By: Joshua Hancik Assigned to: Nobody/Anonymous Summary: No mouseEvents in Mac IE5 in layers w/ images Initial Comment: Using the example dynapi.api.mouseevents.htm try adding an image to myLayer using the .setHTML command; it will break in Mac IE5. All of the mouseEvents still work in mac nav 4.x, but none of them work in IE5 and there are no fatal scripting errors generated or reported. I tested using just text in the .setHTML command and the problem disappeared - definately an image-related situation. Here is the line I added: myLayer.setHTML('<img src="images/gray_1.gif" width="250" height="144" border="0">') ---------------------------------------------------------------------- Comment By: Pascal Bestebroer Date: 2001-02-25 05:56 Message: Logged In: YES user_id=38844 see if it is fixed in latest CVS code ---------------------------------------------------------------------- Comment By: Pascal Bestebroer Date: 2001-01-12 11:23 Message: Problem might be because of the event code and image tags. This should be fixed once Jordi wins his war with the event code. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous Date: 2000-12-08 09:40 Message: I noticed that this bug also occurs when an image is added to any layer. It causes all mouse events to disappear for everything. ---------------------------------------------------------------------- Comment By: Nobody/Anonymous Date: 2000-12-08 09:38 Message: Is someone working on this bug? ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=105757&aid=223612&group_id=5757 |
|
From: Eytan H. <ey...@tr...> - 2001-02-25 13:47:54
|
Are your dynform for forms as in vb delphi forms (windows) or as in HTML forms? Cause I was also going to devlop a vb delphi one. I'd love to see urs. 8an |
|
From: Michael P. <mp...@po...> - 2001-02-25 13:44:59
|
this can be done again by just extending an Object. it is actually something i'm thinking of looking into for use with my dynform objects. Eytan Heidingsfeld wrote: > Ok. > Now to another discussion that has to do with the previous one. > What about creating an Application object. > You don't have to use it. It will be optional but will take care of stuff > like focus. > 8an > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-dev -- Michael Pemberton mp...@ph... ICQ: 12107010 |
|
From: Eytan H. <ey...@tr...> - 2001-02-25 13:36:14
|
Ok. Now to another discussion that has to do with the previous one. What about creating an Application object. You don't have to use it. It will be optional but will take care of stuff like focus. 8an |
|
From: Michael P. <mp...@po...> - 2001-02-25 13:28:34
|
I'm sorry if I'm late on the topic but it sux being 12 hours behind on all of these discussions. The API IS standalone. By itself it has NO visual components. If you want a root object on which to base your widgets, use the base JS object Object. This is what the DynLayer istelf in inhereting from.. The reason that almost all of the widgets inheret from DynLayer is because they are just that, VISUAL. If you want to create a widget that has NO functionality and no visual aspect, just use Object and write your own methods for it. Eytan Heidingsfeld wrote: > Ok. > You know what. > I can see this. > U win. (About the DynLayer not being a property) > > k? > 8an > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-dev -- Michael Pemberton mp...@ph... ICQ: 12107010 |
|
From: Michael P. <mp...@po...> - 2001-02-25 13:16:15
|
I've combined the different methods of stopping IE from displaying
context menus and selecting text into the following lines of code. They
should be placed just before the "return evt.browserReturn;" line.
if (is.ie5) {
if (evt.type=='mouseup' && evt.button==3)
dyndoc.doc.oncontextmenu=(evt.browserReturn) ? null : function() {return
false};
else if (evt.type=='mousedown')
dyndoc.doc.body.onselectstart=(evt.browserReturn) ? null : function()
{return false};
};
This means that there is now no need to repeat the code in all the
different widgets. Just cancel the browser event and the above code
will do the rest.
--
Michael Pemberton
mp...@ph...
ICQ: 12107010
|
|
From: Eytan H. <ey...@tr...> - 2001-02-25 13:06:54
|
Not having much luck with removeChild in NN6 and NN4 seems like a lossed cause. Even if I browse non DHTML pages it = leaks! 8an |
|
From: Eytan H. <ey...@tr...> - 2001-02-25 12:54:08
|
Ok. You know what. I can see this. U win. (About the DynLayer not being a property) k? 8an |
|
From: Pascal B. <pa...@dy...> - 2001-02-25 12:42:42
|
DynLayer IS the root component (that's what I've been trying to say) Every widget needs the graphical functionality of a DynLayer, that's why it IS the base object. Ofcourse TComponent is Delphi only, because Windows internally probably doesn't have anything like it.. just graphics functions to draw canvas's. But that's what we're doing here as well, DynLayer is the canvas object to do all "graphical" interface tricks (this is DHTML, not windows, so mostly used for visual development of websites) If you want a widget without any graphicall functionality then don't base if on the DynLayer (never seen one, but it might happen). But as it is now, all widgets will always function the same they always have: moveTo, setSize, setHTML, etc,etc,etc This makes creating widgets that interact with each other alot easier because you don't have to check for these methods to be available, they are simply available.. so take a toolbar widget, you can add ANY other widget on it, without having to prepare them or checking there class type. If you want your widgets using another model, go ahead but most (not all though, but majority) people involved agreed that this was the way to do widget inheriting: it's simple, short, and standard Javascript inheriting. And I for one will stick to this way of widgets.. use your own model if you like, just make sure there fully compatible. Pascal Bestebroer pa...@dy... http://www.dynamic-core.net > No, > Delphi TComponent (been reading about this because of the Kylix) > is a basic > component that wraps the calls to the API. > > I don't care if we make a TComponent or TWidget but I just perfer > this over > using the DynLayer itself. > > 8an |
|
From: Eytan H. <ey...@tr...> - 2001-02-25 12:18:51
|
No, Delphi TComponent (been reading about this because of the Kylix) is a basic component that wraps the calls to the API. I don't care if we make a TComponent or TWidget but I just perfer this over using the DynLayer itself. 8an |
|
From: Pascal B. <pa...@dy...> - 2001-02-25 12:11:35
|
> * Correct programming > Just what it sounds like. Imagine in windows all components would inherit > from canvas look at delphi : TComponent (that's our DynLayer) the base object of all components/widgets. > * Eaisier to write widgets. > For instance a pop up menu (what a cool idea ;-) because you don't know > where on the page you are and you might want the pop up menu to show up to > the left of the cursor or right or above or below you could put > that code in > popup.prototype.moveTo You lost me there.. can't we do that now with our current widgets?.. I always thought that was the beauty of the current model! Pascal Bestebroer pa...@dy... http://www.dynamic-core.net |
|
From: Eytan H. <ey...@tr...> - 2001-02-25 12:01:58
|
The problem is actualy two: * Correct programming Just what it sounds like. Imagine in windows all components would inherit from canvas * Eaisier to write widgets. For instance a pop up menu (what a cool idea ;-) because you don't know where on the page you are and you might want the pop up menu to show up to the left of the cursor or right or above or below you could put that code in popup.prototype.moveTo 8an |
|
From: Eytan H. <ey...@tr...> - 2001-02-25 11:20:52
|
And even greater news from the front 15k divs bump the mem to 20MB freeing brings us back to 9MB Yippy 8an |
|
From: Pascal B. <pa...@dy...> - 2001-02-25 10:57:48
|
over head of those bytes IS a problem.. a webapplication or very enhanced website would have ALOT of extra code going on, so all files would require much more. I dont see what the big improvement would be.. you still have a DynLayer to deal with. The main problem is that your doing alot of workaround methods to call all dynlayer methods. Widgets are now completely the same as dynlayers only with added functionality. That's the beauty of the current model. I just can't believe that any deletion code we eventually get working 100% can't be used in the current widget model (on which MANY widgets are already based). Pascal Bestebroer pa...@dy... http://www.dynamic-core.net > -----Oorspronkelijk bericht----- > Van: dyn...@li... > [mailto:dyn...@li...]Namens Eytan Heidingsfeld > Verzonden: zondag 25 februari 2001 11:47 > Aan: dyn...@li... > Onderwerp: Re: [Dynapi-Dev] a few hours for only 2 lines of code.. damn! > > > Give me a break! > Not meaning to sound rude: the over head of those bytes is the > least of our > problems and anyway since they are part of an object (not element) there > isn't even a leak! > 8an > > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-dev > |
|
From: Eytan H. <ey...@tr...> - 2001-02-25 10:46:19
|
Give me a break! Not meaning to sound rude: the over head of those bytes is the least of our problems and anyway since they are part of an object (not element) there isn't even a leak! 8an |
|
From: Pascal B. <pa...@dy...> - 2001-02-25 10:44:37
|
not sure how we can maintain it.. currently we have one release version, and one in CVS which is just the working code. No real versions numbers (just dates) are added.. having two versions is alot to maintain (I know :) but if you can come up with a good idea, attach it to a rock and throw it. Pascal Bestebroer pa...@dy... http://www.dynamic-core.net > -----Oorspronkelijk bericht----- > Van: dyn...@li... > [mailto:dyn...@li...]Namens Raymond Smith > Verzonden: zondag 25 februari 2001 2:14 > Aan: dyn...@li... > Onderwerp: [Dynapi-Dev] nameology > > > Since DynAPI3 stuck the fear of God into some individuals unnessarily, how > about adopting the naming syntax used by Linux. > > 1) Stable releases are "even" numbered. 2.0, 2.2, 2.4, etc... > 2) Working releases are "odd" numbered. 2.1, 2.3, 2.5, etc... > > Updates can happen to both, development can be concurrent. Odd's are more > experimental in nature, and not meant for "public consumption". > And this is > pretty easy to understand and add to the DynAPI F.A.Q. so new users > understand. > > Thoughts? > > Ray |
|
From: Pascal B. <pa...@dy...> - 2001-02-25 10:42:16
|
k, fixed it Pascal Bestebroer pa...@dy... http://www.dynamic-core.net > -----Oorspronkelijk bericht----- > Van: dyn...@li... > [mailto:dyn...@li...]Namens Pascal Bestebroer > Verzonden: zondag 25 februari 2001 11:21 > Aan: dyn...@li... > Onderwerp: RE: Re[2]: [Dynapi-Dev] [ dynapi-Bugs-404007 ] Events in > Images (IE 5.5) > > > uhm.. just in case: sorry :) > > Not sure if I broke anything, but that's why people should now > test the CVS > code as much as possible > I did alot of if statement changes, and other optimisations so > these might > have caused problems. > > Pascal Bestebroer > pa...@dy... > http://www.dynamic-core.net > > > -----Oorspronkelijk bericht----- > > Van: dyn...@li... > > [mailto:dyn...@li...]Namens Robert Rainwater > > Verzonden: zondag 25 februari 2001 10:28 > > Aan: DynAPI Development List > > Onderwerp: Re[2]: [Dynapi-Dev] [ dynapi-Bugs-404007 ] Events in Images > > (IE 5.5) > > > > > > > > Try any of the button examples or the scrollpane example. No events > > are fired when directly over an image. I'm using the latest code from > > CVS. > > > > I thought this had been fixed before? > > > > -- > > // Robert Rainwater > > > > On 2/24/2001, 11:37:55 PM EST, Doug wrote about "[Dynapi-Dev] > > > dynapi-Bugs-404007 ] Events in Images (IE 5.5)": > > > > > I've just updated my JS and found no such problem. > > > Win98 > > > IE 5.5 > > > ----- Original Message ----- > > > From: "nobody" <no...@so...> > > > To: <no...@so...> > > > Sent: Saturday, February 24, 2001 4:07 PM > > > Subject: [Dynapi-Dev] [ dynapi-Bugs-404007 ] Events in Images (IE 5.5) > > > > > > >> Artifact #404007, was updated on 2001-02-24 16:07 > > >> You can respond by visiting: > > >> > > > > http://sourceforge.net/tracker/?func=detail&atid=105757&aid=404007 > &group_id= > > 5757 > >> > >> Category: Core API > >> Group: None > >> Status: Open > >> Priority: 6 > >> Submitted By: Robert Rainwater > >> Assigned to: Nobody/Anonymous > >> Summary: Events in Images (IE 5.5) > >> > >> Initial Comment: > >> Using the dynapi_2001_02_24 snapshot, events in layers > >> in IE 5.5 do not appear to be fired. > >> > >> For example, in the dynapi.gui.button.html example, > >> the onmousedown events fail to fire when doing a > >> mousedown on the image part of a button. > >> > >> ---------------------------------------------------------------------- > >> > >> You can respond by visiting: > >> > > > http://sourceforge.net/tracker/?func=detail&atid=105757&aid=404007 &group_id= > 5757 >> >> _______________________________________________ >> Dynapi-Dev mailing list >> Dyn...@li... >> http://lists.sourceforge.net/lists/listinfo/dynapi-dev > --- > Outgoing mail is certified Virus Free by AVG Free Edition > Download at: http://www.grisoft.com/html/us_index.cfm > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.231 / Virus Database: 112 - Release Date: 2/12/01 > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-dev ---------------------- DynAPI Snapshots: http://dynapi.sourceforge.net/snapshot/ DynAPI Homepage: http://dynapi.sourceforge.net/ _______________________________________________ Dynapi-Dev mailing list Dyn...@li... http://lists.sourceforge.net/lists/listinfo/dynapi-dev _______________________________________________ Dynapi-Dev mailing list Dyn...@li... http://lists.sourceforge.net/lists/listinfo/dynapi-dev |
|
From: nobody <no...@so...> - 2001-02-25 10:41:08
|
Artifact #404007, was updated on 2001-02-24 16:07 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=105757&aid=404007&group_id=5757 Category: Core API Group: None Status: Closed Priority: 6 Submitted By: Robert Rainwater Assigned to: Pascal Bestebroer Summary: Events in Images (IE 5.5) Initial Comment: Using the dynapi_2001_02_24 snapshot, events in layers in IE 5.5 do not appear to be fired. For example, in the dynapi.gui.button.html example, the onmousedown events fail to fire when doing a mousedown on the image part of a button. ---------------------------------------------------------------------- Comment By: Pascal Bestebroer Date: 2001-02-25 02:42 Message: Logged In: YES user_id=38844 uhm, and closed it. ---------------------------------------------------------------------- Comment By: Pascal Bestebroer Date: 2001-02-25 02:42 Message: Logged In: YES user_id=38844 fixed the problem ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=105757&aid=404007&group_id=5757 |
175 messages has been excluded from this view by a project administrator.
