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, "[email protected]" <[email protected]> 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 <[email protected]> > 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ş <[email protected]> > Reply-To: "[email protected]" <[email protected]> > Date: Tuesday, December 4, 2018 at 7:48 PM > To: "[email protected]" <[email protected]> > 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> uygulamasını > edinin > > > > On Wed, Dec 5, 2018 at 12:02 AM +0300, "Alex Harui" > <[email protected]<mailto:[email protected]>> 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ş <[email protected]> > Reply-To: "[email protected]" <[email protected]> > Date: Tuesday, December 4, 2018 at 12:56 PM > To: "[email protected]" <[email protected]> > 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:[email protected]] > > > 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:[email protected]] > > > 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ş > <[email protected]><mailto:[email protected]> > Reply-To: "[email protected]"<mailto:[email protected]> > <[email protected]><mailto:[email protected]> > Date: Tuesday, December 4, 2018 at 12:16 PM > To: "[email protected]"<mailto:[email protected]> > <[email protected]><mailto:[email protected]> > 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>); > > > > > > 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:[email protected]] > > > 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ş > <[email protected]><mailto:[email protected]> > Reply-To: "[email protected]"<mailto:[email protected]> > <[email protected]><mailto:[email protected]> > Date: Monday, December 3, 2018 at 12:10 PM > To: "[email protected]"<mailto:[email protected]> > <[email protected]><mailto:[email protected]> > Subject: Re: Work on Emulation > > Hi, > > Here is the next step: > > [cid:[email protected]] > > 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 -------------------------------------- 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. --------------------------------------
