Results for "Author: vesa piittinen"
This is a Collection replacement, limiting itself to objects. This is mostly a usable "technology demo", showcasing how to create a feature full syntax compatible replacement of a Collection. By speed this class only competes in a few areas, being much slower in adding new items for an example. Maybe someone takes this over and makes a syntax compatible version that is much faster. **** Features: Add, Clear, Clone, Count, Index, IndexByPtr, Item, ItemByIndex, ItemByKey, ItemByPtr, Items, Key, KeyByPtr, Keys, Ptrs, Remove, RemoveByIndex, RemoveByKey, RemoveByPtr, Swap, SwapByIndex, SwapByKey and SwapByPtr. As you can guess by this listing of features, you can do a whole lot more than you can do with the native Collection (which only has Add, Count, Item and Remove). **** Based on SelfEnum class posted yesterday. Credits to Paul Caton and LaVolpe for their work on SelfCallback.
By a request here, I was fooling around with different ways of changing a form's caption to Unicode. I've seen commercial controls that take over the drawing routine with some heavy subclassing and other similar poor attempts, which have then broken, if not when theme changes, then by when Vista got released. I started off by figuring out a way to create a custom Unicode window and then make an existing form a child of it, but this got pretty messy and I wasn't very happy with the complexity. However, I had a bug during this process that I by mistake used a non-Unicode version of DefWindowProc, which prevented the caption to be Unicode. And it didn't take me long to figure out that by temporarily changing a window's window procedure any window caption can be made Unicode. So here it is: a very short and clean way to have an Unicode caption in your forms! The code can be pasted directly to your form.
This single class file gives you tons of power in handling the messagebox: you can change the texts in the buttons, you can set the window's icon, you can set the icon shown besides the message and all the the text is understood in Unicode so no more question marks. If you're an advanced coder you can use the provided interface to do practically whatever you like to the message box window! **** Again thanks to Paul Caton and LaVolpe for their work on SelfSub, SelfHook and SelfCallback.
A new class implementation of Winsock API. By style close to the native Winsock control and other class implementations such as CSocket and CSocketMaster, so you don't need to learn or rewrite much of existing code. The new and cool part about this class is that it is just one class file. Also, it performs better (by speed) and handles errors a bit more cleanly (you aren't forced to close the socket each time an error occurs). Other speciality is transparent Unicode support: when you switch to text mode, you start receiving TextArrival event instead of DataArrival and start getting individual lines. These lines are automatically Unicode if received line is UTF-8 or UTF-16! ANSI lines require you to use StrConv to get an usable string, thus you have the power on what to do with the raw data before any conversion has affected it. **** Support thread and documentation: http://www.vbforums.com/showthread.php?t=534580 **** Special thanks to Paul Caton and LaVolpe for their work on SelfSub, SelfHook and SelfCallback. **** UPDATE 2008-08-12: Now Vista compatible!
It is hard to get Unicode in VB6. The biggest reason is the nowhere-to-be-found support in any of the native controls. In the past few years people have been mostly forced to commercial solutions or to move to another language. With UniControls I try to change this by providing some of the most essential tools for working with Unicode. **** This is the summer release. What you find here are a few powerful controls, and some that are still in an earlier level of development, yet useful for many tasks. Included: UniCaption, UniCommand, UniDialog, UniLabel, UniList, UniMenu & UniText, with some additional bonus code. **** NOTE: despite these controls using SelfSub, SelfHook and SelfCallback by Paul Caton and LaVolpe, not all of these controls are Stop button safe. This is because of UserControl's limited OLE interface, which has forced to some IOleInActivePlaceObject hacking, for which there currently is no perfectly IDE safe solution. If I didn't use it, I would have to use complex hooking to capture Enter, Escape, Tabulator, arrow keys and other navigation keys. **** Hopefully you enjoy these controls!