-
Notifications
You must be signed in to change notification settings - Fork 181
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WinCon, endwin() kills QuickEdit/InsertMode options and more.. #148
Comments
They should all be restored, yes, and are, in my experience. (And I did recheck, just now.) What version of Windows are you seeing this with? |
Hmm. That made me think.
I am using Win7 x64 for the most part, and it is definitively not working there, but, I also
checked my Win10 and Win11 machines and sure enough, it does there...
Given that we depend on JB's using an undoc function, I guess this won't be easily fixed..
*sigh*
Thanks anyway!
Fred
On Sunday, July 9, 2023 at 06:25:40 PM EDT, William McBrine ***@***.***> wrote:
They should all be restored, yes, and are, in my experience. (And I did recheck, just now.) What version of Windows are you seeing this with?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Sorry, what's "JB"? |
/* Wrapper around WM_SETCONSOLEINFO. We need to create the necessary
section (file-mapping) object in the context of the process which
owns the console, before posting the message. Originally by JB. */
On Sunday, July 9, 2023 at 07:30:49 PM EDT, William McBrine ***@***.***> wrote:
Sorry, what's "JB"?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
OK. To be clear, it also works on XP, for me. Usually, if something works on both XP and 11, I'll assume it works on the versions in between. But I'm not set up to test with 7. |
Oh. Yeah, didnt try XP yet, but if you say that does work.. mmm.
Win7 being weird?
Let me know if there's anything I can do to help.
(I use VMs for pretty much all variants of Windows, macOS x64 and most mainstream Linux)
|
So, I set up a Windows 7 x64 VM to test, and -- as I expected -- I don't see the behavior you describe there, either. It's something else about your system. |
Hi:
So, I set up a Windows 7 x64 VM to test, and -- as I expected -- I don't see the behavior you describe there, either.
It's something else about your system.
I did the same here just now.
Results: installing retail MS Win7 SP1 x64 *works*
installing Dell OEM Win7 SP1 x64 results in the behavior I see.
So, their image (and/or any of the later patches they installed) seems to have messed with this.
At any rate, that is not a PDCurses bug, so we can close #148.
Thanks for checking into it!
Fred
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Hi:
Using 3.9 on Windows Console.
All works fine, however, after application closes, it leaves the console window
with its QuickEdit and InsertMode options disabled, and it zapped the 'Screen Buffer' size to 'Window Size'.
Although I can see why the screen buffer size would be reset (while PDcurses is running), I do not see a good reason for dropping those two options. Plus - should these (all) not be restored to "previous" on close?
The text was updated successfully, but these errors were encountered: