what's good proceed bond common concentration window frontmost request window?


i have an concentration allows churned nsdocuments open. concentration unparalleled concentration window contains functionality i wish ask frontmost document.



i am perplexing bindings here, pretence purify bond user interface concentration window frontmost document. idea following switching frontmost request window transform perspective concentration window; controls organization properties frontmost document's denote updated graceful state changes document's model, etc.



for eventuality actions such window, it's easy only initial responder; request vigilant prevent actions around responder chain. nonetheless i wish some-more this, impetus can't bond initial responder.



a few ideas i have:




  • put an vigilant controller beak common window. request window changes frontmost status, change calm binding. rubbish i have another kind concentration window, i'd have remember offshoot adult bindings request window concentration window too!

  • make an accessor concentration nominee gets frontmost request window traversing window list. concentration window only bond by concentration delegate's method. rubbish here it's kvo compliant

  • have getter setter concentration nominee establish (and maybe set kvo-compliant? sense?) frontmost document. maybe window notifications set an ivar suitable value window loses sure status. update: i'm controlling now, indeed seems graceful clean. i set value windowdidbecomemain presentation doc window pristine (if it's tide value) windowwillclose. unless there any vital objection, substantially proceed i'll use.

  • bond mainwindow.windowcontroller.document ... comes close, solely common window becomes main, following contracting goes away. unequivocally i need frontmost document window's controller (and right class).



none seem definitely right. there improved proceed i'm missing?



Comments

Popular posts from this blog

list macos calm editors formula editors

how hibernate @any-related annotations?

why does floated <input> control floated component slip over too distant right ie7, nonetheless firefox?