Wokawidgets Component Suite

Attached is a collection of some of my better projects that are almost complete, POP3 Mail is way off yet, maybe in a week or so.

The suite as components for the following things:

• Custom Tooltips
• Skinning A Form
• Application LiveUpdate (AutoUpdate)
• SysTray Icon
• API Timer
• Aynchronous Download From Web
• MSN Messenger Client
• Simple, but very effective, multipurpose graph
• Simple Selector Control. Very Handy.
• Winsock in a DLL
• XP Button
• MSN Messenger Style Popup Messages
• POP3 Email

More descriptions to come.

Woof

I always keep things simple (for my sake).
So I -
- don't use MDI Forms
- Always have all related frm's, bas's etc in the same folder as the vbp
- and I have never used Project groups

What is the impact (difference) when it comes time to -
- make exe
- use P&D
- and anything else that one might encounter with a vbg ?


Thanks for sharing your apps

None really.

I do keep things simple :D
That's why I use a vpg and multiple projcts.

When you come to P&D your app, you just need to make sure that your DLLs are included in the package.

Splitting code off into DLL means that many apps can use the same DLL, and thus the same code.
Ie. If I changed the code behind the vbWinsock dll then my liveupdate, downloder and MSN client, would ALL automatically see the changes made. No need to update 3 applications. Just one.

Woka

Hey Woka, do you have individule DLs for each component project? Say if I just wanted the XP Button
project would you have a link for it somewhere? :D

Quote:

---

Originally Posted by RobDog888

Hey Woka, do you have individule DLs for each component project? Say if I just wanted the XP Button
project would you have a link for it somewhere? :D

---

That would be very useful I agree :)


Cheers,

RyanJ

hahaha...you both ganging up on me to cause me more work? :p

Yea...I keep meaning to. Working on a few more "little" projects and getting other projects up to release level, then I will add them here.

My component suite now consists of 18 seperate components.

Woka

Just thought it would be easier for me to use if I only wanted XP Button for example and not all the msn stuff.

When can we expect to see individule DLs for each component? :lol:

Errr...you can still use the XP Button on it's own.
Just copy the vbButton project.

Or do you mean you don't want to download it all when all you need is the XP Button project?

Woka

Yes, I was hoping for individule DLs so I dont have to DL all the projects, just the ones I want/need.

Newbie Question
I am using MS Visual Studio 2003 for my projects. How do I use the Wokawidgets examples?

Tom

You don't.
These are written in VB6 not .NET
You would have to convert them, but I'm not sure how well they would convert :(

Woka

Hi,
I'm trying to use some of your great projects like MSN stype popups, systray and skinning.

It seems that when I have a visible skinned form, the MSN stype popups can't be correctly clicked (they are clickable and sticky) and they will not automatically close after being clicked.

If I keep the skinned form invisible, everything goes well.

Any idea? :confused:

Many thanks,
C!

Hmmm...Interesting...:confused:

Will have a look at that.

Woka

Quote:

---

Originally Posted by RobDog888

Hey Woka, do you have individule DLs for each component project? Say if I just wanted the XP Button
project would you have a link for it somewhere? :D

---

Yea...just to clarify, they are all seperate projects, and thus seperate DLLs/OCXs.
They are just all zipped up in one folder for ease of downloading.
Or did you mean have a seperate thread on VBF for each project?

Woka

Quote:

---

Originally Posted by _Ci_

It seems that when I have a visible skinned form, the MSN stype popups can't be correctly clicked (they are clickable and sticky) and they will not automatically close after being clicked.

If I keep the skinned form invisible, everything goes well.

---

I couldn't replicate this :(
Did you find the problem?

WOka

Brillaint work, I love these and even better now they are seperated!

Cheers and thanks for this great component set!

Cheers,

RyanJ

Quote:

---

Originally Posted by Wokawidget

I couldn't replicate this :(
Did you find the problem?

WOka

---

No, I don't!

Honestly it does not happen all the time, sometimes when you click on the popup link it works, sometimes it doesn't (but if you just keep clicking it might work).

Cheers,
_Ci_

Hi, I was wondering if there was a way to use the Live Update on an FTP server, I have tried it basically out of teh box but it trys to use html protocol. Thanks for any help that anybody can give.

-Ian

Sorry to drag out old thread!
I don't really get the POP3 demo! Is it now fully completed??? (The POP3 Section)

What do i do?
This is the error:
Private WithEvents mobjMSN As MSNMessenger
User-Defined Type Not Defined
???

