30 replies to this topic

[DataLife]

1. actually, when the program starts, it checks the registry and saves the settings in variables,

when you select quit, the program apply the saved settings, then exits.

 

2. Its very weird that "mode con" doesnt work...

try this command manually: "mode con:cols=80 lines=300", thats suppose to change the window's maximum size..

----------end quote------------

It changes the window to half my screen wide and the height of my screen.

 

I uncommented the line to make it apply the patch everytime the script starts and the prompt shows

con:cols=160 lines =300

The system cannot find the path specified.

 

And when I try to type anything at the dos prompt I get the message box that my system does not support fullscreen.

 

If I apply the patch via the system tray everytime I start the script it works great.

 

Is the script suppose to remember if it has been patched before?

 

I applied the patch and looked at the variable "patched" and it shows "true"

 

I restarted the script and the variable "patched" shows "false"

[DataLife]

I don't see where in the script that it remembers if it is patched or not after a restart.

 

So, I applied the patch then I put

patched = true

at the beginning of the script. Saved the script and restart it.

 

Now it works properly.

[joedf]

ok, sure!

 

it just that by default it uses the "mode con" which is weird, because it doesn't seem to work on your computer...

so i am happy that you can just the script to your needs, making it apply the patch on startup, if you want i could just a

the ability to change the startup settings using a gui and an ini file

 

lol, im working on using the WinAPI method (as suggested by Lexikos) , which should work perfectly, once its completed

[joedf]

DataLife, what is your screen resolution?

 

the problem seems to be in the script, in your case, here?

cmdf := "mode con:cols=" . getscr_w8p(A_ScreenWidth) . " lines=300"

 

?

[DataLife]

W1280 X H800

 

Looking forward to the new version.

 

thanks

[joedf]

So, ive just put together a small update, including the bugfix you wrote.

I'll optimize the bugfix another day

 

hope this satisfies you for now

[joedf]

W1280 X H800

 

Looking forward to the new version.

 

thanks

--------END QUOTE-----------

 

for 1280 px its 160 cols

 

Could you record your screen typing "mode con:cols=160 lines=300" and anything other that produces errors

with screenr so that i could "see" the problems...

[DataLife]

I am using version 2.3 with no changes.

 

I did not apply the patch.

 

http://www.screenr.com/JjC7 typing "mode con:cols=160 lines=300"

 

http://www.screenr.com/LjC7 no patch, pressing alt enter

 

http://www.screenr.com/zjC7 no patch, pressing alt enter

 

When I use the patch and a different hotkey other then alt enter it works perfectly.

 

It just won't work without the patch. It tries to put "mode con:cols=160 lines=300" at the command prompt but the word "mode" is not there. Then when I try to type exit all kinds of weird things happen like a key is stuck.

[joedf]

EDIT: At the Atl+Enter hotkey remove the "~", then try it, if that doesnt work, replace  the "~" with a "$"... hope that works 

 

thats really weird.... I don't get it

 

Im using Autohotkey 1.1.09.02 Unicode 64-bit

 

theres a bug with Screenr, well i think

 

-this is the script with screenr:http://www.screenr.com/FIC7 (Really weird!!)

-this the script with a normal screen recorder: 

 

try to edit the script to send something like "blah mode con....."

try to fix if you can please because, i would have to do testing on

your computer to see why this is happening...

 

otherwise, the script seems to be working fine on my computer...

 

it seems that you can type the command, but it doesnt seem to want to accept the script inputing the command using send...

 

-----------------

so your system is:

screen: 1280x800

windows 7 home premium

UAC turned off

32bit or 64 bit?

 

my system:

screen: 1366x768

 

windows 7 home premium

UAC full on

64 bit

-----------------

 

this is just weird...

 

is it ok that work on a fix for me? pleaasseee, because i don't have access to computer that has the same bug

its ok, if you say no...

thanks!

[DataLife]

I think I have it figured out. There were 2 issues causing problems.
 
 
1. BlockInput
 
--Quote from the help file--
If BlockInput becomes active while the user is holding down keys, it might cause those keys to become "stuck down". This can be avoided by waiting for the keys to be released prior to turning BlockInput on, as in this example:

^!p::
KeyWait Control ; Wait for the key to be released. Use one KeyWait for each of the hotkey's modifiers.
KeyWait Alt 
----------------------------

So I added

KeyWait Enter      
KeyWait Alt

after the Alt Enter hotkey. This explains why it appeared a key was being held down and random weird things were happening when I pressed any keys.
 
2. A timing issue
There needs to be a 500 milliesecond delay before your send commands for cmdf and cmdw.
This explains why it kept putting "con:cols=160 lines=300" instead of "mode con:cols=160 lines=300"
 
After these 2 changes it works very well for Mode Con and Patched.
 
thanks for a great script. I use the dos prompt almost daily and miss the fullscreen mode.

[joedf]

Ahhhh! i thought there was a problem with my hotkey

I didnt know that about blockinput , i guess i should read the

documentation more thoroughly next time...

now it makes so much sense!

but, i didn't know the delay was not long enough... 

 

well, Great Work! finding these problems..

 

ill add the changes in the next version! + more + maybe an option to change

the delay, so people can change it to what works best on their computers.

 

thank you so much for your contribs!

the next major release will use WinAPI to set the console style....

 

next update will be up soon...

[joedf]

Update coming soon!
Version 2.8.0
sorta late  i know...
 
Well since i didnt really get how to do stuctures in Ahk....
i worked around it... I made a custom dll in C (using WinAPI), then made wapper
functions around my dll functions, which calculates the screenbuffer to
Window size ratio... also creates the stuctures for me.
of course, ...now, i think i understood how to make it full in Ahk...
That will maybe come in the late future..
 
Now every everything works great! No more using the "dirty" old
methods. Out with the old, in with the new!
i also added a some new things...including Custom Hotkeys!
I will also add the ability to have multiple Fullscreen Cmds, to
support for example, Multiple monitors, though I may not get the
chance to test it out
 
Cheers!

[joedf]

Version 2.8.0 (2.8c-Dev) Released!
Currently seems stable enough for release...
All files have been packed into a single zip file.

It includes the source, resources, builds, etc...
 
More will come soon?! :D
Regards

[joedf]

New Update!

 

Version 2.8.2
-Stable (Enough) Release
-NEW Feature: Click the Maximize Button of the console window to put it directly in Fullscreen
-Now totally independent: meaning no more using SizeCon.dll
-Small changes, fixes...
 
Download - View Source - Project Page

[joedf]

New Update! V2.8.3

See the first post