bug

[Dennis Brown]

I'll give you another one.  Ten minutes ago I made a new group, then  
I made a group of this group plus a table field I have had around for  
weeks.  As soon as I hit the group button, the table field  
disappeared.  I looked all over for it... no dice.  I looked in the  
app browser... totally gone (my new group was there though.  Only  
thing to do was revert.  Since I recalled this happening to me  
before, I decided I could live without the extra group and put in a  
few more lines of code instead.  The IDE bites me every hour or so  
since I began working with it regularly a couple of months ago --and  
I am just doing simple things (I don't know how to do the really  
complicated stuff that I might expect has less use and testing).  It  
just does not seem right to bite the hand that feeds you.  I hope  
Kevin's promise of an improved IDE soon will come true.  I hate  
getting poked in the eye several times a day.

Dennis

On Jun 4, 2005, at 9:55 PM, Jon wrote:

> Dennis:
>
> "I think  the IDE should ask if you want to apply before running  
> the script  again, or always apply when leaving the window focus"
>
> I agree totally.
>
> "I like to leave the script I am debugging/improving open with the   
> script running so I can quickly try different things with nary a   
> mouse click.  You learn about "apply" very quickly in that case. "
>
> I gave up on this when the IDE started to spontaneously just  
> disappear when I tried to click the Files menu.  I HAVE to save to  
> disk, because I don't trust the IDE as far as I can throw it.
>
> Sigh.
>
> Jon
>
>
>
> Dennis Brown wrote:
>
>
>>
>> On Jun 4, 2005, at 2:12 PM, 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.
>>>
>>
>>
>> Jon,
>>
>> Sounds like you were saving the script, before Applying it.  I  
>> got  caught a few times on that also.  I am in the habit of  
>> hitting the  enter key after editing a script to apply it now.   
>> Otherwise, the  script says what you edited, but it executes what  
>> was last applied  before your last edits.  I don't like this way  
>> of doing it, I think  the IDE should ask if you want to apply  
>> before running the script  again, or always apply when leaving the  
>> window focus, and having a  proper unlimited undo for at least the  
>> text editing of a script -- that can't be that hard to do.
>>
>> I like to leave the script I am debugging/improving open with the   
>> script running so I can quickly try different things with nary a   
>> mouse click.  You learn about "apply" very quickly in that case.
>>
>> Dennis
>> _______________________________________________
>> use-revolution mailing list
>> use-revolution at lists.runrev.com
>> http://lists.runrev.com/mailman/listinfo/use-revolution
>>
>>
>>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution
>