Console

[oex]

:lol Maybe I'll post it when it's done

[dedndave]

i didn't necessarily need to see the code
i was just wondering why you needed a console window   :P
you can run other app's with CreateProcess or ShellExecute

[oex]

I'll play with it and see if I can work out which bit I'm not understanding.... I have some ideas in how I would get around this it just appears there are more flaws than I first thought than simply changing my compile method and calling AllocConsole.... :lol....

I use both Console and Windows because I have input/display mechanisms for both and would rather not have to recode both right now :lol.... Most of my tools are written for console and translation to Windows controls properly (if indeed I bother) will take some time.... It is an admin app (ie only I use it atm)....

[dedndave]

i was curious because i am working on a project that is along similar lines
but, i am using a window to replace the console   :P
it offers a window that is more tailored for the application than the console
you saw the other post with the hidden window and the visible one, right ?
the hidden window is somewhat analogous to the console app
and the visible one is analogous to the console

[dedndave]

as an example, here is a series of WM_MOUSEWHEEL messages
the values are: sequence number, uMsg, hWnd, wParam, lParam

[oex]

That's a nice project and I see your thinking.... I have similar ambitions for removing the console however they will unlikely be realised in the near-term.... I have written my own basic console already however serveral key features remain missing.... You'd laugh if I showed you which ones (display cough) :lol.... It's a minimalist approach.... simply text entry :lol.... For the time being Windows Console fills that gap :bg....

[dedndave]

well - in this app, i have no need for keyboard entry, although it would be easy to add
i do have the display working pretty much
i have a macro i call "dPrint" which is similar to the masm32 "print" macro
that all works great   :bg
i am almost done with the visible window code - looking at about 13 kb
as opposed to the ~380 kb of cmd.exe

i could have just as well used a console, but i wanted to learn to write GUI apps   :P

[oex]

:lol I also have a >8Kb font somewhere complete with creation tool and editor.... Worked out how to create one in >1Kb also (Probably less than 100 bytes) but never implemented it :bg....

[oex]

I think the 8Kb font is how they draw Courier VGA font

[dedndave]

i was going to do something like that
but, i figured out how to enumerate the regular "Terminal" font that the console uses
i wanted to use it for 2 reasons
1) it has the graphics line symbols that some use for boxes
2) it is monospaced, which greatly simplifies the WM_PAINT code   :P



i eliminated the sizes where the cell width is larger than the cell height - lol

[oex]

i was going to do something like that
but, i figured out how to enumerate the regular "Terminal" font that the console uses
i wanted to use it for 2 reasons
1) it has the graphics line symbols that some use for boxes
2) it is monospaced, which greatly simplifies the WM_PAINT code   :P

:lol dont use that as an excuse.... Mine has an editor to allow you to draw the graphics line symbols and is also monospaced :bg....

It currently has only 12x16 size however :lol

[oex]

[dedndave]

well - there are a couple other advantages to using the Terminal font
it is on every windows machine
there are several sizes already made for you
it doesn't require the data size, which can get large if you make several sizes
a lot of work to make fonts - lol

sent you a PM Peter   :bg

[oex]

a lot of work to make fonts - lol

:lol that is for sure....