IDE Interference (not just a another rant)

xbury.cs at clearstream.com xbury.cs at clearstream.com
Fri May 28 04:42:15 EDT 2004


Jan,

Well put and said... 

the solution is quite simple after all...

on suspendstack
  if the topstack is not the long name of me 
  -- optional :  AND  "app/Revolution/components/" is not in the effective 
filename of the topstack then
      save this stack
  end if
  pass suspendstack
end suspendstack

--

Now, is there any way to paste script text
in the script editor WITHOUT textstyle?

--

And yet another crash... 

Am I the only one experiencing these crashes?

cheers
Xavier

On 28.05.2004 09:39:34 use-revolution-bounces wrote:
>--- xbury.cs at clearstream.com wrote:
>[snip]
>>
>> >> Should the suspendstack be sent to the stack each
>> time you edit an
>> >> object causing a save? One missing feature (no
>> blame anywhere) is
>> >> the function
>> stackwaschangedsincelastsave()=true|false... The
>> other
>> >> is that the suspendstack should be ignored while
>> in the GUI design
>> >> mode of RR...
>>
>> >Yes, of course it should be sent. That's how the
>> message is defined.
>> >Nobody said to put a save handler in there!
>>
>> You didn't get my point. But if I want a
>> suspendstack event, it's my
>> business
>> to have one as it is a feature. The point is that
>> when you are in an IDE,
>> the IDE
>> messaging should NOT interfere with your
>> applications' events. When I
>> choose a different tool, go to the message or to set
>> an object's
>> properties
>> via the pallete, I am NOT leaving my application...
>> In RR's case, it is...
>>
>
>Hi Xavier,
>
>I would say Revolution is not to blame ; it's not
>their fault that clicking in a palette means that your
>stack is suspended and the palette receives a
>resumeStack message : it's the engine that is doing
>that, and for good reason.
>How else would you intercept certain events in palette
>stacks, to do preparation work _before_ the mouse hits
>the button ? In HC this didn't happen because a stack
>was topLevel, period -- anything else such as lmodal,
>modeless palete had to be dealt with via externals.
>If you are convinced that suspending your stack and
>resuming the palette is bad behaviour, then by all
>means use Bugzilla and rally votes on the mailing
>lists.
>But before you do so, please think about why this was
>setup that way : so that developers who switch from
>topLevel to modeless or palette would consistently
>receive the same set of messages.
>And if you still think it is a problem, please provide
>an alternative method for those who need to trap the
>resumeStack message in their palettes.
>While I realise that you were confronted with a bug in
>the engine concerning images in htmlText, the fact
>that your own solution has a downside is not the fault
>of the engine, IMHO.
>
>Best regards,
>
>Jan Schenkel.
>
>=====
>"As we grow older, we grow both wiser and more foolish at the same time." 
 (La 
>Rochefoucauld)
>
>
>
>
>__________________________________
>Do you Yahoo!?
>Friends.  Fun.  Try the all-new Yahoo! Messenger.
>http://messenger.yahoo.com/
>_______________________________________________
>use-revolution mailing list
>use-revolution at lists.runrev.com
>http://lists.runrev.com/mailman/listinfo/use-revolution


Visit us at http://www.clearstream.com
                                                          
IMPORTANT MESSAGE

Internet communications are not secure and therefore Clearstream International does not accept legal responsibility for the contents of this message.

The information contained in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any views expressed in this e-mail are those of the individual sender, except where the sender specifically states them to be the views of Clearstream International or of any of its affiliates or subsidiaries.

END OF DISCLAIMER


More information about the use-livecode mailing list