On 12/3/12, looncraz <looncraz@xxxxxxxxxxx> wrote: > It's trying to make a call into fAccSetCursorBitmap when it is in fact > NULL... I missed it because I tried it on real hardware with > fAccSetCursorBitmap actually present. That no longer crashes and generally seems to work better as far as the cursor itself is concerned...however, now I'm observing a different problem...whenever I pass a spot that causes a cursor shape change, that area isn't properly repainted once the cursor moves away again, leaving a dirty image of the cursor shape at that spot (i.e. if the mouse passes over a splitter and the cursor correspondingly changes to a resize indicator and back, the spot where it shifted to a resize indicator has a ghost of the latter remaining until repaint). Regards, Rene