Author Topic: GlassPrompt 1.1 (Read 29,326 times)

f0dder · « **Reply #25 on:** September 19, 2010, 04:03 PM »

Decent article, Eóin - a funny little thing from it, though:

Quote

If you look at the details of the process from within Process Explorer, you’ll notice that the ComSpec is set to cmd.exe, a clear indication that it’s hosting the command prompt.

Oh really? I thought that was just the standard system environment variable that you'll see in every process

MilesAhead · « **Reply #26 on:** September 19, 2010, 06:32 PM »

Quote from: f0dder on September 19, 2010, 01:55 PM

I definitely prefer to use .rc files when doing simple-ish GUIs for ligthweight C++ apps. Once you need anything fancy (like auto-resizing), you're better off using some framework...

Thanks for the ResEdit link

In this Code Project article he provides skeleton code for a dialog app using the editor:

http://www.codeproject.com/KB/cpp/resedit.aspx?msg=3102372

Although it would have been a tad more useful if he showed adding your own icon as the application icon as that's the more common case then sticking it in a picture box.

Stoic Joker · « **Reply #27 on:** September 19, 2010, 07:25 PM »

Quote from: MilesAhead on September 19, 2010, 06:32 PM

Although it would have been a tad more useful if he showed adding your own icon as the application icon as that's the more common case then sticking it in a picture box.

Perhaps he followed the MSVS resource editors behavior a bit too closely, as I've always found it to be a bit of a PITA for much the same reason.

f0dder · « **Reply #28 on:** September 19, 2010, 07:32 PM »

Adding your application as the application icon? Simple - define it as the first icon in the resource file

(or rather, the icon with the lowest identifier number; usually you use 100, but afaik anything goes, as long as it's the lowest). I think it's actually the shell (explorer.exe) that chooses to show the lowest icon number, rather than having anything to do with the resource editor or compiler.

Eóin · « **Reply #29 on:** September 19, 2010, 07:35 PM »

I believe the application's icon has is simply the first icon in it's resources, so actually he did set the custom icon as the app one.

[edit] oops too late.

MilesAhead · « **Reply #30 on:** September 19, 2010, 07:36 PM »

Quote from: Stoic Joker on September 19, 2010, 07:25 PM

Quote from: MilesAhead on September 19, 2010, 06:32 PM
Although it would have been a tad more useful if he showed adding your own icon as the application icon as that's the more common case then sticking it in a picture box.

Perhaps he followed the MSVS resource editors behavior a bit too closely, as I've always found it to be a bit of a PITA for much the same reason.

Heh. As soon as I wrote that it prompted me to look at his one liner for setting the dialog icon again. I got it to work by using the same trick MS programmers do in the win32 template. Copy hInstance given in WinMain to the global hInst. Then just use MAKEINTRESOURCE macro for my custom icon id. More elegant than the use of LoadImage as shown in the MSDN example.

Instead of his init dialog line
SetClassLongPtr(hDlg, GCLP_HICON, (long)LoadIcon(0, IDI_APPLICATION));

I just used
SetClassLongPtr(hDlg, GCLP_HICON, (long)LoadIcon(hInst, MAKEINTRESOURCE(IDI_ICON)));

bah... I hate making all the newb mistakes all over again though. Not linking with MT switch and getting dll dependency booby trapped all over again!!

But at least it's a way of doing stand-alone exe with a gui editor that emits pretty small code for small utils.

MilesAhead · « **Reply #31 on:** September 19, 2010, 07:46 PM »

Quote from: f0dder on September 19, 2010, 07:32 PM

Adding your application as the application icon? Simple - define it as the first icon in the resource file (or rather, the icon with the lowest identifier number; usually you use 100, but afaik anything goes, as long as it's the lowest). I think it's actually the shell (explorer.exe) that chooses to show the lowest icon number, rather than having anything to do with the resource editor or compiler.

That works fine with standard win32 apps. No joy in this probably because the win32 template where all the icon handles are set is not used.

f0dder · « **Reply #32 on:** September 19, 2010, 07:50 PM »

Oh, you mean the "upper-left-corner" icon rather than what's shown in explorer? Yeah, that requires code.

MilesAhead · « **Reply #33 on:** September 19, 2010, 07:55 PM »

Quote from: Eóin on September 19, 2010, 03:59 PM

Quote from: MilesAhead on September 15, 2010, 09:37 PM
In Windows Seven it shows up easily. They must have improved the scrollbar draw when it's glass.

Indeed they did! This was why it didn't work pre Win7.

Interesting link. I'm not a habitual console drag dropper(I saw an article saying how great VistaSwitcher was so I hit Alt-Tab only to find I already had it installed... guess I don't Atl-Tab much) but I did notice a lot of griping about it when Vista first came on the scene.

MilesAhead · « **Reply #34 on:** September 19, 2010, 08:04 PM »

Quote from: f0dder on September 19, 2010, 07:50 PM

Oh, you mean the "upper-left-corner" icon rather than what's shown in explorer? Yeah, that requires code.

The way he did it was pretty neat though. I can recall using LoadImage in Delphi similar to how MS suggests. Delphi let you assign icons to custom controls, but if you made an ActiveX control out of them, you had to kludge it yourself to get the custom icon to display a design time icon when dropped on a form. But I'll say one thing for the Delphi 5 wizard created ActiveX. If it installed in the IDE it worked as expected. Usually the biggest headache was getting the thing to stay in the toolbox.

Author Topic: GlassPrompt 1.1 (Read 29,326 times)

f0dder

Re: GlassPrompt 1.1

MilesAhead

Re: GlassPrompt 1.1

Stoic Joker

Re: GlassPrompt 1.1

f0dder

Re: GlassPrompt 1.1

Eóin

Re: GlassPrompt 1.1

MilesAhead

Re: GlassPrompt 1.1

MilesAhead

Re: GlassPrompt 1.1

f0dder

Re: GlassPrompt 1.1

MilesAhead

Re: GlassPrompt 1.1

MilesAhead

Re: GlassPrompt 1.1