March 5, 200322 yr I have a very strange problem, I have a multi related DB which is hosted on one machine with a master file and many related files, there are portals throughout the DB that link to the other files, with buttons inside the portals that perform actions. When testing on the host machine, everything works fine. Now we come to network the solution, we find that on a client machine, a button in a portal behaves very strangely. When you click the button, as normal, it is highlighted, but then stays highlighted when you release the mouse button, it stays this way forever until you click the button again. You have to double click the button?! (But normal double clicking doesn't work, you have to pause for a second or so) Then the button activates after the second click. But this is not consistant. There are times when a single click still works, but this is rare It seems like a bug - but where exactly? Has anyone ever seen portal buttons, when running on a networked client machine require two clicks to activate? this seems to happen on a test empty DB as well as the fully populated solution. any ideas?:: I'm stumped, this is a real problem! (all machines running Mac OS X 10.2.4, FileMaker Developer 6, form mode only)
March 6, 200322 yr We are having the same problem. FM tech support here in Australia were able to re-create the problem & have informed FM in the states about it. My observations... It only happens on OS X It doesn't happen if the portal has been scrolled before clicking the button If you wait for the button to highlight it will work ok Sometimes it happens, sometimes it doesn't It happens on all versions of FM from 5.5 It happens on all versions of OS X 10.2 (not sure about earlier versions) We are running FM 6.0.4, FM Server 5.5, OS X 10.2.4
March 11, 200322 yr Author yes, that is the problem exactly. so is there anything that can be done about this? if it is a real FileMaker bug, should it be reported to FileMaker? what is the correct procedure for this? thanks for any info...
Create an account or sign in to comment