forum.vdsworld.com

Garrett · Posted: Sun Sep 28, 2003 2:56 am Post subject:

I only found one issue... Not bug, just issue.

When starting new programs, if they previously had the top and left
coordinates under the appbar area, the system does not push the new
window out in the open.

Basically, if have an appbar at the top, it's 21 pixels high, the desktop
has been pushed down, open windows have been pushed down, great.
But if I run a new program, and if it opens to 1,1 then it shows up
underneath the appbar.

Do you understand what I'm saying?

-Garrett

CodeScript · Posted: Sun Sep 28, 2003 11:07 am Post subject:

Hi Garett
Yes I did look into it. I think you are talking about a ontop bar on the top screen edge and the title bar of the new window(unless maximized) can get underneath the app bar and you can't contol that window now without access to it's title bar. I think this is the behaviour of windows itself, even XP Sad

EDIT:
No ....
I checked the normal windows tool bars they check if a window title bar is hidden underneath and push it down. I will try if it is possible inside the dll without subclassing like thing (which I don't want as errors will certainly bring in crashes). Else it can be acheived in VDS itself I think.

BTW:
Appbar start,<window class name>,<position> actually has a additional undocumented parameter messsge number i.e
Appbar start,<window class name>,<position>,<messsge number>
You can specify a custom message number and use option msgevent. This is untested and entirely at users risk.

FreezingFire · **Admin Team** Joined: 23 Jun 2002 Posts: 3508

This whole appbar thing does not work for me. Crying or Very sad

If I could see the source of the DSU or something I might be able to
fix it but nothing happens when I click "create". Sad

CodeScript · Posted: Sun Sep 28, 2003 3:32 pm Post subject:

Garett:
Probably the best way to tackle this is using:
A custom message number (WM_USER+Number)
NB: WM_USER = $400
and option msgevent

FreezingFire · **Admin Team** Joined: 23 Jun 2002 Posts: 3508

It could be that the VB runtime is missing because I never checked
that. I figured it would make an error.

FreezingFire · **Admin Team** Joined: 23 Jun 2002 Posts: 3508

One thing though, in the INI file, it talks about phone-dialing DLLs.
I'm a bit confused.

CodeScript · Posted: Sun Sep 28, 2003 5:37 pm Post subject:

No I am sorry for the oversight It is the same list template taken from a phonedialer dll I wrote for VDS. Correct name of the dll is as that of the dll itself. Anyway that requirement has been overcome and any name for the dll will work but you need to register them manually if you chnge the name that's all.
BTW if you want to dial phone using mscomm32.ocx you can look at the sample on my homepage in DLL section. VDS sometimes throws false errors so I have not yet posted it here.
Did the dll work ?
such errors are likely due to copy/paste and I cannot dedicate that much freetime that I can always write everything afresh Sad

.
I am sad to see that being posted in red letters.
I will rectify that error tommorow. I don't think it's a big bug after all.
I was thinking of interfacing XP explorer bar (common file tasks bar on the left) in VDS using activex. But now I have decided otherwise.
FF if you are still concerned Sad

I will give you the complete source. PM me.

Regards

FreezingFire · **Admin Team** Joined: 23 Jun 2002 Posts: 3508

Sorry if I hurt you by posting it in red letters. I was just trying to
point it out.

I'm not concerned. But I was just wondering what a phonedialer
DLL had to do with this.

Keep up the good work. Very Happy

I have to download the VB6 runtime.

Again, sorry if I hurt you.

Garrett · Posted: Sun Sep 28, 2003 7:45 pm Post subject:

Codescript, thanks for checking into this for me. I'm going to take a look
at trying a couple of idea's. I think this will work out fine Smile

-Garrett

LiquidCode · Posted: Mon Sep 29, 2003 12:45 am Post subject:

Me too. I have been wanting this for a while. Great job! Smile