U need to add the MSNMessenger.vbp to your project. U are trying to run the UI, but it has no ref as to what MSNMessenger is.
Alternatively you can compile MSNMessenger.vbp to MSNMessenger.dll, and then in your UI app click project--->references, then select MSGMessenger dll.

WOka

Great work on the XP Buttons. :wave:
Been waiting3yrs for that...

Have you the same for optionbutton and checkboxes?
I use them in pic mode, so they look like a button, but act like optionbutton and checkboxes, and of course doesnt show in XP style

:lol: :cry:

Cheers.
It isn't 100% my code.
I took the code from a button that did way more stuff, like MAC look and feel.
I rewrote the code slightly, stripped out all the crap, like MAC look and feel :)

Woka

Quote:

---

Originally Posted by Wokawidget

U need to add the MSNMessenger.vbp to your project. U are trying to run the UI, but it has no ref as to what MSNMessenger is.
Alternatively you can compile MSNMessenger.vbp to MSNMessenger.dll, and then in your UI app click project--->references, then select MSGMessenger dll.

WOka

---

Argh it doesnt matter, still doesnt work. anyway i did a full client, standalone, portable and powerful with Delphi. no DLLs, or anything and its about 300kb.
Delphi Owns VB, but i still like VB. Delphi is complicated.

Well explian why it doesn't work and I may be able to help you.
U need a good understanding off how DLLs and windows work, then this becomes dead easy.

Woka

Hmm, is it possible to rip out the XP painting bit and apply to optionbutton and checkboxes?

Or, to make it so the button can stay down. This can at least simulate a checkbox.
With some more work maintaining state even optionbuttons.
:wave:

Oh, I added this

VB Code:

Public Property Let Value(b As Boolean)
    If b = True Then RaiseEvent Click
End Property

It did that originally, but I didn't want the code there, and it was messy, so I simply stripped it out :D
U basically have to add an enum of the modes, then a public property to say what mode the button it in. then just change the draw function.

I would use:

VB Code:

Public Property Let Value(ByVal Value As Boolean)
    If Value Then 
        RaiseEvent Click
    End If
End Property

woka

Quote:

---

just change the draw function

---

You make it sound like it's easy :p
I looked but duno how the code works, I dun even know XP shading works!

BTW, I found it draws in XP even on W2K!? How come? I thought u have to use the XP theme/colors which of course W2k doesn't have.
Anyway this becomes a small problem cuz not all my buttons are of this. I think it'd be good to check whether XP themes were enabled or else draw in standard shape. Even XP users sometimes turn themes off! :confused:

Also suggest adding to ImageSizeConstants lv_Full = 5
to display in full size centered.

v.small/v.large images don't scale well.

It does use XP theme...:)

It's draws the button manually using API commands...
so it will look xp on all OS's regardless of the theme used.

Woka

OK, I guess this means there's no way to switch it on/off by code for various OSs?

not a chance...unless, like I said, you rewrite the Draw function :D

Woka

I see. Oh well. I'm thinking aobut using the button state to simulate a pic checkbox. But with timers and stuff going on I'm not sure if its a good idea. Any ideas on potential pitfalls?

I'd like to contend that cback should writeproperty to Parent.BackColor. vb's button also defaults to Parent.BackColor and doesn't write the value unless it changes.

I'd say the same about font, but it seems complicated and I don't know how to incorporate it.

No pitfalls that I can see.

The rest of that post I didn't understasnd, sry :(

Woka

vbxpbuttons works great,
Question: Can I use this ocx in a shareware application.
Thanks,
Jack44

yup. go for your life.
glad you like it.

Woka

hi Wokaidgets, I've tried your XP Buttons control and I liked so much.
My question is, do you think it will work on other Windows versions than XP? (98, Vista, etc)

Thanks.

Not sure about 98, but Vista yes.

The XP button code was taken from someone else project on the web.
I tidied to the code up, and trimmed out all the other stuff I didn't want. So cannot take full credit for that. I thought I put a message to the persons code in my 1st link. Damn bad woka.

Woka

thx 1st for your great work!

but I don't like all dll staff, so why i can't integrate "Asynchronous Web Download.vbg " into a single project?

would you like to help ?

when I put all file in that vbg into one project, IDE told me that "sckClosed " may be dim twice:

i can find both in "Socket.cls" and "clsSocket.cls"

is there any way to solve that?

thanks!

Quote:

---

''The Socket state's constants as for
''the MS Winsock Control interface
Public Enum StateConstants
sckClosed = 0
sckOpen
sckListening
sckConnectionPending
sckResolvingHost
sckHostResolved
sckConnecting
sckConnected
sckClosing
sckError
End Enum

---

the codes is very well
thank you !