Redraw problems in FMP 6.0v3 on MacOSX v10.2

[spragueg]

I have FMP v6.0v3 installed on a Mac running Mac OS X 10.2. I have a database that has a few layouts with up to 5 portals. The file is served from a Mac running 5.5 server on X. Three of the portals can have as many as 100- 400 items in them the other two have 1-3 records at any given time. The problem is that when I click buttons that set globals to filter the portals, the screen does not update. However if I minimize the window into the dock and then bring it back the data is there. So it seems I have a redraw problem. This does not happen in 9.x or on Win 98 with the same file. Any one out there having the same problem?

Thanks,

G

[Anatoli]

That is happening also on other systems e.g. Windows. When portal record is deleted the screen also doesn't redraw to show that.

Put some minimize or toggle stuff on the end of the script. It will blink, but it will be better than not redraw at all.

[falkaholic]

I've had problems on Windows 98 and OSX 10.2 both with 5.5v2.

The windows one would never redraw anything in layout mode., had kind of the same problem the other day with OSX 10.2 with a layout that had many fields and layout objects. I think its a memery issue and/or just the ghettoness of FM 5.5 in OSX.

[spragueg]

Put some minimize or toggle stuff on the end of the script. It will blink, but it will be better than not redraw at all.

Yeah, I tried that. It dosen't work. Thanks anyway.

[Anatoli]

I am 100% sure I did something like this.

Maybe going to another record and back?

Probably the minimize doesn't refresh the window.

[The Bridge]

You might also want to try script steps like Exit Record, Go to Field(""), and/or Flush Cache to Disk to force FileMaker to update the display.

[spragueg]

Maybe going to another record and back?

It's way too slow. Too many portal records.

I still think it may be one of my scripts causing a problem.

It dosen't matter anyway I'm just testing 10.2 and FMP 6. All my clients are still using Mac OS 9.2 and FMP 5.5. I'm not wasting any more time on this. I just hope it's fixed by a future release.

Of course, they never fixed the Scheduler in 5.5 Server on X. Why would they fix this?

Thanks,

G

[spragueg]

You might also want to try script steps like Exit Record, Go to Field(""), and/or Flush Cache to Disk to force FileMaker to update the display.

Yeah I tried Exit Record and Go To Field. No dice.

I can't do flush cache due to the fact htat the file is on a server and the action required will be perfomed once every few seconds (user click button in portal rows) so the constant flow of 150+ users asking to flush cache every 2-3 seconds would be very bad for performance. This is what I assume. I may be wrong but it stands to reason that this would cause a problem. Anyone disagree?

It seems to me that filemaker is acutually updating the window or it believes that the window was updated. If I drag a finder window infront of the database window then drag it away the data is updated. But it's instantaneous like the data was always there just never drawn to the screen. Maybe a bug with FileMaker and the new Quartz layering technology? Or to much data in too many portals and filemaker is spending more proccessing power on making sure the data is correct and lapsing on actually updating the window for whatever reason.

Thanks,

G