(no subject)

[Peter Brigham]

Jim Sims wrote:

> On Jan 1, 2008, at 4:35 PM, Peter Brigham wrote:
>
>
>> The problem is with Leopard; my wife has an intel mac and it runs
>> fine on that with Panther. So the Win build in Mac Studio 2.8.1
>> build 471 fails for Leopard. Do later builds work? or will I have
>> to wait for 2.9?
>>
>
>
>
> OS X (10.4.11) PPC
>
> Does not open here.
>
> sims
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> ClipaSearch Pro
> http://www.ClipaTools.com
>
> Across Platforms - Code and Culture
> http://www.ezpzapps.com/blog/

Weird. Do you get any error message? I just downloaded the file from  
the website and opened it fine. I'm using a Mac iBook G4, OSX 10.4.1.  
I have a mainstack that doesn't splash, it remains hidden, and serves  
only to open my data stack. The script of the only card in the  
mainstack consists entirely of:

on preopenstack
   set the visible of this stack to false
end preopenstack

on openstack
   go stack "recipesData" in a new window
end openstack

The preopenstack handler in the data stack script is as follows  
(there is no openstack handler):

on preOpenStack
   set the tool to browse
   set the cursor to arrow
   if the environment = "development" then
     set the menubar of this stack to ""
   else
     set the menubar of this stack to "RFmenubar"
   end if
   set the backcolor of the templatecard to 218,225,197
   if the platform = "macOS" then
     put the macHelp of this stack into h
   else if the platform contains "win" then
     put the winHelp of this stack into h
     set the textfont of btn "FileM" to "Tahoma" -- menubutton
     set the textfont of btn "EditM" to "Tahoma" -- menubutton
     set the textfont of btn "HelpM" to "Tahoma" -- menubutton
     set the textfont of btn "new" to "Tahoma"
     set the textfont of btn "delete" to "Tahoma"
     set the textfont of btn "import" to "Tahoma"
     set the textfont of btn "export" to "Tahoma"
     set the textfont of btn "find" to "Tahoma"
     set the textfont of btn "print" to "Tahoma"
     set the textstyle of btn "new" to "bold"
     set the textstyle of btn "delete" to "bold"
     set the textstyle of btn "import" to "bold"
     set the textstyle of btn "export" to "bold"
     set the textstyle of btn "find" to "bold"
     set the textstyle of btn "print" to "bold"
     set the textfont of fld "notes" to "Times New Roman"
     set the textfont of fld "ingr" to "Times New Roman"
     set the textfont of fld "dir" to "Times New Roman"
     set the textfont of fld "help" to "Times New Roman"
   end if
   set the htmltext of fld "help" to h
   put the uRect of this stack into rct
   put item 3 of rct - item 1 of rct into wndW
   put item 4 of rct - item 2 of rct into wndH
   put the working screenrect into scrRct
   put item 3 of scrRct - item 1 of scrRct into scrW
   put item 4 of scrRct - item 2 of scrRct into scrH
   set the maxwidth of this stack to scrW
   set the maxheight of this stack to scrH
   if wndW > scrW or wndH > scrH then
     set the rect of this stack to scrRct
     storeRFrect
   else
     set the rect of this stack to rct
   end if
end preOpenStack

This is all initialization stuff that should not prevent the stack  
from opening in some form or other, AFAICT. And it opens fine on my  
G4 mac and my wife's Intel mac, both running OSX 10.4.1 (I guess  
that's Tiger, not Panther as I said before). Any ideas anyone?

A different puzzle (or maybe not?): When the build is done, if I copy  
the mac version of the standalone to a different folder to force the  
finder to recognize the custom icon, that doesn't work, I still have  
the generic mac app icon. After some fiddling, I found that the  
Revolution.icns file that the standalone builder creates in the app  
bundle appears to be corrupt -- at least it crashes IconBuilder when  
I try to open it. But if I make a copy of my custom .icns file  
(created with IconBuilder) and rename it "Revolution.icns" and  
substitute it in the bundle for the one that Rev created, the icon  
then appears when I copy the app to a different folder, and all  
appears well. Has anyone else seen this? Could this be related to the  
above problem of the app not opening for some people?

-- Peter

Peter M. Brigham
pmbrig at gmail.com
http://home.comcast.net/~pmbrig/

-- Hofstadter's Law: It always takes longer than you expect, even  
when you take Hofstadter's Law into account.