SL Baur <steve(a)xemacs.org> writes:
>> How much time do you need? Personally, DND is more
important to me
>> than MS Windows support, and I'm already prepared to slide the schedule
>> further to allow more MS Windows changes in.
> Currently coding. Perhaps I can get a working new version for drops
> only until this evening.
Cool!
[Just for the others waiting]
> I have eleminated the special events. The x_event_to_emacs_event
now
> generates a misc-user-event with dragdrop_drop_dispatch as function
> and a (TYPE . DATA) cons as object. This can be displayed (inserted,
> etc.) by this function. I'm now adding the needed button information
> to the misc_user_event. I hope this will not break anything.
> There are actually two ways to do this:
> a) hardcode them into the misc_user and make the event-x, event-button,
> etc. function recognize this (the easy way).
> b) add it to the eval-object and create the necessary functions to convert
> this information to frame/buffer/point information.
> Personally I prefer a), because rewriting all the internal pixel to whatever
> translation seems not the right way.
> Any comments?
None from me, I'm probably not the right person to ask though. I
trust your better judgement on this.
Then I will give off another comment (and but this into xemacs-beta...):
b) would also be possible, if I call all necessary functions (event-window,
event-point, event-closest-point) while creating the misc-user-event and then
putting the returned data also into the misc-user object.
But for me a) is still the best (?) solution. Will it break something? I think
not.
Regards,
Oliver.