I think the only thing we have going is the Product Issues area. It would be nice to see those categorized as issues by version. I think the Product Issue area is working.
Is the web viewer still using Safari 5.0 on Mac?
3 of 3 people found this helpful
FMI has never stated when a issue will or will not be fixed.
TS employees following up on previous post. When FMP16 was released TSGAL updated several post with such statements "This issue has been addressed in this version".
If there is a post you are following and there has not been an update in awhile you can always send a message to the TS person that responded to the post.
We still expect a v1 update soon.
At least I hope they will bring something as we have some more conservative customers which won't install version 16 before there is the first bug fix update available.
1 of 1 people found this helpful
FileMaker 16 uses WebKit 2 on Mac and IE11 on Windows.
That's great step forward, but broke a few scripts.
I could recommend a database product FMI could use to track and make public their bugs for their customers.
They could even JDBC-enable it so people could do non-FMP automated searches.
Crazy talk, right?
Although I usually jump right in with new releases, I can't say I blame anyone for waiting given the track record here.
PhilModJunk used to maintain a bug databases, that he created in FM and he provided it to the community. He might let you get a copy to maintain. I'm sure it's a big job.
If new features (for which we probably already have workarounds in place in our solutions) are less than optimal, I don't consider it being red alert.
The only problem for me, as a developer on mac, is the debugger thing. But it's not a problem for my clients. Moreover, as I said somewhere else, FM16 has yet to crash on me, while 15 does it too frequently for being a DBMS.
Add to that the lack of slowing down with use, which affects 15 but not 16, and the result is that I advise clients to make the jump, no matter when a patch will arrive and what it will fix.
2 of 2 people found this helpful
I know this will astonish people, but FMI uses (internally developed) bug-tracking software... created in... FileMaker.
It and the bug report content it manages is not publicly available due to a wide variety of factors. It is company policy not to pre-announce fixes or schedules (mainly because it may be pulled at the last minute if something catastrophic is discovered, but for other reasons too.)
As for the auto-scroll bug in Debugger on macOS, I would recommend that you check that first after installing any update to v16 in the future.
Which OS are you on? Just curious.
I recently moved to a new Macbook Pro ( 2016, macOS 10.12 ). On 10.11, 16 never crashed. On 10.12, I am getting very frequent stalling and "Application Not Responding" messages.
2 of 2 people found this helpful
Sure that makes sense.
If FMI publishes a "what was fixed" with a new version point release, that's fine too. I was just wondering what happens to all the reported bugs and what competitive advantage is really lost by being a little more transparent on their status (or even if FMI considers a reported forum-problem a bug at all).
On my development machine in the office I'm still on the latest 10.11.
Here at home I also do a lot of development and I'm on 10.12.6 beta.
no stalling, swift swimming in our 93 database files solution.