 |
|
 |
I long for the days when I could just click-on my TI-994A, see the prompt "TI-Basic Ready", and start having fun. (Remember Parsec?)
This control is very sweet.
I'm wondering what it would take to get it to compile using the .Net 4.0 Client Profile?
Regards,
Chris
|
|
|
|
 |
|
 |
Hi Chris,
I just found this recently: Classic99 Emulator[^]
It really brings back the memories. In also OCR'd some old programs I wrote back in the day and they Worked! It is really cool seeing them working again after so many years.
I am not sure what it will take to get it working with the ClientProfile I may look when I have some time.
SSDiver2112
|
|
|
|
 |
|
 |
Wow, I could really lose myself in that for a while (heh)
Thanks for the link.
Chris
|
|
|
|
 |
|
|
 |
|
 |
Just choose Build Solution.
|
|
|
|
 |
|
 |
I have a fondness for progress controls, perhaps because so many programmers don't bother to add them. You have a clearly written article and a very impressive & flexible progress control. You get a 5 from me.
Just because the code works, it doesn't mean that it is good code.
|
|
|
|
 |
|
 |
Shouldn't I be seeing a .dll file in the extracted files?
Thanks. Looks like a great control.
|
|
|
|
 |
|
 |
Figured it out. Thanks. It is a great control!!
|
|
|
|
 |
|
 |
I Can't find it neither, i hate projects that expects me to compile the project and produce the actual dll.
Plus, before rebuilding the project (when first opened vbproj of test form) i got 105 warnings about declerations and the actual form is not visible in designer using VS 2005.
When you just alone set Value property, nothing happens, it seems "Timer" was used in sample project.
modified on Wednesday, April 27, 2011 6:15 AM
|
|
|
|
 |
|
 |
I am sorry for the trouble you are having, but every project must be compiled to create the dll's.
As stated in the Submission Guidelines for Code Project Articles:
"Sample Project:It is recommended that you also include a sample project. When creating a zip file for the sample project, please do not include either the Debug or the Release directories. They simply inflate the size of the ZIP file. Also, do not include the *.clw, *.ncb, *.opt and other such files that are automatically recreated."
Because of this, the project will not have sufficient information to view forms and such until it is rebuilt and all the supporting files are created.
SSDiver2112
|
|
|
|
 |
|
 |
Stupid question time. This control looks likes the answer I've been looking for; an easy way to do progress bars in Word 2003 VBA.
But, I'm still a bit confused. Looking in the zip, I see no ReadMe telling me how to get the control installed. I'd be ever so grateful if someone could enlighten me.
dedawson
|
|
|
|
 |
|
 |
I'm not really sure how or even if you can. I would suggest doing a search for "add vb.net usercontrol to VBA" or something similar. For simplicity in VBA I have used two labels. One label has a transparent backcolor, border and text. A second label is layered behind the first. Adjust the width of this one to simulate the progress bar. lblBar.Width = currentValue * ((lblBarBack.Width - 2) / maximumValue) Another thing I have done is replace the Label lblBar with an Image control to use a bitmap as the Bar.
SSDiver2112
|
|
|
|
 |
|
 |
I was afraid of that. I'm guessing, that in the .net world, this control gets compiled and can then be employed as an ADDIN. Is there any possibility you might be able to provide such a module (.com, .dll, etc) that I could try loading as such? I only have the VBA that is resident in Office, with no means of doing a .net compile.
thanks in advance,
david
dedawson
|
|
|
|
 |
|
 |
Good control, Nice features. Well thought out.
|
|
|
|
 |
|
 |
i'm using vb express 2008 and I've been so impressed with all the improvements over vb6 that I was using for so long..until I started using the standard progress bar control
i have a couple of apps that use filesearch and I had trouble getting the bar display to accurately reflect the search progress. tried so many things but it wouldn't finish it's display to 100%, and was just inaccurate in general, no matter how many refresh or updates or doevents i tried. just something really wierd going on with thier pbar display lagging behind it's value when dealing with intense processes like filesearch.
so i added your progressbar to my toolbox, set it's look, docked it in place of the standard one, and threw it the same percent value as i had been giving microsoft's p.o.s bar...worked perfect first time out! accurate, good looking, and finished the bar display exactly as expected.
wish i would have found this first instead of messing around so much.
thanks a bunch for your hard work, it's an excellent control and very easy to use.
|
|
|
|
 |
|
 |
This is a controll that I have been looking for for a long time! Excellent work on this one!
|
|
|
|
 |
|
 |
Could someone convert this project to C# please? Or let me know of a progress bar with a percent label on the bar itself.
Pete
|
|
|
|
 |
|
 |
If you just want the control in your project, just add the dll to your toolbox and use it in your C# project. If you need the code then someone will have to convert it.
Scott
|
|
|
|
 |
|
 |
Thanks,
I know I can add the DLL to my project, but I really wanted to have the code in C#. I only need some of the properties of thie control.
Pete
|
|
|
|
 |
|
|
 |
|
 |
Thanks for those sites - I'll check them out later.
Pete
|
|
|
|
 |
|
 |
One useful feature for some types of controls, especially progress bars, is the ability to update them from any thread without blocking the thread doing the update. Using BeginInvoke by itself isn't quite good enough, since it would be possible for thousands of update events to get queued up before the control was refreshed. Using CompareExchange, however, it's possible to add thread safety with minimal difficulty. Something like:
Sub DoUpdate
if NeedsUpdate <> 0 Then
needsUpdate = 0 ' Do at start of update routine
...
End If
End Sub
Sub ReqUpdate
If NeedsUpdate = 0 Then
If Threading.Interlocked.Exchange(NeedsUpdate,1)=0 Then
If InvokeRequired Then
BeginInvoke(DoUpdateDelegate)
Else
DoUpdate
End If
End If
End If
End Sub
You still need to make sure that you store your values in such a way that a refresh that occurs while they are written won't cause problems, but the approach outlined above will work pretty well. It can be improved slightly by adding a timer to limit the maximum update speed, but the key aspect is that a thread can update the progress bar whenever it wants without having to wait, even if the user interface thread is blocked.
|
|
|
|
 |
|
|
 |