[01:28] err.. move workspace has been changed back [01:28] but i cant find in ccsm where that is configurable [01:28] its not in "viewport switcher" and its not in unity settings [01:28] ahh its in Desktop Wall ;) [01:29] lol god dammit i just got used to the new way of doing it too.. *facepalm* cant win can you [04:39] thomi, hey, are you around on a wonderful Saturday? [04:43] bschaefer: yup [04:43] bschaefer: but it started raining, so I'm indoors :( [04:43] what's up? [04:44] thomi, nothing much, just working on getting some introspect for LensView for this no-result-message branch im doing [04:44] cool [04:44] thomi, but ive never done introspect and now I seem to be stuck on how get_state_by_path is reading '\Unity\DashController' [04:45] as I tried '\Unity\LensView' and nothing was in it [04:46] and im not seeing what the DashController is doing differently then the LensViews introspect wise. [04:47] bschaefer: [04:48] ok, the introspection tree is a tree, so "/unity/DashController" says "get me the dashcontroller object which is a direct parent of unity (which is the root node)" [04:48] bschaefer: if you're doing stuff on the python-side, your properties will appear magically in the LensView class [04:49] thomi, is seems like /unity/LensView hasnt been added to the tree [04:49] so if you've added a property called 'foo' in unity, you can do something like this (all from memory, so may be innacurate): [04:49] my_lens = controller.get_current_lens() [04:49] my_lens.foo [04:49] bschaefer: it has, we already use it in autopilot [04:49] dbus.Array([], signature=dbus.Signature('a{sv}')) [04:50] bschaefer: but the lensview isn't a child of Unity, so it's more like /Unity/DashController/LensView [04:50] is what I get when I try to get its state :( [04:50] o [04:50] hang on, let me look up the proper path... [04:50] I was looking for something like that too, hmm [04:51] /Unity/DashController/DashView/LensView [04:51] where is that stored at? [04:51] bschaefer: the tree can be visualised by running $ ./tools/unity-introspection-visualiser.py -d [04:51] as I greped through the entired unity dir looking for a path '/unity/DashController' and didn't find anything :( [04:52] ..you'll need the autopilot module to be in your PYTHONPATH, if it's not already [04:52] anything that was usefull at lease [04:52] bschaefer: no, it's not stored as a full string like that [04:52] that would explain that! [04:52] you just know that the DashView adds the LensView instnces, and the DashCOntroller adds the DashView instance, and UnityShell adds the DashController instance :) [04:53] yeah as soon as you said the path i was like UGG! haha [04:53] I was thinking namespaces [04:53] bschaefer: but I'm a little concerned - you shouldn't need to know that path at all - autopilot takes care of that stuff for you automatically [04:53] you should never need to call get_state_by_path yourself [04:53] thomi, so what I need to do! [04:54] my_lens = controller.get_current_lens() [04:54] my_lens.foo [04:54] thomi, I need to access a private var [04:54] from LensView [04:54] bschaefer: ok, first thing: add it in LensView::AddProperties [04:54] in unity [04:54] thomi, did that already :) [04:55] ok, then it will be in python already [04:55] thomi, I was just having problems finding where the hell LensView was [04:55] bschaefer: get it from the dash emulator... [04:56] idk what that is... [04:56] that standalone dash? [04:56] bschaefer: if you look at the tests in test_dash.py [04:57] 'self.dash' is the dash emulator - it allows you to get useful stuff out of unity [04:57] and in that file, if you search for "self.dash.get_current_lens()" [04:57] oo yeah [04:57] you'll see places where we get the current lens [04:57] which is an instance of the LensView class [04:57] yeah I saw that, I thought you ment something else... [04:57] yeah [04:57] ...which contains all the properties that are added on the unity-side [04:58] thomi, sweet thanks! [04:58] bschaefer: no worries - ping me if you have any Q's [04:59] thomi, found the bool I needed from LensView :) [04:59] I agreed to give a talk at the local college this Tuesday... now I have to come up with something... [04:59] cool! [04:59] thomi, haha about what? [04:59] * thomi heads back to fighting with LibreOffice Impress [04:59] thomi, good luck! [04:59] bschaefer: unity, testing & code quality - what else? [04:59] :) [05:00] thomi, some awesome computer science topic! [05:00] yeah. I may be frightening them a bit [05:00] ahh well [05:00] thomi, haha [05:01] Im learning how different computer science is vs software engineer everyday I work here haha [05:38] thomi, sweet, that went smoothly; but lets see what you have to say about my autopilot test :) [05:39] https://code.launchpad.net/~brandontschaefer/unity/fix-711199/+merge/89192/ [05:39] (diff still needs to update) [05:42] o im missing sleep after the second type [06:01] * thomi looks [06:03] * thomi waits for the diff [06:07] thomi, also, last time I ran the ibus test the dash wasnt opening :( [06:07] thomi, let me test it really quick though [06:07] bschaefer: really? [06:07] ok, there are some dash issues, but most tests pass on jenkins [06:08] thomi, yeah, let me make sure though. I had to restart my VM [06:08] which could easily be the problem too [06:08] (the VM part) [06:10] thomi, hmm wel it started once, then it didn't [06:10] bschaefer: maybe a VM issue? [06:10] thomi, also if you start the test before the dash view has had time to init you get this [06:11] return self.get_children_by_type(DashView)[0] [06:11] IndexError: list index out of range [06:11] }}} [06:11] but thats for 60 seconds after start up haha [06:11] (unless you open the dash) [06:12] thomi, it could easily be a VM issue. Compiz has started to crash on me more latly :( [06:12] hmmm [06:12] thomi, but how does my other autopilot test look? [06:13] just looking now [06:13] thomi, sorry, got you side tracked ;) [06:13] no worries, I need abreak anyway [06:15] bschaefer: OK, the test looks good, but I think you should split it into at least three separate tests: 1) open app lense, verify that no message is shown before typing anything. 2) open app lens, type 'a' verify no message is shown. 3) open app lense, type "kjashfjksadjk", verify message is shown. [06:15] thomi, sounds good! [06:15] thomi, I was worried I was cramming to much into one test [06:16] bschaefer: as a general rule, try not to do anything after an assert [06:16] as in: do something, assert something. [06:16] thomi, alright! [06:16] having said that - sometimes we can't avoid making it more complicated than that [06:16] thomi, one thing actually so [06:16] thomi, so if the dash has a string in it already so "ljadslfk" [06:16] thomi, then I open the dash without typing and check no message is shown, but that text is left over [06:17] bschaefer: when you do dash.reveal_app_lens, there's an optional parameter that defaults to true to clear the old message [06:17] so by default it will delete the old string [06:17] thomi, I think I saw that, it does a ctrl+a and delete I think [06:17] check out the 'reveal_app_lens' method in dash.py [06:17] exactly [06:17] alright! [06:18] but I set the class up so it can get added when there is some introspection the results each lens returns :) [06:18] well mostly just the name haha [06:21] Right, gotta cook dinner or starve. It's a harsh reality, but it's high time I faced it. [06:21] maybe I can find something in a jar that smells edible... [06:21] * thomi wanders into the kitchen [06:21] thomi, hahaha, I enjoy peanut butter in a jar :) [06:21] thomi, good luck not starving, it is a tough world [06:32] thomi, pushed changes! Thanks again [07:11] god damn.. somebody fix fglrx..i just want to cry [08:28] is anyone here? === yofel_ is now known as yofel [15:06] Hi all! [18:18] mhall119: hey