sorry for the screenshot - but the system didn't let me save the issue report without a screenshot. is this new?? ouch..
(I'm on a iPad)
I find several similar issues reported in my Known Bugs list.
For More Information see:
Many acknowledged bugs can be found in the Known Bug List here in the Report an Issue section of the forum.
The list can also be downloaded as a database file from: http://www.4shared.com/file/8orL8apk/FMP_Bugs.html
all I wanted to say is that I have that issue every couple of days - and before Lion, I've had it a couple of times a year...
Such additional info is welcome and should be reported. I know from other posts that some FileMaker techs are (hopefully) busily investigating some other reports of trouble with Lion and FileMaker (Pro and Server).
Thank you for your post.
When FileMaker Pro closes a file, it records the position and size of the file window, so the next time the file is accessed, it opens in the last saved position and size. If you close the file when it is not on the main monitor, then when you bring that file to another computer, the file may open to what it believes is a second monitor and be out of view.
I don't have a reason why the file is not opening in the same position on the same computer unless you changed the mointor configurations. If you run this on a one monitor system, do you ever experience the problem?
I realize more than two months have passed, so if you have either a resolution or additional information about the problem, please post here so others can benefit or help.
thank You very much for Your answer!
- allways the same machine
- I realized that FM will open files on a wrong position/in a wrong size more often, I beleve that this is an issue of Lion
- FM stores not the files proper size/position, can be the size/position of the file that was used the last time
I realized similar issues i.e. with OmniFocus as well (position 0;0 instead of the last position after a newstart)
while supporting a customer with an own FM solution (she wrote that solution by here own, not my work...), I realized the same issue - a small starter file was opened in the position (and the much bigger size) of the file that was used the last time before quitting FM - therefore, it' not an issue with my Mac.
Those files are files without any change during the last db-session.. maybe that's the point. Have not had that issue under older OS, AFAIK