I fixed the fact that an item used in nested states where the containing states
were different than a child’s states was being put in the output list more than
once, resulting in the duplicate keys issue.
The exception I saw in your code is that when you have a parent and child being
added to or removed from the same state, the current state handllng code
doesn’t like it because the parent may not have been created before the child
or vice versa, and we don’t want to increase complexity of the state handling
in these cases, since it doesn’t make sense to have:
<Group id=”MainApp” excludeFrom”loggedOut”>
<MenuBar excludeFrom=”loggedOut” />
</Group>
-Alex
From: Serkan Taş <serkan....@likyateknoloji.com>
Reply-To: "users@royale.apache.org" <users@royale.apache.org>
Date: Friday, December 7, 2018 at 11:32 AM
To: "users@royale.apache.org" <users@royale.apache.org>
Subject: Re: Work on Emulation
Hi Alex,
Thank you for the good news. I am going to try to build the libraries locally,
guess i can. And going to remove nested include/exclude declarations.
As far as I remember you fixed the include/exclude issue before, I am
surprised to see the same bug here. Is it something different ?
Serkan.
7.12.2018 22:23 tarihinde Alex Harui yazdı:
OK, The problem was that some addDependency calls were being incorrectly
computed and added to the output. I pushed a fix for that. If you don’t want
to wait for the nightly or can’t build from sources, you can get past this
problem by hand-editing the index.html. For each exception you should find the
entry in there twice. So for mx_internal, you’ll see two addDependency calls
and the second one will be missing dependencies. Remove that second one and
the exception will go away.
Once I got that exception to go away, there was one remaining exception due to
nested states again. The menubar above “messagePanel” is being
included/excluded from the same state as a containing parent, in this case
“mainApp”.
HTH,
-Alex
From: Serkan Taş
<serkan....@likyateknoloji.com><mailto:serkan....@likyateknoloji.com>
Reply-To: "users@royale.apache.org"<mailto:users@royale.apache.org>
<users@royale.apache.org><mailto:users@royale.apache.org>
Date: Thursday, December 6, 2018 at 11:31 AM
To: "users@royale.apache.org"<mailto:users@royale.apache.org>
<users@royale.apache.org><mailto:users@royale.apache.org>
Subject: Re: Work on Emulation
Sure here it is :
https://drive.google.com/open?id=1GXx7WgNJ2LPkkgwCZdmXefDykckk-TR7<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdrive.google.com%2Fopen%3Fid%3D1GXx7WgNJ2LPkkgwCZdmXefDykckk-TR7&data=02%7C01%7Caharui%40adobe.com%7C6e935abf06a24742028f08d65c7ac8e9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636798079774152981&sdata=2j0CnBQudrRP72tjm8w0TIWTfETKAhNNFlkr1EhCZsI%3D&reserved=0>
A bit big in size but I hope it is okay.
Thanks,
Serkan
6.12.2018 22:27 tarihinde Alex Harui yazdı:
Serkan,
Won’t Windows Explorer let you compress a folder into a regular zip file? All
of these other compression formats are not handled by default on my computers,
especially my Mac.
-Alex
From: Serkan Taş
<serkan....@likyateknoloji.com><mailto:serkan....@likyateknoloji.com>
Reply-To: "users@royale.apache.org"<mailto:users@royale.apache.org>
<users@royale.apache.org><mailto:users@royale.apache.org>
Date: Thursday, December 6, 2018 at 11:18 AM
To: "users@royale.apache.org"<mailto:users@royale.apache.org>
<users@royale.apache.org><mailto:users@royale.apache.org>
Subject: Re: Work on Emulation
Hi Alex,
Is seven zip okay for you ?
https://drive.google.com/open?id=1S3TkSkM9SiViU0nr7MRjbpCRxFkqRRET<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdrive.google.com%2Fopen%3Fid%3D1S3TkSkM9SiViU0nr7MRjbpCRxFkqRRET&data=02%7C01%7Caharui%40adobe.com%7C6e935abf06a24742028f08d65c7ac8e9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636798079774162991&sdata=0eCGuW6XqDr6SOAywyhdzfB7kvtBT9PDUJ7N7vE6txQ%3D&reserved=0>
If not tell me which program i may use.
Thanks,
Serkan
6.12.2018 22:13 tarihinde Alex Harui yazdı:
Hi Serkan,
The console only reports what you ask it to report. The debugger and elements
tree hold the data.
I will look at your test case later, but please re-post it by using Zip instead
of WinRAR. I’ve had trouble with RAR files.
Thanks,
-Alex
From: Serkan Taş
<serkan....@likyateknoloji.com><mailto:serkan....@likyateknoloji.com>
Reply-To: "users@royale.apache.org"<mailto:users@royale.apache.org>
<users@royale.apache.org><mailto:users@royale.apache.org>
Date: Thursday, December 6, 2018 at 11:09 AM
To: "users@royale.apache.org"<mailto:users@royale.apache.org>
<users@royale.apache.org><mailto:users@royale.apache.org>
Subject: Re: Work on Emulation
Hi Alex,
I do not understand why it is not helpful but do not want go that way, because
i know that you are spending so much time to help me :)
Some years ago i was working with javascript debugging kind of things but i
left and now trying to get used to.
Hope these are useful :
1. When i look at the web console of firefox developer edition, there are two
divisions. On the left side there are errors and warnings, on the right side
there are file names and Namespace.js is not there. I thought that these are
the list of the files loaded by browser. Am I wrong ?
2. When I debug the code;
Put break-point to the line : mx.core.mx_internal = new
Namespace("http://www.adobe.com/2006/flex/mx/internal";<http://www.adobe.com/2006/flex/mx/internal>);
And mouse-over the Namespace I see the message "Undefined"
After stepping over, thane get the message :
ReferenceError: Namespace is not defined[Learn More] mx_internal.js:17:1
· <anonymous>
file:///D:/dev/royale-emulation-works/github/bin/js-debug/mx/core/mx_internal.js:17
3. You asked me the check the "You can examine in the browser the global
variables looking for Namespace," But really i do not know how to check it,
sorry for that.
If you want to check it, I shared the folder here
:https://drive.google.com/open?id=1n1-4dqStXOCwoG10eWgQExJilYxovwCZ<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdrive.google.com%2Fopen%3Fid%3D1n1-4dqStXOCwoG10eWgQExJilYxovwCZ&data=02%7C01%7Caharui%40adobe.com%7C6e935abf06a24742028f08d65c7ac8e9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636798079774162991&sdata=bLBS8%2FhHwvXhn%2FHKV5QxgWW5NQx%2Bu%2FyWycIy2QVVr5E%3D&reserved=0>
Compressed with WinRar
Thanks,
Serkan
5.12.2018 09:31 tarihinde Alex Harui yazdı:
I saw the browser console as well, but neither are what I asked and do not
provide helpful data.
Please check the loaded scripts and the global variables.
-Alex
On 12/4/18, 10:14 PM,
"serkan....@likyateknoloji.com"<mailto:serkan....@likyateknoloji.com>
<serkan....@likyateknoloji.com><mailto:serkan....@likyateknoloji.com> wrote:
May be a problem with the mail, sorry for that but there are two
images in mail i sent to you. One is folder view for Namenode.js and
the other is browser console.
I am using firefox, and attaching the image again : image002.png
As i am at client for now, i am not able to send you the content of
the folder. I ll do it after work.
Thanks.
Serkan
Alinti Alex Harui <aha...@adobe.com><mailto:aha...@adobe.com>
> I see a screenshot of what looks like the file folder. We need to
> know what the Browser has done.
>
> What browser are you using? Zip up your bin/js-debug and post it
somewhere.
>
> -Alex
>
> From: Serkan Taş
<serkan....@likyateknoloji.com><mailto:serkan....@likyateknoloji.com>
> Reply-To: "users@royale.apache.org"<mailto:users@royale.apache.org>
<users@royale.apache.org><mailto:users@royale.apache.org>
> Date: Tuesday, December 4, 2018 at 7:48 PM
> To: "users@royale.apache.org"<mailto:users@royale.apache.org>
<users@royale.apache.org><mailto:users@royale.apache.org>
> Subject: Re: Work on Emulation
>
> Alex, can you see the screen shots?
> Android için
>
Outlook<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2Fghei36&data=02%7C01%7Caharui%40adobe.com%7Ceff0fbf780bd42c2fc7b08d65a78e3dc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636795872636276227&sdata=PB8x0W0MN04%2FXCGPsFZbWbkKySU6rbhZeBteLi1tY78%3D&reserved=0><https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Faka.ms%2Fghei36&data=02%7C01%7Caharui%40adobe.com%7C6e935abf06a24742028f08d65c7ac8e9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636798079774172996&sdata=L%2Frf%2FaBuqHYvwlTtohMyi7V2lxD4VBSdPC%2Fne%2FldeZE%3D&reserved=0>
uygulamasını
> edinin
>
>
>
> On Wed, Dec 5, 2018 at 12:02 AM +0300, "Alex Harui"
>
<aha...@adobe.com<mailto:aha...@adobe.com><mailto:aha...@adobe.com><mailto:aha...@adobe.com>>
wrote:
> I don’t know what you mean by “check image for loaded files”. I’m
> not sure what Image you refer to, plus, I already mentioned two ways
> to check.
>
>
> From: Serkan Taş
<serkan....@likyateknoloji.com><mailto:serkan....@likyateknoloji.com>
> Reply-To: "users@royale.apache.org"<mailto:users@royale.apache.org>
<users@royale.apache.org><mailto:users@royale.apache.org>
> Date: Tuesday, December 4, 2018 at 12:56 PM
> To: "users@royale.apache.org"<mailto:users@royale.apache.org>
<users@royale.apache.org><mailto:users@royale.apache.org>
> Subject: Re: Work on Emulation
>
> Hi Alex,
>
> Same approach also fixed the ImageContainer.as static initialization
error.
>
> The namespace error comes from main application and Namespace.js in
> root folder.
>
> [cid:part1.80584B16.3C988882@likyateknoloji.com]
>
>
> I guess the Namespace.js is not loaded if I check the right side of
> the image for loaded files. If this is the right way to check loaded
> files.
>
> [cid:part2.7D2F40D8.4A37C7C1@likyateknoloji.com]
>
>
> It is up for tonight. I am going to look forward tomorrow.
>
> Thanks,
> Serkan
> 4.12.2018 23:45 tarihinde Alex Harui yazdı:
> Hi Serkan,
>
> Is the mx_internal/Namespace problem coming from the main app or a
> module? Is there a Namespace.js in bin/js-debug? Is Namespace.js
> loaded at the time of the error? You can examine in the browser the
> global variables looking for Namespace, and also check the set of
> scripts loaded by the browser.
>
> Maybe the problem you are reporting with ArrayList and ModelLocator
> is the same that Yishay is reporting. Some static dependencies are
> not being handled correctly, but your workaround should be fine for
> now.
>
> -Alex
>
> From: Serkan Taş
>
<serkan....@likyateknoloji.com><mailto:serkan....@likyateknoloji.com><mailto:serkan....@likyateknoloji.com><mailto:serkan....@likyateknoloji.com>
> Reply-To:
"users@royale.apache.org"<mailto:users@royale.apache.org><mailto:users@royale.apache.org><mailto:users@royale.apache.org>
>
<users@royale.apache.org><mailto:users@royale.apache.org><mailto:users@royale.apache.org><mailto:users@royale.apache.org>
> Date: Tuesday, December 4, 2018 at 12:16 PM
> To:
"users@royale.apache.org"<mailto:users@royale.apache.org><mailto:users@royale.apache.org><mailto:users@royale.apache.org>
>
<users@royale.apache.org><mailto:users@royale.apache.org><mailto:users@royale.apache.org><mailto:users@royale.apache.org>
> Subject: Re: Work on Emulation
>
> Hi Alex,
>
> 4.12.2018 03:45 tarihinde Alex Harui yazdı:
>
>
>
> Serkan,
>
> Are you sure you are using the latest code and have deleted the
> bin/js-debug before building?
>
> I cleaned all folders and tried again.
>
>
>
>
> If so, what is in mx_internal.js? Mine has a section that looks
> like this, which should load Namespace (and Namespace.js should be
> in bin/js-debug)
>
> Content of mx_internal.js
>
> /**
> * Generated by Apache Royale Compiler from mx\core\mx_internal.as
> * mx.core.mx_internal
> *
> * @fileoverview
> *
> * @suppress {missingRequire|checkTypes|accessControls}
> */
>
> goog.provide('mx.core.mx_internal');
> /* Royale Dependency List: XML*/
> /* Royale Static Dependency List: Namespace*/
> goog.require('Namespace');
>
> mx.core.mx_internal = new
>
Namespace("http://www.adobe.com/2006/flex/mx/internal";<http://www.adobe.com/2006/flex/mx/internal><http://www.adobe.com/2006/flex/mx/internal><http://www.adobe.com/2006/flex/mx/internal>);
>
>
>
>
>
> What is the code in ToolTipContainer where it is throwing an error
> about ArrayList?
>
> TooltipContainer.js [L:35]:
>
>
com.likya.pinara.containers.ToolTipContainer.com_likya_pinara_containers_ToolTipContainer_toolTipList
= new
> mx.collections.ArrayList();
>
> TooltipContainer.as :
>
> package com.likya.pinara.containers
> {
> import mx.collections.ArrayList;
> import mx.resources.ResourceManager;
>
> public class ToolTipContainer {
>
> private static var toolTipList:ArrayList = new ArrayList();
>
>
> toolTipList.addItem(ResourceManager.getInstance().getString('messages',
> 'readyTooltip'))
>
> toolTipList.addItem(ResourceManager.getInstance().getString('messages',
> 'waitingTooltip'))
>
> toolTipList.addItem(ResourceManager.getInstance().getString('messages',
> 'workingTooltip'))
>
> toolTipList.addItem(ResourceManager.getInstance().getString('messages',
> 'successfulTooltip'))
>
> toolTipList.addItem(ResourceManager.getInstance().getString('messages',
> 'failedTooltip'))
>
> toolTipList.addItem(ResourceManager.getInstance().getString('messages',
> 'timeoutTooltip'))
>
> toolTipList.addItem(ResourceManager.getInstance().getString('messages',
> 'skippedTooltip'))
>
> toolTipList.addItem(ResourceManager.getInstance().getString('messages',
> 'stoppedTooltip'))
>
> toolTipList.addItem(ResourceManager.getInstance().getString('messages',
> 'pausedTooltip'))
>
> toolTipList.addItem(ResourceManager.getInstance().getString('messages',
> 'workingTooltip'))
>
> toolTipList.addItem(ResourceManager.getInstance().getString('messages',
> 'disabledTooltip'))
>
> public function ToolTipContainer() {}
>
> public static function getToolTip(data:Object):String {
>
> var statu:int = data.visualParams.statu;
>
> // Alert.show("Vparams : " + data.visualParams);
> // Alert.show("statu:" + statu + " image:" +
> imageList.getItemAt(statu));
>
> return toolTipList.getItemAt(statu) as String;
> }
>
> }
> }
>
> I thought that the initialization of the ArrayList the root cause of
> the problem and modified the code as below, ant the error has been
> fixed;
>
> package com.likya.pinara.containers
> {
> import mx.collections.ArrayList;
> import mx.resources.ResourceManager;
>
> public class ToolTipContainer {
>
> private static var toolTipList:ArrayList;
>
> public function ToolTipContainer() {}
>
> public static function getToolTip(data:Object):String {
>
> var statu:int = data.visualParams.statu;
>
> // Alert.show("Vparams : " + data.visualParams);
> // Alert.show("statu:" + statu + " image:" +
> imageList.getItemAt(statu));
>
> if(toolTipList == null || toolTipList.length == 0) {
> toolTipList = new ArrayList()
>
> toolTipList.addItem(ResourceManager.getInstance().getString('messages',
> 'readyTooltip'))
>
> toolTipList.addItem(ResourceManager.getInstance().getString('messages',
> 'waitingTooltip'))
>
> toolTipList.addItem(ResourceManager.getInstance().getString('messages',
> 'workingTooltip'))
>
> toolTipList.addItem(ResourceManager.getInstance().getString('messages',
> 'successfulTooltip'))
>
> toolTipList.addItem(ResourceManager.getInstance().getString('messages',
> 'failedTooltip'))
>
> toolTipList.addItem(ResourceManager.getInstance().getString('messages',
> 'timeoutTooltip'))
>
> toolTipList.addItem(ResourceManager.getInstance().getString('messages',
> 'skippedTooltip'))
>
> toolTipList.addItem(ResourceManager.getInstance().getString('messages',
> 'stoppedTooltip'))
>
> toolTipList.addItem(ResourceManager.getInstance().getString('messages',
> 'pausedTooltip'))
>
> toolTipList.addItem(ResourceManager.getInstance().getString('messages',
> 'workingTooltip'))
>
> toolTipList.addItem(ResourceManager.getInstance().getString('messages',
> 'disabledTooltip'))
> }
>
> return toolTipList.getItemAt(statu) as String;
> }
>
> }
>
>
>
>
>
> I cannot produce the problem with Spark Panel. Panel’s
> get_numElements should access the “get view” in UIBase and load a
> valid PanelView. You will have to debug in and find out why not.
> I am not getting error for now, may be related with old code and
> disappeared after cleaning js-debug folder.
>
> When i move forward than get some other errors:
>
> [cid:part1.7C3FE3E5.307DCB7B@likyateknoloji.com]
>
>
> I am going to apply the same approach to the ImageContainer as I did
> in ToolTipContainer and see if it is going to be fixed.
>
>
> Thanks,
> Serkan
>
>
>
>
>
> Thanks,
> -Alex
>
> goog.provide('mx.core.mx_internal');
> /* Royale Dependency List: XML*/
> /* Royale Static Dependency List: Namespace*/
> goog.require('Namespace');
>
>
>
>
> From: Serkan Taş
>
<serkan....@likyateknoloji.com><mailto:serkan....@likyateknoloji.com><mailto:serkan....@likyateknoloji.com><mailto:serkan....@likyateknoloji.com>
> Reply-To:
"users@royale.apache.org"<mailto:users@royale.apache.org><mailto:users@royale.apache.org><mailto:users@royale.apache.org>
>
<users@royale.apache.org><mailto:users@royale.apache.org><mailto:users@royale.apache.org><mailto:users@royale.apache.org>
> Date: Monday, December 3, 2018 at 12:10 PM
> To:
"users@royale.apache.org"<mailto:users@royale.apache.org><mailto:users@royale.apache.org><mailto:users@royale.apache.org>
>
<users@royale.apache.org><mailto:users@royale.apache.org><mailto:users@royale.apache.org><mailto:users@royale.apache.org>
> Subject: Re: Work on Emulation
>
> Hi,
>
> Here is the next step:
>
> [cid:part1.64C4E4AF.C1D7CDA2@likyateknoloji.com]
>
> Thanks,
> Serkan
--
Serkan Taş
Mobil : +90 532 250 07 71
Likya Bilgi Teknolojileri
ve İletişim Hiz. Ltd. Şti.
https://na01.safelinks.protection.outlook.com/?url=www.likyateknoloji.com&data=02%7C01%7Caharui%40adobe.com%7Ceff0fbf780bd42c2fc7b08d65a78e3dc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636795872636276227&sdata=gXzF2N4cPIFL5QpUElKNKWythiR5Yen9F3BVgLvyAWk%3D&reserved=0<https://na01.safelinks.protection.outlook.com/?url=www.likyateknoloji.com&data=02%7C01%7Caharui%40adobe.com%7C6e935abf06a24742028f08d65c7ac8e9%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636798079774183005&sdata=dYOoAvUJiAbFOnBEGoKTQp%2FTwXIhW63%2FSJV4cwc8W20%3D&reserved=0>
--------------------------------------
Bu elektronik posta ve onunla iletilen bütün dosyalar gizlidir. Sadece
yukarıda isimleri belirtilen kişiler arasında özel haberleşme amacını
taşımaktadır. Size yanlışlıkla ulaşmışsa bu elektonik postanın
içeriğini açıklamanız, kopyalamanız, yönlendirmeniz ve kullanmanız
kesinlikle yasaktır. Lütfen mesajı geri gönderiniz ve sisteminizden
siliniz. Likya Bilgi Teknolojileri ve İletişim Hiz. Ltd. Şti. bu
mesajın içeriği ile ilgili olarak hiç bir hukuksal sorumluluğu kabul
etmez.
This electronic mail and any files transmitted with it are intended
for the private use of the persons named above. If you received this
message in error, forwarding, copying or use of any of the information
is strictly prohibited. Please immediately notify the sender and
delete it from your system. Likya Bilgi Teknolojileri ve İletişim Hiz.
Ltd. Şti. does not accept legal responsibility for the contents of
this message.
--------------------------------------
