Problem with porting a CScrollView to the macintosh
Flora Gurcharan -- GFLORA@farn03.datasci.co.uk
Tuesday, May 14, 1996
Hi folks,
Can anybody help me with a problem porting an MSVC++ 4.0 app to the mac
please ?
I have a CScrollView-derived view placed on a CTabCtrl; The scrollsizes need
to be adjusted according to
which page of the tab control is active. This works fine on the PC, but on
the Mac causes problems:
If the scroll size is small enough that scrollbars are NOT required,
everything is fine; However, if the total
size is set larger than the viewable area, i.e. scrollbars are needed,
everything slows down dramatically.
Changing the tab page, or any of the other controls available, take ages -
there's a delay of up to 6 - 7
seconds routing straight forward mouse messages to the appropriate place. I
discovered this by adding
an OnLButtonDown() handler to the CScrollView, and the delay between the
click and the MessageBeep()
(which was all the handler did) was typically 4 - 6 seconds. Even the clock
on the mac only updates
itself every 3 -4 seconds in this situation, but as soon as you turn to a
tab page that doesn't need
scrollbars, everything is fine again.
As I said, this only happens on the mac, the PC is fine.
Any help greatly appreciated !!
Thanks,
Jools
Flora Gurcharan -- GFLORA@farn03.datasci.co.uk
Thursday, May 23, 1996
Hi folks,
Can anybody help me with a problem porting an MSVC++ 4.0 app to the mac
please ?
I have a CScrollView-derived view placed on a CTabCtrl; The scrollsizes need
to be adjusted according to
which page of the tab control is active. This works fine on the PC, but on
the Mac causes problems:
If the scroll size is small enough that scrollbars are NOT required,
everything is fine; However, if the total
size is set larger than the viewable area, i.e. scrollbars are needed,
everything slows down dramatically.
Changing the tab page, or any of the other controls available, take ages -
there's a delay of up to 6 - 7
seconds routing straight forward mouse messages to the appropriate place. I
discovered this by adding
an OnLButtonDown() handler to the CScrollView, and the delay between the
click and the MessageBeep()
(which was all the handler did) was typically 4 - 6 seconds. Even the clock
on the mac only updates
itself every 3 -4 seconds in this situation, but as soon as you turn to a
tab page that doesn't need
scrollbars, everything is fine again.
As I said, this only happens on the mac, the PC is fine.
Any help greatly appreciated !!
Thanks,
Jools
Howard Rubin -- hrubin@nyx.net
Saturday, June 01, 1996
Jools,
You didn't say what you've tried so... Here are two things that help MFC
Macintosh performance. Compile for release rather than debug and increase
your memory size either in the mac resource file or using Command-I.
Howard Rubin
>If the scroll size is small enough that scrollbars are NOT required,
>everything is fine; However, if the total size is set larger than the
>viewable area, i.e. scrollbars are needed, everything slows down
>dramatically. Changing the tab page, or any of the other controls available,
>take ages - there's a delay of up to 6 - 7 seconds routing straight forward
>mouse messages to the appropriate place.
| Вернуться в корень Архива
|