On Mon, 2026-05-11 at 12:15 +0100, Richard Shann wrote: > On Sun, 2026-05-03 at 18:35 +0100, Richard Shann wrote: > > I've just pushed what I hope is a fix for the bug which caused us > > to > > switch to libatril instead of libevince (the links in the Print > > View > > didn't work). > > One consequence of this fix is that you can no longer select an > object > in the Print View *and* get the menu for it just by right clicking on > the object. I have fixed this - if you right click it will select & pop up the menu, if you left click it will just select. Richard
> You have to select it (with Shift-left-click) and then > right click on the blue marker that indicates it is selected. > I haven't been able to figure out why just right clicking was working > before, so unless someone has a bright idea we will have to live with > that. > > Richard > > > > It seems that the guys at evince decided on a rather different > > semantics for what it means to be the "same" signal. We were > > catching > > the signal "button_press_event" and handling it and also catching > > the > > signal "external-link" and handling that. But at some point it > > would > > seem they decided that external-link would not be fired if > > button_press_event was declared dealt with. It seems that libatril > > has > > not (yet?) adopted this change and so it carried on working. > > So the fix just comprised allowing further signal handlers to fire > > after we have finished with button_press_event. > > I've tested the fix, but would be reassured if others could report > > that > > Denemo does indeed now follow links in the Print View when built > > with > > libevview. > > > > Richard > > > > > >
