2015-05-15 9:55 GMT+02:00 Nicolai Hess <[email protected]>: > > We now use a new class for the space-key as key combination. fixed and > included in 50045 (https://pharo.fogbugz.com/default.asp?15529) > This way we don't end up with hundreds of obsolete class instances. > > But the problem with circular references still exist. > 15535 <https://pharo.fogbugz.com/default.asp?15535> > break circular reference for keymappings > > I could need some help here, any idea how to work with the key mapping > registration without holding (or how to release) strong references? > > > thanks in advance > nicolai > > Can anyone help me with this. I need a way to break the circular references.
a class is referenced by its compiled method the compiled method is referenced by the method context the method context is reference by a block context (the keymapping action) the block context is referenced by the registration item the registration item is referenced by the pragma registration builder the builder is reference by the method context (it is the method argument) and here the circle closes. > > > 2015-02-20 9:26 GMT+01:00 Marcus Denker <[email protected]>: > >> >> > On 19 Feb 2015, at 10:19, Nicolai Hess <[email protected]> wrote: >> > >> > Fogbugz issue 14936 >> > and slice in inbox >> > >> > After loading this slice, there are still many references to the (now) >> obsolete class KMUntypeableSingleKeyCombination. >> > I tried to remove these references with the following code : >> > >> > NECPreferences popupShowWithShortcut: nil. >> > KMSingleKeyCombination reset. >> > KMSpecialCharSingleKeyCombination reset. >> > KMRepository reset. >> > >> > >> > But they arent removed. >> > >> > Anyone knows how to re-init all users of >> KMUntypeableSingleKeyCombination ? >> > >> > >> >> Very strange… using “explore pointers” with the old inspector, it shows >> lots of instances… I sadly have no >> time to now look deeper, but the pointer explorer should be a way to find >> who holds onto them… >> >> Marcus >> >> >> >> >
