#subclassing

What we know (pre-PTS)

You need to be level 50 to unlock it

Skills cost 2 skill points instead of 1, and level slower

Leveling progress is saved account wide

You must have access to the class you want (necromancer, arcanist, warden, which are/were DLC, require the DLC to subclass into)

If you already have a character that's fully leveled and of the class you want to subclass into (you're a sorc and have a templar alt, and want to subclass templar), you just have to level the skills. If you don't have a character of that class (never leveled a templar), you can do a quest to unlock leveling for that subclass, rather than needing to fully level an alt to unlock that subclass.

You must keep at least one skill line from your base class

You can only take one skill line from a specific class (ie you can be a warden at base, and take a templar and dragonknight skill line, but not 2 templar skill lines)

Passives work as stated. If they buff only skills from that skill line, then that's how it works. If it says it buffs class skills in general, it includes All class skills.

Class mastery scripts and infinite archive sets are set to your base class

The armory saves your selections

One major thing that I am finally figuring out, and another very cool thing that I learned.

First, I am finally getting ahold of the idea that I can subclass any of the standard UI objects to give them the predefined properties and behaviors that I want to be there and then use the subclass as my starting point for further code, or for direct use in a storyboard.

So the trivial example that I am actually using is a bordered UILabel.

First Cool Thing

So I drag a label into the storyboard, then I select my custom label class, in this case “CBFRoundEndLabel”. Then all my settings are automatically applied. A few things to keep in mind

Remember to use initWithCoder or awakeFromNib (see below as well) for any properties that you want the storyboard to capture.

To get inset spacing, use the alignmentrectinset

- (id)initWithCoder:(NSCoder *)aDecoder { self = [super initWithCoder:aDecoder]; if (self) { // Initialization self.layer.cornerRadius = (self.frame.size.height+self.alignmentRectInsets.top+self.alignmentRectInsets.bottom)/2; self.layer.borderColor = [UIColor lightGrayColor].CGColor; self.layer.borderWidth = 1; self.textAlignment = NSTextAlignmentCenter; NSLog(@"border %.1f", self.layer.borderWidth); } return self; } - (UIEdgeInsets)alignmentRectInsets { //tlbr return UIEdgeInsetsMake(2, 10, 2, 10); }

Second Cool Thing

The other thing that I learned was using the “User Defined Runtime Attributes”. You can set colors of any UI-compatible property that is exposed in the header file. You simply define keys and values in the “identity inspector”. Then in the awakeFromNib method, you set the value of the UIElement equal to the property corresponding to the key. But you must do this in awakeFromNib or else you crash.

That's a good name for protected extensions for a subclass that I came across in UIGestureRecognizerSubclass.h