hi, Am Dienstag, 19. Februar 2019, 09:46:41 CET schrieb Thomas Friedrichsmeier: > > do you have come control over their appearance? like, could they be > > 50% transparent unless you press alt? that could make it more obvious > > that alt is like the activator key for the windows. it would also > > make them less a distraction when you're writing code. > > I do not have direct control over the appearance, and little over the > behavior. Some things could be hacked, but hacks will break...
yeah, hacks should be avoided. > So, for now, I have implemented the alt+up/down idea. I intend to make > this configurable, too, if only to give users a chance to discover the > feature ;-) +1 > > on other thing: i really love the slot() completion! the only thing > > is that it lost the ability to browse objetcs recursively -- you can > > access one slot and that's it. with the @-notation, if the slot was, > > e.g., a list, you were also offered it's members and so on. can that > > be fixed? > > I noticed that mid-way through implementing it, and it's a bit > embarrasing, indeed, but I hoped it would be a relatively rare case. well... not for me :-D the tm.plugin.koRpus package is entirely built on nested S4 objects (as deep as you need it to reflect the hierarchical structure of a text corpus). it is actually the rare case for me to only want access to a top level slot. > In theory this can be fixed, but it's not totally easy: We'll have to do a > little more parsing so that RKWard will understand that slot(x, y) > refers to the object's slots. i can imagine the @ operator is easier to parse. > Perhaps add a ticket, for now. will do. viele grüße :: m.eik -- dipl. psych. meik michalke institut f"ur experimentelle psychologie abt. f"ur diagnostik und differentielle psychologie heinrich-heine-universit"at d-40204 d"usseldorf
signature.asc
Description: This is a digitally signed message part.
