Re: UIComponents set visible positioner.style.visibility = null not working wir IE11

[tranquiliste]

Thanks Harbs,

I don't want to use the nightly build for the project to avoid regression,
so I  was thinking to backport the 2 lines modification in the 0.9.7 and I
was wondering if/what I need to compile the patched 0.9.7?

Nicolas



-
Nicolas
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/

RE: UIComponents set visible positioner.style.visibility = null not working wir IE11

[Yishay Weiss]

Are you compiling from source? If so, it should be as easy as re-compiling 
after cherry-picking 9029464918b0d3dbb746343cd5bb337d77cd2a3c.

From: tranquiliste
Sent: Wednesday, July 8, 2020 1:09 PM
To: users@royale.apache.org
Subject: Re: UIComponents set visible positioner.style.visibility = null not 
working wir IE11

Thanks Harbs,

I don't want to use the nightly build for the project to avoid regression,
so I  was thinking to backport the 2 lines modification in the 0.9.7 and I
was wondering if/what I need to compile the patched 0.9.7?

Nicolas



-
Nicolas
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/

RE: UIComponents set visible positioner.style.visibility = null not working wir IE11

[tranquiliste]

Hello,

No I am not compiling from source, how should I do?

my current compiler options are (with visual studio code)
{
"compilerOptions": {
"targets": ["JSRoyale"],
"source-path": ["src"],
"source-map": true,
"output": "../ProjectBuilds",
"html-output-filename": "Project.html",
"library-path": [
"${royalelib}/js/libs/MXRoyaleJS.swc"
],
"js-library-path": [
"${royalelib}/js/libs/MXRoyaleJS.swc"
],
"remove-circulars": true
},
"additionalOptions":
"-keep-as3-metadata+=Inject,Dispatcher,EventHandler,PostConstruct,PreDestroy,ViewAdded,ViewRemoved,Bindable,Transient
-keep-code-with-metadata=Inject",
"mainClass": "Project",
"copySourcePathAssets": true
}

Thanks
Nicolas



-
Nicolas
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/

Re: UIComponents set visible positioner.style.visibility = null not working wir IE11

[Piotr Zarzycki]

Hi Nicolas,

You have two options to build framework.

1) Using ANT - instruction can be found here [1]
2) Using Apache Maven - I personally recommend to use that one, but that's
just a preference [2]. There is special parameter which allows you to
output Royale binaries which can be used in your IDE.

[1] https://github.com/apache/royale-asjs/blob/develop/README.md
[2]
https://github.com/apache/royale-asjs/wiki/Build-Apache-Royale-with-Maven

Thanks,
Piotr

śr., 8 lip 2020 o 13:53 tranquiliste  napisał(a):

> Hello,
>
> No I am not compiling from source, how should I do?
>
> my current compiler options are (with visual studio code)
> {
> "compilerOptions": {
> "targets": ["JSRoyale"],
> "source-path": ["src"],
> "source-map": true,
> "output": "../ProjectBuilds",
> "html-output-filename": "Project.html",
> "library-path": [
> "${royalelib}/js/libs/MXRoyaleJS.swc"
> ],
> "js-library-path": [
> "${royalelib}/js/libs/MXRoyaleJS.swc"
> ],
> "remove-circulars": true
> },
> "additionalOptions":
>
> "-keep-as3-metadata+=Inject,Dispatcher,EventHandler,PostConstruct,PreDestroy,ViewAdded,ViewRemoved,Bindable,Transient
> -keep-code-with-metadata=Inject",
> "mainClass": "Project",
> "copySourcePathAssets": true
> }
>
> Thanks
> Nicolas
>
>
>
> -
> Nicolas
> --
> Sent from: http://apache-royale-users.20374.n8.nabble.com/
>


-- 

Piotr Zarzycki

Patreon: *https://www.patreon.com/piotrzarzycki
*

Re: UIComponents set visible positioner.style.visibility = null not working wir IE11

[Alex Harui]

IIRC, standard Flex “monkey-patching” should also work.  Copy the one source 
file into the source-path with the correct folder structure.

-Alex

From: Piotr Zarzycki 
Reply-To: "users@royale.apache.org" 
Date: Wednesday, July 8, 2020 at 4:57 AM
To: "users@royale.apache.org" 
Subject: Re: UIComponents set visible positioner.style.visibility = null not 
working wir IE11

Hi Nicolas,

You have two options to build framework.

1) Using ANT - instruction can be found here [1]
2) Using Apache Maven - I personally recommend to use that one, but that's just 
a preference [2]. There is special parameter which allows you to output Royale 
binaries which can be used in your IDE.

[1] 
https://github.com/apache/royale-asjs/blob/develop/README.md
[2] 
https://github.com/apache/royale-asjs/wiki/Build-Apache-Royale-with-Maven

Thanks,
Piotr

śr., 8 lip 2020 o 13:53 tranquiliste 
mailto:nicolas.agut...@gmail.com>> napisał(a):
Hello,

No I am not compiling from source, how should I do?

my current compiler options are (with visual studio code)
{
"compilerOptions": {
"targets": ["JSRoyale"],
"source-path": ["src"],
"source-map": true,
"output": "../ProjectBuilds",
"html-output-filename": "Project.html",
"library-path": [
"${royalelib}/js/libs/MXRoyaleJS.swc"
],
"js-library-path": [
"${royalelib}/js/libs/MXRoyaleJS.swc"
],
"remove-circulars": true
},
"additionalOptions":
"-keep-as3-metadata+=Inject,Dispatcher,EventHandler,PostConstruct,PreDestroy,ViewAdded,ViewRemoved,Bindable,Transient
-keep-code-with-metadata=Inject",
"mainClass": "Project",
"copySourcePathAssets": true
}

Thanks
Nicolas



-
Nicolas
--
Sent from: 
http://apache-royale-users.20374.n8.nabble.com/


--

Piotr Zarzycki

Patreon: 
https://www.patreon.com/piotrzarzycki