Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cs.utexas.edu!samsung!munnari.oz.au!bunyip!lance!kirk!cameron From: cameron@kirk.nmg.bu.oz (Cameron Stevenson) Newsgroups: comp.sys.mac.hypercard Subject: Re: Background Button Problems Message-ID: <1767@kirk.nmg.bu.oz> Date: 18 Aug 90 00:46:49 GMT References: <2080@ux.acs.umn.edu> Organization: Network Management Group, Bond University, Australia Lines: 46 From article <2080@ux.acs.umn.edu>, by clarson@ux.acs.umn.edu (Chaz Larson): > In article <15824@s.ms.uky.edu> miles@ms.uky.edu (Stephen D. Grant) writes: >> >>What can I do to get one card to hide a button for it, and then show or turn >>on the button when it goes to the next card?? Arf! > > On the appropriate cards, cover the offending background button with a card > button containing the following script: > > on mouseUp > --do nothing > end mouseUp > > that will absorb any clicks that might otherwise get to the background button. > > You can use card graphics to visually hide the button. > > > Chaz, without sounding rude, this seems like a very clumsy way to hide a few buttons. Sort of bulldozer effect - cover the bloody thing up and it might go away.... What is wrong with: on opencard hide bg btn BUTTON_NAME end opencard accompanied with: on closecard show bg btn BUTTON_NAME end closecard Those two handlers, placed in the scripts of every card for which Stephen wants the bg btns to disappear will work. Alternatively, if there are more cards in that background that need the buttons to disappear, than ones that don't, then create a new background without the offending buttons (and have two backgrounds in your stack - what a concept, eh?) Cheers.... Cameron Stephenson Telephone +61 75 951220 Bond University Gold Coast Australia