Ok, the bug has been fixed. Turns out calling setFocus() on a combo will actually reset the text entry to the previous entry, so I had to save it prior to that call and set it back on the combo after that call. There's a lot of workarounds for various OS-strangeness in the CalendarCombo already, so this isn't exactly "new".
In any case, I committed the changes to CVS, nightly build should pick it up, otherwise just check it out and apply to your current code. Let me know if you run into anything else, Regards, Emil On Fri, Apr 18, 2008 at 9:35 PM, B. Haje <[EMAIL PROTECTED]> wrote: > Hi, > > I'm just trying to use the CalendarCombo widget, which by the way seems to > be a pretty good piece of work, but I'm experiencing a problem, after > using > the setDate() method. > > Usually I can use the combo-field to enter a date directly, without using > the popup. The entered date gets used after the popup afterwards and can > be > read using getDate(). If I use setDate() before, that doesn't work any > more. > The widget always uses the date which was set via setDate() - as long as I > use the popup to select an other date, but I can't enter it directly. > > Do I have to specify a listener to the changing of the combo or something? > > Thanks for your help > > Bjoern > > _______________________________________________ > nebula-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/nebula-dev > -- Emil Crumhorn - [EMAIL PROTECTED] Senior Software Engineer http://www.hexapixel.com/
_______________________________________________ nebula-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/nebula-dev
