| || |
Can the window declaration be done out side of silk
Can the window declarations be made out side of silk? IF this is possible then you won't have to worry about changes in window ID when app is changed this way the process of generating the declarations could be done as a part of build process and won't have to bother about manually recording the windows evertime the windowIDs change.
Or is there any way to control the window IDs some settings to be made while compiling the application so that the IDs remain static.
Re: Can the window declaration be done out side of silk
>Can the window declarations be made out side of silk?
You can do something like this using dynamic window instances. I've many JavaMainWins whose declarations exist only as part of a class definition. They are created dynamically when needed and disappear when they go out of scope. Taken to its extreme, it's possible to have no declarations at all. They'd all be replaced with constructors.
If Silk supported something like function protypes (and/or #IFDEFs), you could insert or remove things dynamically with "winclass classname : classname" blocks. Unfortunately you're only allowed one of these per-class without incurring a compile error.
>Or is there any way to control the window IDs some settings to be made while compiling the application so that the IDs remain static.
Tags can be replaced with function calls. Another way, using Silk Test plans and a setup() testcase you can modify most anything you want - for example: by actually rewriting include file code. When subsequent testcases are run, they include these changes in their compile. Be careful though, self-modifying code can get 'interesting'.