bug
Jon
jbondy at sover.net
Sat Jun 4 14:40:33 EDT 2005
Stephen:
When I say "delete/kill a script editor" I mean to click on the red "X"
icon in the upper right corner of the editor. This causes the editor to
terminate. If the script has not been saved, the save/cancel/abandon
dialog comes up. Somehow going this route forces the error message
window to become visible, something that does not occur if you just do a
Save. In the latter case, it says "saving" cheerfully, and never
mentions the fact that the save failed. In addition, the Apply button
goes from black to trey, implying that the save succeeded. Very
misleading. Why do I think the Rev development team works on a Mac and
not under Windows <grin>
Windows XP. Not that I'm proud of it <sick grin>. This whole Revolution
push on my part is an attempt to see if I can create cross platform
tools so that I can move to the Mac without feeling helpless, and so
that I can share my tools with my Mac friends.
:)
Jon
Stephen Barncard wrote:
> What do you mean by delete/kill the script editors? I've never seen
> that term before, nor have I had problems saving scripts, except when
> I've done some name changes to stacks, which would really be my fault.
> I just type <enter><enter> and the script commits and the window
> closes. Then I do a save of the stack..
>
> Also you have not mentioned the platform that you are having window
> problems with. Mac OSX in general has a fairly rude window
> management/priority scheme, IMHO, compared to OS9.
>
> At 2:12 PM -0400 6/4/05, Jon wrote:
>
>> Dennis:
>>
>> You said "lots of cracks in the IDE". I'd have to agree.
>> I've given up on saving scripts, and now only delete/kill the script
>> editors. That way I'm SURE to see the error messages. Far too often
>> I have "saved" a script and the save did not take, with no error
>> window visible. Too bad window visibility is handled correctly
>> during a script editor kill, but not when saving a script. It can't
>> be that hard to do the latter correctly if the former is correct.
>>
>> Window visibility is a problem in general with the IDE: do an
>> <alt><tab> away from Rev and an <alt><tab> to go back, and a
>> different window appears within Rev, not the one you were working
>> on. Do a save and focus flies away to a context other than the one
>> you were working on. Lots of windows pop up so that they cannot be
>> controlled (kill or minimize buttons hidden behind other windows) and
>> many windows cannot be hidden at all, and can only be killed, forcing
>> the user to reactivate them from scratch.
>>
>> I like the (theoretical?) cross-platform aspect of Rev, and some
>> things are fairly easy to do in it, but the conceptual base is
>> verbose and the implementation is buggy. Sigh.
>>
>> Jon
>>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution
>
>
More information about the use-livecode
mailing list