[MacPorts] #57925: inkscape: Extension dialog boxes don't stay on top

MacPorts noreply at macports.org
Mon Jan 21 22:53:38 UTC 2019


#57925: inkscape: Extension dialog boxes don't stay on top
-----------------------+----------------------
  Reporter:  fdesar    |      Owner:  dbevans
      Type:  defect    |     Status:  accepted
  Priority:  Normal    |  Milestone:
 Component:  ports     |    Version:  2.5.4
Resolution:            |   Keywords:
      Port:  inkscape  |
-----------------------+----------------------

Comment (by dbevans):

 Testing update:

 After spending some time comparing the behavior of 0.92.3 and 0.92.4
 releases, I was able to get a bit more specific about the symptoms of this
 problem.

 The problem can be demonstrated as follows:

 * open a sample document ( I use the animated clock example distributed
 with inkscape)
 * select an extension to apply (Extension->Color->Black_and_White)
 * at his point, an extension dialog will appear on top of document window
 * the dialog appears in the upper left of document window (should be
 centered on the document)
 * either selecting the document window or applying the extension will
 bring the document window to the foreground with the dialog behind it
 * correct behavior is for the dialog window to stay on top of the document
 window even though the focus has shifted to the document.
 * this assumes that the Windows preference "Dialog on top" (see above)
 has been set to either Normal (default) or Agressive. Inkscape must be
 restarted to make a setting change to be effective.
 * only dialog windows from Extensions or Filters are effected.  For
 instance, the Preferences dialog works as expected in all cases.

 Inkscape 0.92.3 distribution works correctly, Inkscape 0.92.4 does not,
 nor does Inkscape built from the latest 0.92.x maintenance branch
 (inkscape-devel).  inkscape-gtk3-devel built from git master appears to
 work correctly.

 Using git bisect, I was able to track down the offending commit on the
 0.92.x maintenance branch:

 {{{
 f6a0b7f6fcf690a7ffdd6e2237376ad7ead43e7e is the first bad commit
 commit f6a0b7f6fcf690a7ffdd6e2237376ad7ead43e7e
 Author: Jabiertxo Arraiza Cenoz <jtx at jtx.markerlab.es>
 Date:   Thu May 10 19:33:19 2018 +0200

     Backport from trunk 99f25194657838f3bac55c38dc7edde802c9d2b1 Extension
 improvements

 :040000 040000 fca3a32073bf1420d4627ad55647c6daa852d579
 88e0ef0de803fa7cc5d0eee8d3ebf66aefd69fd7 M      src

 }}}

 which certainly has a suspicious sounding name!!  I'm looking now to see
 what exactly in this commit might be causing the problem and why it works
 on master (possibly a fix not back-ported to maintenance, gtk2/3
 differences?).

 Will report after I zero in a bit further.

-- 
Ticket URL: <https://trac.macports.org/ticket/57925#comment:12>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list