Here is a free oscilloscope control for use with IWB (EB).
I have ported over the minimal set of api declares, maybe around 6 of them.
The control has 40 exported functions in total. You can convert the remaining as needed.
Attached is a quick sample.
You should get the entire oscilloscope package from the author's site to get all the documentation and
more examples in various programming languages.
Oscilloscope Home Page (http://www.oscilloscope-lib.com)
screen shot and link for IWB example below:
Thanks Guilect!
That was on my "to do" list for a while but never get to do it.
I own you one. ;D
Great idea Guliect
and i always want make something with OSC.dll.
Screenshot is from VB example if I remember.
But unfortunatly your example dont work on my computer.
errors:
QuoteCompiling...
Scope.eba
No Errors
Linking...
Emergence Linker v1.11 Copyright ÂÃ,© 2006 Ionic Wind Software
Unresolved external __imp_AtOpenLib
Error: Unable to open file C:\PROGRA~1\EBDev\libs\Osc_DLL.lib
Error: Unresolved extern __imp_AtOpenLib
Error: Unresolved extern __imp_ScopeCreate
Error: Unresolved extern __imp_ScopeShow
Error: Unresolved extern __imp_ExternalNext
Error: Unresolved extern __imp_ShowNext
Error: Unresolved extern __imp_ScopeDestroy
Error: Unresolved extern _window_list
Error(s) in linking D:\Scope\Scope.exe
Aurel
Did you create the lib file?
QuoteTools/Create Import Library
LarryMc
Oups sorry no :-\
I never before do this.
Can you little bit explain how i must do this,if you have some time.
Larry this lib is some kind of static library, is'nt?
Ok i crete import lib from oscdll and recive this error:
QuoteCompiling...
Scope.eba
No Errors
Linking...
Emergence Linker v1.11 Copyright ÂÃ,© 2006 Ionic Wind Software
Unresolved external _window_list
Error: Unresolved extern _window_list
Error(s) in linking D:\Scope\Scope.exe
Oh sorry again i compile as console that's the problem.So i compile again as windows and finaly work :)
Aurel
In order to compile a program using the dll you have to create a Import Library.
You create one by clicking on the main IDE menu TOOL and then selecting the Create Import Library option.
A file dialog will open that says Select DLL to Import.
Locate the oscope dll that you are wanting to use.
Click on it just like you were selecting a file to open.
In the build window it will show you what is happening while it builds the library.
The created library will be named the same as the dll except it will end with .lib.
It will be created in your EBDev\Lib directory.
This Import lib is different from a STATIC lib.
A static lib contains all the actual code for subroutines, etc inside the lib file. When you compile your application the required subroutines are copied out of the static lib into you exe.
With an Import lib the lib only contains the addresses of the subroutines in the dll file.
When you compile, your application just puts in code to load the subroutines when they are needed at runtime.
That's why you have to package a dll with your application when you compile it with an import library.
For the OScope demo you are trying to compile you have to have the import lib and the application has to be able to find the dll when you try to run it. The application(and the linker) will look in the directory that the exe is in or it will look in the windows/system32 folder for the dll.
In my button designer I wrote I used both a static lib and an import lib to build it. The import lib was the dll that contains all the predefined shapes.
Hope this helps you out.
LarryMc
I didn't type fast enough. ;D
LarryMc
No problem ;D
Thanks Larry on great explaination!
Hello
Can you please download an new zip file but this file is demaged or broken zip archive.
Thank you
Stephane
The file got corrupted due to hacking at the IW website back in 2010.
I have re-uploaded the scope.zip file.
Zip file works again.