Results for "top"

An ASP bar graph. Easily customized and great examples. Customizations include Top Padding, Side Padding, Bar Width, Bar Padding, (Only if bars are in groups.) Group Padding, Number of Groups, Number of Bars Per Group, Maximum Value Values For Each Bar, Colors of Bars, and Titles Of Each Bar! The inputs are all at the top of the code with explanations. Nicely blocked off for your convenience. I have not tested this with Netscape. Please let me know how it does. You can only have a maximum of 18 bars due to restrictions from style properties. This problem is easily breached by using javascript. If you would like that code please email me @ checkerman_1985@yahoo.com

This will put your forms on top. Works good. It uses API calls to do this. Hope it helps you. Also Please visut my site, i got some video tutorials there about visual basic. http://www14.brinkster.com/computerteck/?p254

It can scroll right to left or bottom to top, stop at top or stop centered, scroll and stop or Scroll Continuously and background, text colors & fonts are all customizable. It uses bitblt to do the drawing so its flickerless. This control is a updated version of http://www.Planet-Source-Code.com/vb/scripts/ShowCode.asp?txtCodeId=14967&lngWId=1 that I modified & updated for Almost Real Jukebox.

Hooks END safe now, added Paul's CDECL class to project so we don't lose that one either. Continuing on where Paul Caton left off. Paul has moved on from VB and his thunks are too good to let die. The attached contains a complete revamping of his subclassing thunks and significant enhancements to other thunks. The subclassing thunks, I believe are now 100% IDE-safe. I have even placed END statements inside of the subclass procedure and IDE did not die. The usercontrol (UC) crashes occurring when subclassing parent by multiple UCs is now history too. See the top remarks in cSelfSubHookCallBk_Template for overview. The assembly code is provided in .ASM files and can be opened with notepad. 18Jul07: Minor tweak in subclass.asm to attempt crash on compiled app when END executed. 21Jul07: Believe hook thunks now 100% END safe, added CDECL class allowing one to call C++ APIs or ASM thunks. Workaround for making Hook thunks more END-safe is commented in remarks at top of Template class.

'I developed this code because I have seen many people boasting that their code being 'the one that stays avove all of the other windows .. well I hae never found their 'claim to be true so I wrote this code .... in order to test my code just use any 'yes any stay on top form in the software world and I bet it won't fail ... what more 'it can be on top of even the menu items of the Windows start menu ... jus place the 'form around three inches above start menu and you see the menu items going behind it 'isn't this cool ... 'Just remember me Bis and askbiswa@hotmail.com .... I know now my mailbox is going to 'be flooded with mails for more cool and simple stuff like this .... well I promise 'once I get started I know I will never stop ... so write back soon ... if you like 'it

