Forum Discussion

hrothrock's avatar
hrothrock
Contributor
5 years ago

lazy loading - objects not yet in memory

I am working with an application that uses lazy loading. In one of my tests, I am accessing a row that is visible on a normal monitor. Today I am working on my small laptop and the row is not only no...
  • tristaanogre's avatar
    tristaanogre
    5 years ago

    FindChild by itself still won't overcome the lazy-load... that's why my PseudoCode had the PageDown call in a while loop.  I'd re-write your code as follows.

     

    function findRow()
{
var Row = 8;
var List = Aliases.pageDispatch.ListDispatchJobs;
var child = List.FindChild("Name", "Panel(" + (Row -1) + ")", 1, true);
while (!child.Exists) {
    List.Keys("[PageDown]");
    child = List.FindChild("Name", "Panel(" + (Row -1) + ")", 1, true);
}
Log.Message(child.contentText);
}

    This will check to see if the child exists.  If not, it sends a page down keystroke to scroll the list and then checks again.  When it does exist, it exits the while loop and the child object is now the desired object.

hrothrock's avatar
hrothrock
Contributor

tristaanogre 

I have been experimenting with the find child (which i have used successfully in other places) and it will not return a stub object. Maybe I am using it incorrectly. Here is my code:

 

function findRow()
{
var Row = 8;
var List = Aliases.pageDispatch.ListDispatchJobs;
var child = List.FindChild("Name", "Panel(" + (Row -1) + ")", 1, true);
Log.Message(child.contentText);
}

 

Row 7 does not exist yet as I haven't scrolled that far. If I run it without the Log.Message line, it passes with no details at all. With the Log.Message, I get this message: "The object does not exist. See details..." and the details say "You are trying to call the "contentText' method or property of an object that does not exist." It does not give me a stub object. I also tried entering a row number that does exist and it returned the correct content text.

tristaanogre's avatar
tristaanogre
Esteemed Contributor
5 years ago

FindChild by itself still won't overcome the lazy-load... that's why my PseudoCode had the PageDown call in a while loop.  I'd re-write your code as follows.

 

function findRow()
{
var Row = 8;
var List = Aliases.pageDispatch.ListDispatchJobs;
var child = List.FindChild("Name", "Panel(" + (Row -1) + ")", 1, true);
while (!child.Exists) {
    List.Keys("[PageDown]");
    child = List.FindChild("Name", "Panel(" + (Row -1) + ")", 1, true);
}
Log.Message(child.contentText);
}

This will check to see if the child exists.  If not, it sends a page down keystroke to scroll the list and then checks again.  When it does exist, it exits the while loop and the child object is now the desired object.

  • hrothrock's avatar
    hrothrock
    Contributor
    5 years ago

    I am going to accept the above as the solution because it would have gotten me there if the app was built the way I had assumed. However, I am going to have to re-think how I want to identify the child because it seems to not only be lazy loading but when it generates the content, it seems like it is adding some items to memory and removing others and dynamically generating parts of the identifiers I had planned to use. However, this solution gets me much further down the road. Thank you!!!

    • tristaanogre's avatar
      tristaanogre
      Esteemed Contributor
      5 years ago

      You can still adapt that solution.  But rather than picking a static row number, I'm assuming there's a specific text you're looking for.  If that's the case, you can do something like this.

      function findRow()
{
var List = Aliases.pageDispatch.ListDispatchJobs;
var child = List.FindChild("contentText", "*the text you're looking for*", 1, true);
while (!child.Exists) {
    List.Keys("[PageDown]");
    child = List.FindChild("contentText", "*the text you're looking for*", 1, true)
}
Log.Message(child.contentText);
}