Post by cyall on Sept 5, 2013 2:12:39 GMT -8
I guess it is. ^^ I use IW 2.2.3 for all my alts though, the login choice menu is nice enough and the viewer takes distinguishing between them to the point of absurdity: it keeps a separate toolbar layout for each alt. When you count 5 inworldz alts, 3 on my private grid, the occasional dip into Island Oasis, OSGrid, or Second Life, occasional use of Firestorm (which has the same feature), AND the fact that the folder where the IW beta saves its settings has changed on me twice, I've completely lost count of how many times I've removed that daft SL-only button on the left. Some days are like.. I automatically go to remove the button whenever I log in. Almost. I'll probably start actually doing that now I've posted this.
Anyway, I'd say 99.75% of the time I use Inworldz v2 beta viewer. I like some major features like persistent group notices, the lighting, and what McCabe's done with the menus. What I don't like so much is the way it drops visual updates of linksets being changed by scripts. For example, closing my wings invariably leaves them appearing very untidy, but if i right-click in the place where they're supposed to be, (not where they actually appear), then they appear sorted. Right-clicking on an object gives it a full update. When the beta was first out I had the same problem with my vardo doors. I've put it on the mantis, anyhow.
I don't think the v1 interface is going anywhere any time soon. I'm happy about that even though I think it's a mess, it's just less impractical than the v2. I would like to hack up the UI myself, to rip it all out and implement something better, or at least cleaner. Unfortunately I can't deal with complex things, so I can't really do anything with the viewer source code. I'm not about to touch the xml UI stuff, the faults in the emulation of the v1 interface show how limited it is, and besides that it's XML. If anything was ever complicated for no good reason, it's XML. I haven't entirely given up on the notion of tinkering with the viewer source, I might find some way to deal with it.
Anyway, I'd say 99.75% of the time I use Inworldz v2 beta viewer. I like some major features like persistent group notices, the lighting, and what McCabe's done with the menus. What I don't like so much is the way it drops visual updates of linksets being changed by scripts. For example, closing my wings invariably leaves them appearing very untidy, but if i right-click in the place where they're supposed to be, (not where they actually appear), then they appear sorted. Right-clicking on an object gives it a full update. When the beta was first out I had the same problem with my vardo doors. I've put it on the mantis, anyhow.
I don't think the v1 interface is going anywhere any time soon. I'm happy about that even though I think it's a mess, it's just less impractical than the v2. I would like to hack up the UI myself, to rip it all out and implement something better, or at least cleaner. Unfortunately I can't deal with complex things, so I can't really do anything with the viewer source code. I'm not about to touch the xml UI stuff, the faults in the emulation of the v1 interface show how limited it is, and besides that it's XML. If anything was ever complicated for no good reason, it's XML. I haven't entirely given up on the notion of tinkering with the viewer source, I might find some way to deal with it.