Startbucks:

I didnt offer variables as a complete bypass, i offered it as a suggestion. I was just saying that if you feel the need to have something enabled and disabled within a group, use variables. Yes, I realise variables can be deleted, changes, and whatever else but the point I was making is that it is possible to toggle and event with a variable.

To Cold:

Firstly I didnt give you a cocky attitude, so lose yours", Thanks"

Secondly, to answer your question
Quote:

"What's wrong with #groupA.1 on, #groupA.2 off, #groupA.3 on (...)?"
1: That would be the same thing as using variables. I'd have to use "if ($group(#groupA.1).status == on)" everywhere.
2: Organization. Separating blocks of code not because of #groups not being able to be nested, but because of a common context, their subject.



1. Instead if having a scructure such as:

Code:
#myBigGroup on
; Removed-by-code-segement-space
#mySubGroup1 on
#mySubGroup1 end
;
#mySubGroup2 on
#mySubGroup2 end
;
#mySubGroup3 off
#mySubGroup3 end
;
#myBigGroup end


I was suggesting
Code:
#myBigGroup.MySubGroup1 on
#myBigGroup.MySubGroup1 end
;
#myBigGroup.MySubGroup2 on
#myBigGroup.MySubGroup2 end
;
#myBigGroup.MySubGroup3 off
#myBigGroup.MySubGroup3 end


Now that both puts them in individual groups and offers a group toggle via wildcard match. Now how is that putting the if ($group()) crap everywhere?

2. That seems seperated to me? Are u looking for some other block format when you contain a code segment other than what mirc is providing? If it makes u feel any better, you can do..

Code:
;#Parent on
;
#Parent.Child1 on
#Parent.Child1 end
;
#Parent.Child2 on
#Parent.Child2 end
;
;#Parent end


Now its all nice and "organized"

-KingTomato