Closed kyuucr closed 10 years ago
The ideal variant would be to have this fixed on both, but if it comes to selecting a version I would be in favour of supporting the latest one.
Please ignore my rants above, now I use the same method of determining Shell version by @mpnordland, version fragmentation should not be a problem, thanks dude! :+1:
Not yet tested in 3.10 though
@cldx Can you test if it works on 3.10? @ndyakov Code review?
I've got a hold on machine running 3.10 and tested it and it looks okay
Fixed hover not synced when popup menu closed because forgot to emit the event. Also, I noticed that this:
this.dash.connect('menu-closed', Lang.bind(this, this._box.sync_hover));
doesn't seem to call sync_hover correctly, so I revert to the original:
this.dash.connect('menu-closed', Lang.bind(this,
function() {
this._box.sync_hover();
})
);
I suggest we have to be more careful when cleaning that kind of function.
Tested on 3.10 and 3.12 and merged
Fixes #20 ? The original popover uses AppIconMenu which defaults the PopupMenu to appear on right side (or left side if you're RTL) by calling it's parent initialization (which is PopupMenu)
this.parent(source.actor, 0.5, side);
I need to change theside
toSt.Side.TOP
. If I could only easily extends the original AppIconMenu and change it, but can't. Extending original AppIconMenu means if I callthis.parent()
it means that I call AppIconMenu initialization, which has noside
option. Therefore, I choose to fork AppIconMenu from 3.12, which will give a problem in 3.10.Picture below is a screenshot of implemented popover versus the original one. The implemented one has more options that should not be available in 3.10, but clicking those items has no effect whatsoever.
I need all of your suggestion, should we use the AppIconMenu forked from 3.12 or the original 3.10? And should we choose only one version to develop in?