SPONSORS:






User Tag List

Results 1 to 3 of 3
  1. #1
    Junior Member
    Join Date
    Dec 2001
    Posts
    14
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Any way to create a compiled window declaration on the fly?

    Our target application can throw an error message or other message dialog. These can be any number of levels deep, and they are modal. Rather than declare these dialogs many times, specifying a different parent in each declaration, we are experimenting with using GetActive() and then GenerateDecl() to get a declaration of the message dialog when it pops up. My question is, is there any way to use the info returned by GenerateDecl() to generate a compiled window declaration on the fly? (We don't want to write the declaration to a text file for later compilation; we want to use the declaration to immediately identify the dialog.)

  2. #2
    Senior Member
    Join Date
    Jul 2000
    Posts
    117
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Any way to create a compiled window declaration on the fly?

    Sadly, no way (that I'm aware of) to "compile on the fly" within Silk -- unless you build a framework around Silk and invoke it multiple times ... (ouch)!

    Scripts (and their include files) are pretty much compiled at the start of a run.

    Out of curiousity, though, won't the ~ActiveApp/ syntax work for you in this case?

    Simply do one "generic" dialog declaration with ~ActiveApp/[DialogBox]whatever as the tag. Check the online help for some examples and more info.

    I'm making some assumptions about the dialogs that may not be true, so you may have already headed down this path and abandoned it ... but wanted to offer it up "just in case" ...

    BTW -- what you're asking for would certainly be way cool, I've seen several people ask the same questions in this and other forums over the years.

    Good luck!

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

  3. #3
    Junior Member
    Join Date
    Dec 2001
    Posts
    14
    Post Thanks / Like
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: Any way to create a compiled window declaration on the fly?

    Thanks, Brent for your response. Yes, we tried ~ActiveApp, and it works only if the message dialog has only one level of parentage above it. We also tried multitagging thusly:

    "../Our dialog"
    "../../Our dialog"
    .
    .
    .
    (as many of these as possible parents)

    This was suggested by Segue, but it does not work. In fact, in this case (these are Swing dialogs), even specifying a known parent in the tag does not work!:

    tag "Timesheet/Our dialog"

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

 

 

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 12:55 PM.

Copyright BetaSoft Inc.