| elopio | veebers: there's something weird with get_proxy_object_for_existing_process | 01:05 |
|---|---|---|
| elopio | it takes no positional arguments, yet get_autopilot_proxy_object_for_process is passing one. | 01:06 |
| elopio | http://bazaar.launchpad.net/~autopilot/autopilot/trunk/view/head:/autopilot/introspection/_search.py#L49 | 01:07 |
| veebers | elopio: good catch, it's probably due to get_autopilot_proxy_object_for_process being deprecated and not actually used anywhere. I might remove it this week perhaps | 01:18 |
| elopio | veebers: I haven't seen it in use anywhere. | 01:19 |
| elopio | so +1 to removing it. | 01:19 |
| elopio | we were using a get_proxy_object_for_existing_process with the same arguments as that deprecated method though, so I suppose at some point you removed the pid argument. | 01:20 |
| veebers | elopio: hmm, I think it was changed for 1.5 but my memory might be wrong | 01:22 |
| elopio | veebers: no harm anyway because the branch where it fails has not landed. It just seemed weird and I went to read the code. | 01:23 |
| thomi | veebers: got a moment? | 01:44 |
| veebers | thomi: in 1 minute I will | 01:44 |
| veebers | thomi: what's the haps? | 01:49 |
| thomi | veebers: in _launcher.py, in ApplicationLauncher.__init__ | 01:49 |
| thomi | the docstring says: | 01:49 |
| thomi | :keyword case_addDetail: addDetail method to use (self.addDetail if not | 01:49 |
| thomi | specified) | 01:49 |
| thomi | but I don't see where 'self.addDetail' is used if the parameter is None | 01:50 |
| thomi | amI missing something, or is the docstring just wrong? | 01:50 |
| veebers | self.case_addDetail is used in UpstartApplicationLauncher (which inherits) I'm pretty sure the others did to but have been modified since | 01:51 |
| veebers | thomi: wait, I think i misunderstood | 01:52 |
| thomi | veebers: yeah, I see where it's used, but I'm asking why the docstring says that self.addDetail will be used if that parameter is None | 01:52 |
| veebers | thomi: I'm not sure, that's been recently changed by max (the docstring and the use of self.addDetail if none is passed in) | 01:53 |
| thomi | hmm, ok | 01:53 |
| thomi | I'll remove the docstring comment | 01:54 |
| veebers | thomi: ok | 01:54 |
| ePierre | hey there! | 02:52 |
| josharenson | Me again with another question... Can anyone explain the position attributes listed here http://developer.ubuntu.com/api/devel/ubuntu-14.04/autopilot/api/input.html#autopilot.input.Mouse.move_to_object | 18:01 |
| josharenson | Can't seem to find any examples or any qml docs mentioning those atts | 18:01 |
| balloons | josharenson, globalRect is from qml | 18:09 |
| josharenson | Do you have any documentation? Google turns up nothing except autopilot code. | 18:10 |
| josharenson | click/touch and drag is the last thing I need to get working... I'll stop bothering you after I figure it out. | 18:11 |
| josharenson | :-p | 18:11 |
| balloons | I guess I confused by what you are asking | 18:19 |
| balloons | if you select and object, this method will move to it.. it tries to use any properties it finds for the object in order to move | 18:20 |
| josharenson | balloons, how do you set those properties? When I try in my QML code, it doesn't run. | 18:30 |
| josharenson | and I can't find any QML API info about those attributes | 18:30 |
| balloons | josharenson, afaik, it's a runtime interpertation. You would set the unit size if you are writing a ubuntu sdk app. | 18:36 |
| balloons | you layout your UI in qml, and it's interperted and displayed. the actual coordinates will vary depending on the device you run on | 18:38 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!