This is what REALLY SUCKS about whingeing

[David Burgun]

>David,
>
>This definitely sounds like a user error. If you have more than one 
>menu group it will create confusion. If the group "fgttryiolk" is in 
>the place menu then it was because you 'the user' created it first, 
>Rev certainly did not create it or put it in your stack. Rev gets 
>blamed for things like this all of the time.

I am 100% sure I didn't create it. I reckon it was some kind of 
corruption in stack file. I don't think it was a menu group 
specifically just a random bunch of bytes that "looked" like a group. 
But anyway, even if I had created it, how come it wasn't listed in 
any stack? E.g. when I looked in the App browser, there was no 
control with the name "fgttryiolk"  anywhere in any card of any stack.


>What probably happened was that you were trying to figure out what 
>was wrong and either copied or created a menu group and while it was 
>still selected accidently typed in the name field, then deleted this 
>background group from that particular card but it was still in the 
>stack. Then you created a new group and had two menu groups and were 
>trying to fix the one but the other one was still there.

No, this was not the case, see above.

>The best approach is always to create a sample stack and put a menu 
>into it to see if it works and that you understand what you are 
>doing in that stack then try and figure out what you did wrong in 
>the broken stack.

This was/is a simple stack, with just the Menu Group in it. Can't get 
much simpler than that!

>Don't feel bad though, I certainly blame Rev first and then the Gods 
>of programming before I grudgingly look at myself as the culprit. 
>Most times if I post here others will point this out quickly and 
>then I go OHH, sorry it was me after all. The only problem is that 
>the thread looks like Rev is the problem but in reality it was me 
>all along.

I don't feel bad, it was nothing I did. This was a problem in RunRev, 
not a user error. See above.


>Next time it would be better not to put "what REALLY SUCKS about 
>Rev" in the subject line when after all it more than likely and in 
>this case was your mistake.

In this case it was not my mistake. It was a BUG IN RUNREV and this 
really is what really does suck about RunRev.

Take Care and All the Best
Dave

>I hope that this helps.
>
>Tom
>
>On Nov 24, 2005, at 3:44 PM, David Burgun wrote:
>
>>The only way I could find to fix it was to delete the original Menu 
>>Group, create a new one, and then paste the scripts back into it. I 
>>then had a problem whereby the Menu appeared across the top of the 
>>stack window (ala Windows OS). After fishing around for ages I 
>>found that in the "Place Group" there was a group that was no where 
>>in any stack and had a weird name (something like fgttryiolk). I 
>>selected it (e.g. placed it) and it appeared in my stack. I then 
>>deleted from the stack, saved the stack, quit RunRev and restarted 
>>and then it worked!!!!!
>
>_______________________________________________
>use-revolution mailing list
>use-revolution at lists.runrev.com
>Please visit this url to subscribe, unsubscribe and manage your 
>subscription preferences:
>http://lists.runrev.com/mailman/listinfo/use-revolution