Hey guys,
After going through the discussion, I think I am confused about the actual
requirements from the project.
Clearly there is some problem with the current logger, but I think the
requirements which are mentioned on the FreeType's GSoC page and the
requirements which are discussed being
I have attached the diff of my implementation. I have handled the SC_SIZE
message
and resize the window manually in a non blocking way.
Anuj
changes.diff
Description: Binary data
Alexei Podtelezhnikov wrote:
> Dmitry,
> > It probably needs adding CS_HREDRAW | CS_VREDRAW to ourClass.style.
>
> That was not enough.
I'll try to find time and have a look at it.
--
Dmitry.
> Is that true? Handling WM_SIZING alone was not enough.
No, simply handling WM_SIZING or WM_SIZE is not enough in the current
scenario.
There is a separate system message SC_SIZE under the WM_SYSCOMMAND
(https://docs.microsoft.com/en-us/windows/win32/menurc/wm-syscommand) which
is
posted when
Dmitry,
> It probably needs adding CS_HREDRAW | CS_VREDRAW to ourClass.style.
That was not enough.
Anuj,
> The window enters a modal loop whenever you start resizing the window, the
> loop terminates when the mouse is released.
Yes and I have read that during the look WM_SIZING and WM_NCPAINT
Anuj Verma wrote:
> The window enters a modal loop whenever you start resizing the window, the
> loop terminates when the mouse is released.
> more on this here:
> https://docs.microsoft.com/en-us/windows/win32/winmsg/wm-entersizemove
> So I think the solution would be to handle the
The window enters a modal loop whenever you start resizing the window, the
loop terminates when the mouse is released.
more on this here:
https://docs.microsoft.com/en-us/windows/win32/winmsg/wm-entersizemove
So I think the solution would be to handle the "WM_SYSCOMMAND" message and
manually
