Databases
StackOverflow2013
Postsdbo
POHTMLLoader: Navigate Back and Forward in Page History
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POHTMLLoader: Navigate Back and Forward in Page History
    primarykey
    data
    text
    <p>I never had problems navigating Back and Forward through page history of Htmlloader that was a child of the main Native Window stage. I just have to use: HtmlLoaderVariable.historyForward();</p> <p>But when i add HTMLLoader as a child to a new Native Window, it doesn't seem to work.</p> <p>Here is the code:</p> <pre><code>function createNewHtmlWindow(pageUrl:String):void{ //Everytime I click a button, this function creates a seperate Native Window each containing HtmlLoader Class to load a webpage var myhtml= new HTMLLoader(); myhtml.width = 1000; myhtml.height = 780; myhtml.addEventListener(Event.COMPLETE, myHtmlLoaded); var myHtmloptions = new NativeWindowInitOptions(); myHtmloptions.transparent = false; myHtmloptions.systemChrome = NativeWindowSystemChrome.STANDARD; myHtmloptions.type = NativeWindowType.NORMAL; var extHtmlWindow = new NativeWindow(myHtmloptions); extHtmlWindow.title="new title"; extHtmlWindow.width = 1015; extHtmlWindow.height = 800; extHtmlWindow.activate(); extHtmlWindow.stage.align = "TL"; extHtmlWindow.stage.scaleMode = "noScale"; extHtmlWindow.stage.addChild(myhtml); var backNativeWin=new BackButton(); backNativeWin.x=5; backNativeWin.y=500; backNativeWin.addEventListener(MouseEvent.CLICK, loadPrevHistory); extHtmlWindow.stage.addChild(backNativeWin); var nextNativeWin=new NextButton(); nextNativeWin.x=30; nextNativeWin.y=500; nextNativeWin.addEventListener(MouseEvent.CLICK, loadNextHistory); extHtmlWindow.stage.addChild(nextNativeWin); myhtml.load(new URLRequest(pageUrl)); } function myHtmlLoaded(e:Event):void { //Page loads successfully } function loadNextHistory(m:MouseEvent):void{ output.text="Next&gt;&gt;"+m.target.parent.getChildAt(0); //Next&gt;&gt;[object HTMLLoader] m.target.parent.getChildAt(0).historyForward(); // This line is not working } function loadPrevHistory(m:MouseEvent):void{ output.text="Prev&gt;&gt;"+m.target.parent.getChildAt(0); //Prev&gt;&gt;[object HTMLLoader] m.target.parent.getChildAt(0).historyBack(); // This line is not working } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USJerry-bliss
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. CONot sure if this is what is causing issues, but you should avoid ever using the `parent` property to run a command. You never want to traverse backwards up the display list (or any object tree in OOP languages), only forwards. The only time the `parent` property should ever be used is for checking if the parent exists or what the data type of the parent is. You should save references to the things you need as properties of an available object instead.
      singulars
      1. POHTMLLoader: Navigate Back and Forward in Page History
      1. USJosh Janusch
    2. COYou are right Josh. I got it working just by referencing the parent as a property, and then used getChildAt(0). Thank You
      singulars
      1. POHTMLLoader: Navigate Back and Forward in Page History
      1. USJerry-bliss
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload