Haven't seen this. Questions:
1) Is the script step used to instantiate the window followed up by a Select Window step?
2) Is the new window's name unique?
3) What are the exact options on the new window when it is opened?
4) Are there any other windows on the machine at the time that have been opened via the New Window script step, and what are their settings?
regarding your questions:
1: No, the window is selected, because it´s new. As to our knowledge there is no need to select it "again" after having created a new window.
2: Yes. We even check for this in the script. No new window would be created if it would already exist.
3: Resize yes, close yes, maximize yes, modal, position starting at 10:10
4: No. There is only the main normal window and the newly opened dialog window.
No, there's no need to select it again - but sometimes, a second script winds up getting called due to a script trigger and that can gum things up. This can also create problems if you try to create a new window with the same name as an existing one (because the new one winds up with the " - 2" appended on the end) and your window selection ends up choosing the wrong window.
Okay, what about the original window? Is this window set with any settings different from the norm? Perhaps the runtime has been set for kiosk mode?
first window is automatically opened with no other settings than standard
there are no other windows at all, it´s a one file/one window solution - only this dialogue window is opened
and it works with no problem on Windows 7 and Mac OS X - I have no XP anymore, to test it myself
Hm. No script triggers attached to the layout? Which window has the focus when this is happening?
the new window should have the focus
you can download the software on
In the program go to "Buchungen" on the navigation on the left side and then click on the blue export button on the bottom. A new window should appear in the front. Anyone able to test this with Win XP ?
I can't now, but our systems at work are XP. I can look at it Monday.
Had a thought while I was in the shower. (Amazing how many great thoughts are hatched in the shower.)
By any chance, was the runtime bound under Windows 7? Have you tried binding the runtime under XP and / or running the runtime using FileMaker (rather than via the .usr file)?
hi, was away from my computer
thanks for your shower thoughts :-)
Yes, runtime was bound in Win 7. Since we have no XP machines anymore, we have no chance to bind and test in XP - anyway, the FileMaker command New Window should definetely produce a new in window in front of the existing main window and not behind it. If it is reproducable, it would be a FM12 bug.
Not necessarily. If the runtime was bound under Win 7, it could be a change in window handling between XP and 7. That's why I suggested trying it using FileMaker under XP. If the behavior is different using FileMaker vs. using the .usr file, then it's an issue of the binding - which could be related to a difference in the OS.
I downloaded and ran the program. Ran it on Windows XP Pro SP3 under Parallels on a Mac Air.
Very nice looking program! Wish I knew what it was all about ( sorry, english only here ).
Anyway, navigated as you stated, clicked the Export button and the modal window popped up fine
and on top. Worked as it should.
Sorry no suggestions but that was a confirmation for you!
thank you very much for your test under realworld conditions.
By the way - the program is about double-entry bookkeeping. Thanks for your compliment regarding the UI.