Sending pointers with non pointer functions!

[James Tabor]

I see this and I LMFAO!

co_IntSendMessageNoWait(Window->head.h, WM_WINDOWPOSCHANGING, 0,
(LPARAM) WinPos);
co_IntSendMessageNoWait(WinPos.hwnd, WM_WINDOWPOSCHANGED, 0, (LPARAM) &WinPos);
There is more too! Amazing!

Please tell me this is not wrong!!!!
James

[Giannis Adamopoulos]

It's more correct to say, how is it possible that reactos still works with this!
We are lucky that co_IntSendMessageNoWait supports sending messages with pointers to the current thread. However sending a message with co_IntSendMessageNoWait doesn't marshal lparam if the message goes to a different thread.
I'm starting to wonder if r47126 is really correct...

ReactOS Development List [e-mail] wrote on Sat, November 26th, 2011, 11:05 AM:
> I see this and I LMFAO!
>
> co_IntSendMessageNoWait(Window->head.h, WM_WINDOWPOSCHANGING, 0,
> (LPARAM) WinPos);
> co_IntSendMessageNoWait(WinPos.hwnd, WM_WINDOWPOSCHANGED, 0, (LPARAM) &WinPos);
> There is more too! Amazing!
>
> Please tell me this is not wrong!!!!
> James
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev

[James Tabor]

Well, it is no longer is supported in my local tree. I removed the
packing and added is_pointer_message to make sure no pointer based
message is passed to SendMessageCallBack. Remember that memory eating
problem in win32k? Well now it is gone.
James

On Sat, Nov 26, 2011 at 4:40 AM, Giannis Adamopoulos
[e-mail] wrote:
> It's more correct to say, how is it possible that reactos still works with this!
> We are lucky that co_IntSendMessageNoWait supports sending messages with pointers to the current thread. However sending a message with co_IntSendMessageNoWait doesn't marshal lparam if the message goes to a different thread.
> I'm starting to wonder if r47126 is really correct...
>
> ReactOS Development List [e-mail] wrote on Sat, November 26th, 2011, 11:05 AM:
> > I see this and I LMFAO!
> >
> > co_IntSendMessageNoWait(Window->head.h, WM_WINDOWPOSCHANGING, 0,
> > (LPARAM) WinPos);
> > co_IntSendMessageNoWait(WinPos.hwnd, WM_WINDOWPOSCHANGED, 0, (LPARAM) &WinPos);
> > There is more too! Amazing!
> >
> > Please tell me this is not wrong!!!!
> > James
> >
> > Ros-dev mailing list
> > [e-mail]
> > http://www.reactos.org/mailman/listinfo/ros-dev
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev

[Ameen Ross]

bugfix++;
me->cheer();

On 11/26/2011 12:10 PM, James Tabor wrote:
> Well, it is no longer is supported in my local tree. I removed the
> packing and added is_pointer_message to make sure no pointer based
> message is passed to SendMessageCallBack. Remember that memory eating
> problem in win32k? Well now it is gone.
> James
>
> On Sat, Nov 26, 2011 at 4:40 AM, Giannis Adamopoulos
> [e-mail]  wrote:
> > It's more correct to say, how is it possible that reactos still works with this!
> > We are lucky that co_IntSendMessageNoWait supports sending messages with pointers to the current thread. However sending a message with co_IntSendMessageNoWait doesn't marshal lparam if the message goes to a different thread.
> > I'm starting to wonder if r47126 is really correct...
> >
> > ReactOS Development [e-mail]  wrote on Sat, November 26th, 2011, 11:05 AM:
> > > I see this and I LMFAO!
> > >
> > > co_IntSendMessageNoWait(Window->head.h, WM_WINDOWPOSCHANGING, 0,
> > > (LPARAM) WinPos);
> > > co_IntSendMessageNoWait(WinPos.hwnd, WM_WINDOWPOSCHANGED, 0, (LPARAM)&WinPos);
> > > There is more too! Amazing!
> > >
> > > Please tell me this is not wrong!!!!
> > > James
> > >
> > > Ros-dev mailing list
> > > [e-mail]
> > > http://www.reactos.org/mailman/listinfo/ros-dev
> >
> > Ros-dev mailing list
> > [e-mail]
> > http://www.reactos.org/mailman/listinfo/ros-dev
>
> Ros-dev mailing list
> [e-mail]
> http://www.reactos.org/mailman/listinfo/ros-dev