hello,

My questions are:
------------------------
1) is the builder for PPC correct?
2) is it OK to make a call (a go ) to a SUBSTACK of ANOTHER MAINSTACK? 
Or Am I wrong?
3 )is it "legal" to build ONLY the stack that contains nearly all the 
handlers the other stacks use?

Now this is the case:

I have a project to edit old textes, with (for now) two stacks,each with 
substacks.
1) Bibliotheca
                - dico
                - aide
2)textOne
                - dicoTextOne
                - notestextOne
.......
In stacks 1 and 2, i have a btn-menu "aide" (help) for selecting a topic.
the handler in these btns are the same, and very simple (no formatting 
for the moment):

on menuPick theMenuItem
   switch theMenuItem
   default
     go card theMenuItem of stack "aide"
     show stack "aide"
   end switch
end menuPick

Sure, I have a "start using stack "bibliotheca" in the openStack of 
stack 2.

Under development, the "aide" btn works fine. I can use the cards of 
substack "aide" from stack 1 AND from stack 2
When I build "bibliotheca" (only) for OS X with it and stack 2 are in 
the same folder) the btn works fine also.
BUT when I build "bibliotheca" (only) for PPC, with the app and stack 2 
in the same folder,
... I've a CRASH (in OS 9.2) when I click on the "aide" btn!
  BUT the crash appears only the SECOND TIME. Why?
Test A
1) click the  "aide" btn of stack 1: OK
2) go to stack 2. click the btn: CRASH (System error 10) and must 
reboot...
Test B
1) go immediately to stack 2
2) click on the btn: OK
3) go back to stack 1. Click the btn: CRASH!!!


Many thanks if someone can explain that to me... I've read (and re-read) 
the doc, but not found a mention about calling a substack from another  
mainStack.

I'm using RunRev 1.1.1b
my environment is:
PBook G3 FWire, OS X 10.1.2, Build 5P 48, 320 Mo RAM - internal HD 6 Go

[EMAIL PROTECTED]

_______________________________________________
improve-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/improve-revolution

Reply via email to