Hi Harbs,
I'm not so convinced by the trace. Maybe something from your debugger to
have everything in debug. Does trace stripped out in release version of JS?
Thanks,
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://apache-flex-development.247
I don’t think there were any responses to this.
As it stands, the debugging functions will exist in release versions of swfs.
Harbs
> On Jul 16, 2017, at 12:07 PM, Harbs wrote:
>
> 1. The debugging functions should disappear in a release build of JS, but I’m
> not sure how to make the same th
Both Flash and JS engines automatically convert to RegExp. I had not realized
that at first.
It seems that the only difference between the Flash engine and JS engines is
what happens when constructing a RegExp object from invalid input. Flash
matches nothing, while JS throws an error.
By just
Well, as I said, I already have the compiler parsing the real debugger
statement in AS, and emitting the right JS. I just need to generate some
custom bytecode for SWF and then it will work everywhere.
- Josh
On Wed, Jul 19, 2017 at 7:17 PM, Alex Harui
wrote:
> I think we allow classes to be us
I think we allow classes to be used as a "statement" for dependency
management. CoreClasses.as, for example, has plenty of lines like:
import org.apache.flex.core.IUIBase; IUIBase;
HTH,
-Alex
On 7/19/17, 6:57 PM, "Josh Tynjala" wrote:
>Yes, I'm changing the compiler. The debugger statemen
Yes, I'm changing the compiler. The debugger statement is not a function.
It works like this:
debugger;
I think that flash.system.System.pause() will work too, and it's documented:
http://help.adobe.com/en_US/FlashPlatform/reference/actionscript/3/flash/system/System.html#pause()
- Josh
On Wed
Are you changing the compiler? I thought you could just add:
function debugger{};
to missing.js so it results in:
public class debugger {};
and
package flash.debugger {
native function enterDebugger():void;
}
to one of our swcs? Although I have to say I'm a bit uncomfortable about
ad
It looks like they just trace a warning instead of trying to convert to a
RegExp. Is that what we want to do? Or should we add code that converts
a string to regex?
Thoughts?
-Alex
On 7/19/17, 4:32 AM, "Harbs" wrote:
>I added the utility functions. I think they can be very simple.
>
>> On Jul
I haven't had time to dig into it, but IIRC, because we are using Google
Closure Events, stopImmediatePropagation will have no effect on what event
listeners Google will call. If the underlying DOM event does support
stopImmediatePropagation then it will stop other listeners on that DOM
object, bu
Yes. MDL does not seem to be a problem.
I just committed some more changes which makes my changes seem to work, but I
must be missing something. MouseEvents seem to work as well as BrowserEvents.
With KeyboardEvents, I’m getting mixed results. For some reason, I seem to be
losing focus more eas
Panel , close event not firing on JS side. swf side it is working fine.
This may be an issue.
On Wed, Jul 19, 2017 at 11:00 PM, Prashant Kumar
wrote:
> I am having a gird with one view column. On clicking view link , i want
> to open a popup to view information. I was unaware about actual
I am having a gird with one view column. On clicking view link , i want
to open a popup to view information. I was unaware about actual use of
findPopupHost so i pass this. I was thinking it will work same as
PopupManager works.
On Tue, Jul 18, 2017 at 8:02 PM, Alex Harui-2 [via Apache Flex D
Yishay, Harbs,
Are you using MDL in your project - does all events are working after
changes ? I mean click on controls like switch, new drop down list (you can
check it in MDLExample app)
Thanks,
Piotr
-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
View this message in context:
http://ap
I temporarily worked around our issues by using a try/catch in the code that
calls the handler. I’d like to hear what Alex and Peter have to say about this.
> On Jul 19, 2017, at 3:05 PM, yishayw wrote:
>
> I don't see what we would lose by making your changes and it would solve the
> issue we'
I don't see what we would lose by making your changes and it would solve the
issue we're facing, so I'd vote yes.
I'm not sure what the purpose of throwing the error was in the first place,
as EventDispatcher catches and ignores it anyway.
--
View this message in context:
http://apache-flex-de
I added the utility functions. I think they can be very simple.
> On Jul 19, 2017, at 9:30 AM, Alex Harui wrote:
>
> Unless we are absolutely sure that everybody will need the code generated
> by the compiler, having the compiler call a framework function makes it
> easier for an app developer t
I just created a branch with some of these ideas.
> On Jul 19, 2017, at 12:14 PM, Harbs wrote:
>
> This is kind of long, so please bear with me… ;-)
>
> I’m not sure what the “right” way to deal with my issue is, so I’m looking
> for input.
>
> Currently, FlexJS deals with stopImmediatePropag
This is kind of long, so please bear with me… ;-)
I’m not sure what the “right” way to deal with my issue is, so I’m looking for
input.
Currently, FlexJS deals with stopImmediatePropagation by throwing an error.
(See org.apache.flex.events.Event for details.)
I’m not sure I understand all the
Hi,
> Could you put this code on paste.apache.org or somewhere else?
Sure [1].
Justin
1. https://paste.apache.org/idv6
19 matches
Mail list logo