This project shows how you can add an Intellisense List (like the one in VB where you type an object name, then a "DOT", and then a list pops up -- that's the Intellisense List). Designed to allow you to enter in YOUR SCRIPTING LANGUAGE COMMANDS AND OBJECTS quickly and easily (using an external text file). All efforts were made to make this act exactly as the one in VB does. Press TAB or ENTER to select an item in the list. Clicking TAB immediately automatically selects the first item in the list. You can begin typing the property name and the "closest match" will be highlighted as you type. Backspacing on your typed entry also does the same. Multiple "DOTS" (eg: me.text1.font.) works. Insertion of "DOT" characters in the middle of a string works. Location of intellisense box goes to where it can fit in view (bottom right, bottom left, top right, top left) depending on where your current cursor location is. This project Took me some time troubleshooting, so I hope some of you out there can use this. UPDATED ON AUGUST 9th! Fixed a few unhandled errors, added more comments to help you see what is happening, Wrapped Intellisense core functions into subs for easier include in your projcets, and added the ability for different styles of the Intellisense box (Office XP stlye, VB6 style, and a hybrid style) as many of you have requested.

Simple Win32 API Tic Tac Toe game. Has a total of 24 strategies/blocks incorporated into one function called smart() that works on defense as well as offense. It checks to see what moves have been made and makes it's move accordingly. Better than playing a human for the computer never sleeps. ;) Good example of writing your own functions to perform tasks there are no built in functions for and getting different return values from your function to act accordingly. The boxes are numbered from left to right with the top left box being one. The top row is one to three, middle four to six and bottom seven to nine. Push the button that's number corresponds to the box that you would like to choose. Good example of subclassing child controls and using the template resource editor to create and display dialog boxes. One or two players.

This version of Google Power has automatic top open browser detection for searching individual websites as well as the form staying on top when open.

Have you ever wanted to CLEANLY shutdown an external application that you only had a ProcessID to? I've always wished that there was the equivalent to the TerminateProcess() API that would send the WM_CLOSE message to the application, allowing it to shutdown cleanly, not abruptly as TerminateProcess() does. Because of this, I began a quest to either find such an API or to build one myself... Basically, the only way to successfully shutdown an application who's window title you do not know beforehand on Win95/98 is to use the TerminateProcess() API. WinME seems to correctly process the WM_CLOSE message to its top-level windows, so it can be excluded from this even though according to MSDN it functions the same as Win95/98. Now, use of the TerminateProcess() API is frowned upon because according to the MSDN article http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dllproc/base/terminateprocess.asp : "The TerminateProcess function is used to unconditionally cause a process to exit. Use it only in extreme circumstances. The state of global data maintained by dynamic-link libraries (DLLs) may be compromised if TerminateProcess is used rather than ExitProcess." But... with the use of the WM_ENDSESSION message this downside seems to be obverted, because to this MSDN article http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sysinfo/base/wm_endsession.asp (which is actually for the WM_QUERYENDSESSION message): "Windows 95/98/Me: After all applications return TRUE for this message (WM_QUERYENDSESSION), they receive the WM_ENDSESSION and they are terminated." So if I'm reading that correctly, at shutdown Win95/98 sends the WM_QUERYENDSESSION to all top-level windows, followed by the WM_ENDSESSION then (assuming all applications are happy with the shutdown) they are then terminated assumedly via the TerminateProcess() API! Now this process also occurs at a logoff, so it *should* be reasonable to assume that all of the downsides of the use of the TerminateProcess() API are solved by first sending the window the WM_ENDSESSION and a True in the wParam argument because the application is *supposed* to clean up after itself when it receives the WM_ENDSESSION message. In my research, I found a number of sites concerning the incorrect handling of the WM_ENDSESSION by Delphi applications. They advised their developers to hook the message and fully close their apps (destroy objects, etc) at that time in order to avoid any errors. So as long as I've not missed any important nuances, I believe that with the help of Ark's comment I've stumbled across the answer to my question! So in order to put this into a nice little package, I've implemented the fabled CloseProcess() API I used to wish for... As always… if you find a bug please let me know. Thanks and enjoy!

PLEASE Vote for me!!!!! Magic Windows ver 1.0 Have you ever wanted to have a form that would slide out from behind another form, like a tray? Well now you can. Simply Drop this control onto a form(the one you will use as the tray) and from anywhere in code you call 2 methods. One will Slide the form out, The other retracts the form back. You can set the "tray" form to slide out to the right, left, top. or bottom. You can set it to slide out on top of the calling form, or behind the calling form.

Updated: Metric Grid Scale and Landscape capable. If you hate writing VB code to create printed forms, give this a try. Print Form Code Generator lets you create forms by dropping text boxes, pictures and line on a form and generate the VB print code to paste in your program. This is the first version and it can only get better. Feedback is welcome. To move lines, click to move a point shift + click to move the line ctrl + click to move point left and right only alt + click to move point up and down only shift+ctrl+click moves other point's top position to clicked point's top position shift+alt+click moves other point's left position to clicked point's left position New Version: Select paper size, and line ghosts gone!!

This is an add-in for adding resizing capabilities to your projects. It is based on the add-in "4 mode Resizer" by PeYTaN (you can find it on http://www.Planet-Source-Code.com/vb/scripts/ShowCode.asp?txtCodeId=46731&lngWId=1) which is based on the class ControlResizer by Edward Catchpole (you can find it on http://www.planet-source-code.com/vb/scripts/ShowCode.asp?txtCodeId=46203&lngWId=1) The (GREAT!!) combined work of the two authors spared me *a lot* of coding time, still I had some complex forms on which i wanted to optimize the resizing to the last twip, and the available modes weren't always enough for me. So I ended up extending both the class and the add-in to support anchoring and resizing a control with regard to another control, not just to the form. I also added a small demo project that (I hope!) gives the idea of the various and complex arrangements you can achieve by combining the available modes; just resize the two example forms at will and see how the controls behave. These are the enhancements: 1. More freedom Someone commented on the original class that it had the flaw to reserve tag usage for itself, whereas the developer may want to use control tags for their own purposes. This version is tag-friendly: it doesn't replace the previously designed tag, it appends the designed tag after the resizing data and a custom separator. When the form is loaded and the class initialized, the resizing data are retrieved from the tags and stored in an internal array; the originally designed tags are then restored and no longer needed by the class, as the resizing code will work on the array. 2. More speed Cycling on the internal array, which only stores info for the controls that will be resized, is faster than cycling everytime on the whole array of form controls, in case at least some controls won't need resizing. Besides, the original class used to set the 4 properties (Left Top Width and Height) separately; this version calculates them all and touches the control only once, via the Move method. (A SetWindowPos API call might be even faster, in case you want to try it) 3. More options The new modes allow you to anchor a control to another, so that the gap between those controls stays constant, whereas it grows if both controls grow and move proportionally. A control can now be aligned to another control (Left, Right, Top and Bottom), stretched (Width, Height) to align its right or bottom edge to the latter, or stretched to the same size (Width, Height) of the latter. Relating a control to another requires that the latter has already been resized, but the modified class takes care of it by sorting the data after assigning a priority to each control, requiring no extra effort from the developer. Filling and sorting the array will marginally impact on the form startup time, but as said the runtime resizing tends to be faster. 4. More bugs? Most likely, as there's more code! (I had noticed no bugs in the previous version, just a lacking feature in handling arrays of controls, now properly dealt with) So if you find any, please inform me so that they can be fixed; even better if you send me a fixed version yourself ;)

I was inspired by Clint's vcTrayAlert Control at http://vbasic.iscool.net/ It was cool but he did not make the source code available. So I decided to write my very own control. Along the way I have added many cool features. I have used a gradient-drawing class that I found on PSC by Kath-Rock. I made a help file for my control and as you will easily figure out, I have invested alot of my spare time into this large project. It is made free but make sure to check out the license agreement and copyright info. All I'd like to ask you is your encouragement - IF you DO like my control. So I'll be waiting for your feedbacks and emails :) Oh, I'd like to ask you for one more thing. Help me debug this control, report any bugs you might find to me on my email addres. Thanx. KEYWORDS: MSN Style Tray Alert Control, ActiveX Control, User Control, Play WAVE WAV File Resource, Always On Top, Top Most, Transparency, Transparent, Fade, Mask, Borders, Gradient, Error Handling.

Set your form 'Always On Top' - > On Top of other windows.

This is the simplest code ever for always on top, if you find anything simpler (which i doubt) let me know!

Add special effect to your form when it is showing and hiding! 6 types of effects can be applied. They are roll left to right, roll right to left, roll top to bottom, roll bottom to top, expand window outward and fade window. This program shows how to add these fancy effects. Make sure you have Windows 2000 and later or Windows 98 and later running before running this program. The program is well commented and a tutorial is included. Your comments and votes is the way you repay me for my work.

This "thing" takes advantage of a thoughtless mistake on microsoft's part. This prog can stay on top of anything, even the task manager! PLEASE VOTE! -Note: I used code from Jan Alexanders Transparent form to achieve the flashing effect

A desk top shooter game

I'm not sure sure if it's just my computer but, for some reason, my VB programs never stay on top of other windows all the time when I use the SetWindowPos API. This program still uses the SetWindowPos API but I added some stuff to make it work properly.

get and change numlock ,capslock, scrllock and insert key state using system tray (Add and remove) using self start with windows using transparent layer using read and write registry get screen workarea with SystemParametersInfo and adjust form left and top with a Taskbar Visual Moving a Window Without a Titlebar always Keeping a Window On Top