Request 1038706 (accepted)

This request supersedes: request 934780 (Show diff)

Overview

Request 1038706 accepted

- New version 8.6.13:
* (new)[TIP 599] Extended build information
* (bug)[440c52] fix PPM/PGM read with graylevel > 255
* (bug)[5fb814] canvas redraw region for lines/polygones
* (new)[631a0b] text widget: direct mouse events to insert mark,
not current
* (bug)[b164ef] fix mouse events for multiple toplevels
* (bug)[be8f5b] crash setting -type empty for a menu
* (bug)[50fc02,50fc02,25894d,156e58] ImgPhoto pointer issues
* (bug)[617861] -justify/-anchor defaults for ttk::label
* (bug)[40bc81] embedding error test failure
* (bug)[b1d115] No event on new toplevel on current
toplevel destruction
* (bug)[3fefb3] crash in empty ttk::combobox when end index requested
* (new)[247d80] Chinese message file
* (bug)[e331bc] NULL to memset in photo blank
* (bug)[864b06] PNG photo image color numeric issue
* (bug)[f75190] tk_fontchooser: multiple font families, locale
change, button activation
* (bug)[ce6b42] (in TCL bug tracker) ttk::spinbox increment event
endless invokation
* (bug)[2a6c62] Avoid invalid <>
* (new)[f47920] Updates to Finnish message catalog
* (bug)[29b5c2] error in tk_popup with separator entry selected
* (bug)[415415] scale advances multiple steps on single click
* (bug)[dc4c55] tk_popup entry index
* (bug)[c0bf1b] XVirtualEvent buffer overflows
* (bug)[eedd79] potential crashes in option parsing when
sizeof(enum) not equal to int
* (bug)[0ce975] panedwindow calls memcpy with NULL pointer

Created by rmax almost 2 years ago
In state accepted
Supersedes 934780

Submit tk

Comments for request 1038706 0
Comments for request 934780 2

Dominique Leuenberger (dimstar) - almost 3 years ago

reviewer

Not a huge fan of this being munged into s changelog from 2018.

Is this some SLE fixup due to forgotten factory first?

Reinhard Max (rmax) - almost 2 years ago

source maintainer

It was fixed in Factory with an upstream update in 2018, but not mentioned in the change log, because it looked unimportant to me at that point in time. Then it got discovered in an older version on SLE and fixed there. Now the bug references needed to go into the Factory package, and I added them to the 2018 entry where the actual fix happened.