Adrian Holovaty wrote: > Oooh, that's a good idea. Django already displays the __repr__() of > the corresponding record on the *change* page, but it'd be nice to do > it automatically (via Ajax) right after the field is populated on the > add page (or changed on the change page).
Yup... I noticed this bug, too. This was on my "list of small bugs that I need to fix and submit patches for". :-) Don't forget also... if the pop up selector is used to select the code, it should update the __repr__ *and* the code displayed in the form. Right now, it updates the selected, but does update the __repr__ until the page is saved... It's quite confusing. -jason
