[futurebasic] Re: [FB] Slowdown in Leopard?

Message: < previous - next > : Reply : Subscribe : Cleanse
Home   : November 2007 : Group Archive : Group : All Groups

From: Brian Stevens <bstevens33@...>
Date: Sat, 3 Nov 2007 10:52:00 -0700
Hi John,

This issue has been observed and reported on the FB beta list but  
there is no solution yet. Steve Crossman and Rich Love have discussed  
their respective experiences and might be able to offer more  
technical details (i.e. which version of FB, which version of FB  
compiler, Intel mac vs. Power PC Mac etc.). It is definitely a  
Leopard issue. I believe Steve and Rich first saw this slowdown with  
the FB editor (also an FB app). Only FB compiler-created apps are  
impacted; Native Universal Binary apps created with FBtoC are not.  
I'm not sure if PowerPC macs updated to Leopard also have the  
problem.   Those guys can undoubtedly offer more. We definitely need  
a matrix of what machines (Intel vs PowerPC), what OS (assume only  
Leopard), what version of FB, what version of the FB compiler are or  
are not impacted. The LaunchCFMApp might be involved since it does  
the loading. Identification of we know in one email would help.

Brian S.


On Nov 3, 2007, at 10:26 AM, John McKernon wrote:

> Dear friends,
>
> I've just run into an odd thing: Running my FB app in Leopard, it gets
> slower and slower the longer you run it. After just 20 minutes, it  
> can't
> keep up with typing into an edit field. It works, just waaaaaay  
> slowy. Speed
> is normal when it's first launched.
>
> I ran Activity Monitor and didn't see anything unusual.
>
> It's a project that was originally built with PG and converted to
> Carbon/Appearance.
>
> Anyone have any suggestions? Have I missed some change along the way?
>
> - John
>
> Here are some details:
>
> ---------------------------------------------
> The edit fields are really simple:
>
> gGenericT=85
> gGenericL=289
> gGenericB=98
> gGenericR=593
> A$=""
> TEXT _geneva,9
> EDIT FIELD _DisplayEditBox,A$,@gGenericRect,1,1
>
> ---------------------------------------------
> It has an event loop, on the PG model:
>
> ON BREAK      GOSUB "PG:Chk Break"
> ON DIALOG     GOSUB "PG:Dialog"
> ON EDIT       GOSUB "PG:TEKey"
> ON EVENT      GOSUB "PG:Event"
> ON MENU       GOSUB "PG:Menu"
> ON MOUSE      GOSUB "PG:Mouse"
> ON TIMER(-10) GOSUB "PG:Timer"
> ON STOP       GOSUB "PG:Stop"
>
> gSubAction =_mainStart
> GOSUB "PG:Any Main"
>
> DO
> IF FN pGBestWindow THEN WINDOW OUTPUT FN pGBestWindow
> HANDLEEVENTS
> IF gKissOfDeath THEN GOSUB "PG:Break"
> UNTIL 0
> if 0 then return
>
> ---------------------------------------------
> Here's a typical window build:
>
> wa=_kWindowFullZoomAttribute_kWindowCollapseBoxAttribute_kWindowResiza 
> bleAtt
> ribute_kWindowCloseBoxAttribute
>
> gWindowRect.left=0
> gWindowRect.top=40
> gWindowRect.right=800
> gWindowRect.bottom=540
>
> fn SetWindowPos(_DisplayWnd,_zTrue)
>
> appearance WINDOW -_DisplayWnd,"untitled",@gWindowRect,
> _kDocumentWindowClass,wa,_noAutoFocus'_updateVisRgn
> def setwindowbackground (_kThemeActiveDialogBackgroundBrush,_zTrue)
>
> --
> To unsubscribe, send ANY message to: futurebasic- 
> unsubscribe@...
>

Brian S.