News:

Masm32 SDK description, downloads and other helpful links
Message to All Guests
NB: Posting URL's See here: Posted URL Change

Main Menu

Console window size

Started by nidud, September 08, 2013, 10:09:49 PM

Previous topic - Next topic

nidud

#15
deleted

dedndave

doesn't do much good without the source   :P

nidud

#17
deleted

GoneFishing

Quote from: nidud on September 22, 2013, 12:04:46 AM

the program: the flag is set in a window,
but if you do Ctrl-Enter to full screen nothing happens

the rest of the functions works...

maybe Alt-Enter ?

dedndave

sorry - i guess i don't understand what you are trying to do

nidud

#20
deleted

dedndave

i never tried using the mouse wheel in a console, before
in a GUI app, you handle WM_MOUSEWHEEL and possibly WM_MOUSEHWHEEL messages
it would seem that the console event trap doesn't do that - no surprise, there
i guess you could subclass the window and handle the messages, passing all other messages to the original window proc

nidud

#22
deleted

dedndave

it is indeed a GUI app
and - the "standard" behaviour of the console mouse is very buggish
one might do well to subclass and disable the console mouse code, anyways - lol

if you want to see one of the bugs i'm talking about....
use the right-click context menu of the console to copy/paste text
the console window will lose track of the current X and Y position of the cursor

nidud

#24
deleted

jj2007

Quote from: nidud on October 04, 2013, 04:56:06 PMis there a simple way to test if the window is active or lurking in the background?

GetForegroundWindow

nidud

#26
deleted

jj2007

Quote from: nidud on October 04, 2013, 06:43:33 PMIn the case of not being active I need to call the GetForegroundWindow() function repeatedly, so how should this be handled?

Should I "sleep" for a while and then call it again?

WM_TIMER is a option. Another one is to check for WM_MOUSEMOVE messages, they are being sent even if the window is not active. But no such messages if you hover over an edit control.

The standard option, though, is monitoring WM_ACTIVATE.


dedndave

even GetForegroundWindow doesn't always work the way you think it should
it's a problem i have fought with in the past
so far, i haven't found a perfect solution

nidud

#29
deleted