SPONSORS:






User Tag List

Page 1 of 2 12 LastLast
Results 1 to 10 of 12
  1. #1
    Junior Member
    Join Date
    Jul 2001
    Location
    Roseville, CA USA
    Posts
    20
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Garbage printed using SetText ()

    Using SetText () to type data into a TextField types garbage (extra, meaningless characters) at the end of the field.

    The data that is being passed in has not been corrupted. In the trace, it is as expected. However, in the GUI app, the text field holds improper data.

    Here is an output from the trace:

    ToolProperties.SetActive ()
    ToolProperties.Tabs.Select ("General")
    ToolProperties.General.DisplayName.AgentSetText ("WIN-Verify Node Info")
    // HERE IN THE TEXT FIELD, IT IS DISPLAYED AS WIN-Verify Node Infoo (NOTE: EXTRA o)

    tool name =WIN-Verify Node Info

    ToolProperties.General.Description.AgentSetText ("Parses a file")
    // HERE IN THE TEXT FIELD, IT IS DISPLAYED AS
    Parses a File NodeI

    desc = Parses a file

    This is on Windows XP (Windows Classic Display), running Silk 5.5 SP1. The machine has been rebooted and the Silk agent has been restarted.
    This has occurred intermittently on W2K Server, but on XP it is consistently happening.

    Is this a known problem?

    Any work arounds?

    Thank you.

    ------------------

  2. #2
    Senior Member
    Join Date
    Jul 1999
    Location
    Burlingame CA 94010
    Posts
    502
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Garbage printed using SetText ()

    When does the extra text appear?

    Post the code you're using to do the SetText ()

    Try doing a ClearText () before the SetText ()


  3. #3
    Junior Member
    Join Date
    Jul 2001
    Location
    Roseville, CA USA
    Posts
    20
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Garbage printed using SetText ()

    John,

    We tried the ClearText () function before using SetText () and it seems as if the problem has disappeared.

    Thank you,

    Elizabeth

    ------------------

  4. #4
    Senior Member
    Join Date
    Feb 2000
    Posts
    1,497
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Garbage printed using SetText ()

    I wouldn't necessarily call it fixed quite yet. Try a Print() of the field before you clear it to see if the junk characters appear. If they do, you might ask the developers why they put the junk there. A field that isn't primed with useful information or cleared when the dialog is opened can make for some interesting failures later.

    John


    ------------------

  5. #5
    Senior Member
    Join Date
    Jul 1999
    Location
    Bellingham, WA USA
    Posts
    1,323
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Garbage printed using SetText ()

    ...especially if the "garbage characters" are hidden characters.

    ------------------

  6. #6
    Super Member
    Join Date
    Jul 1999
    Location
    Rancho Santa Margarita, CA
    Posts
    1,439
    Post Thanks / Like
    Mentioned
    4 Post(s)
    Tagged
    1 Thread(s)

    Re: Garbage printed using SetText ()

    Elizabeth,

    Just wondering if you get the same 'garbage' using "TypeKeys ()" instead of "SetText ()"!?


    ------------------

  7. #7
    Junior Member
    Join Date
    Jun 2002
    Posts
    4
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Garbage printed using SetText ()

    We have seen this in two situations: running silk test on pc that are not very powerfull and running silk on forms/windows that can' be fully displayed. If silk scrolls down the window and up again, all data is entered in the same Textfield, and you have the impression that silk enters garbage data. Changing the screen resolution, so that the windows was entierly displayed on the screen helped sometimes.

    Greets Chris


    ------------------

  8. #8
    Junior Member
    Join Date
    Jun 2002
    Posts
    4
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Garbage printed using SetText ()

    id say that this is a bug in SilkTest

    ------------------

  9. #9
    Senior Member
    Join Date
    Dec 1999
    Location
    Sarasota FL USA
    Posts
    109
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Garbage printed using SetText ()

    We have seen this happen several times with our scripts. It seems to happen after running some of our longer tests. To correct the problem (for now anyways) we made sure that we cleared out our vars and records before reusing them. We have also stoped using global Vars and only use locals (passing in records where the data is needed.) This seems to have fixed our problems.

    ------------------

  10. #10
    Senior Member
    Join Date
    Aug 1999
    Location
    Cambridge, UK
    Posts
    470
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Garbage printed using SetText ()

    I have seen a problem occur with records in loops, which might be related; consider the following pseudo-code:
    When in a loop, you declare a record (as in the line 'myrecord r', the initialisation of the fields isn't as you'd expect. If the fields have been filled in on a previous pass round the loop, then that is what the 'new' record's fields are initialised to. So in the example pseudo-code, even though r.field2 is not given a value by the code, it will still 'retain' the value of "bar" it was given the first time round the loop.
    I have been tripped up by this, so have taken to running all such record variables through a function which recursively sets all it's fields to null, just so I could be sure I didn't have any unwanted values hanging around.

    The moral of the story is to always declare your variables outside your loops (good practice anyway), and initialise them yourself if you want to be sure of the values they hold.

    ------------------

 

 
Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

vBulletin Optimisation provided by vB Optimise v2.6.0 Beta 4 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
User Alert System provided by Advanced User Tagging v3.0.9 (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Questions / Answers Form provided by vBAnswers (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
vBNominatevBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Feedback Buttons provided by Advanced Post Thanks / Like (Pro) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
Username Changing provided by Username Change (Free) - vBulletin Mods & Addons Copyright © 2016 DragonByte Technologies Ltd.
BetaSoft Inc.
Digital Point modules: Sphinx-based search
All times are GMT -8. The time now is 09:17 AM.

Copyright BetaSoft Inc.