Hey there,

hm, I don't know ... try using the latest Framework / Jabaco.jar from here:
http://www.jabaco.org/wiki/Latest_JabacoFramework_Binary

make sure you replace your

'C:\Program Files (x86)\Jabaco\Jabaco.jar'

with the new one.

I am curious, why did you add 'Jabaco-REV105.jar' to your Imports?
A standard SDI Projects Imports looks like this...



Dani

Quoted from "swissmade"

I have some funny problem.
When I try to edit the Color with the Colorpicker of a form the GUI crash.
When I edit some lines GUI Crash

Hmmm... thats not funny. Seems that there are some problems with the native part of Jabaco.
I don't know much about the COM-interface in Windows and so on.
So, this seems not to be a problem with the Java-part of Jabaco.

Quoted

Reinstall Jabaco won't help.

Hmmm... hard to say it: I think a reinstall of Windows could help.


But before you reinstall the operating system, try if it helps to remove Jabaco rev 105 from your packages. Don't know, if dupolicated frameworks makes problems for the IDE.
What is, if you create a completly new Jabaco-SDI-application, without integrating the other packages? Crashes it then, too?

Quoted

Rev105 I add because of some classes missing in the others.

Rev 105 have no class, which isn't in Rev 126.
But Rev 126 have additional VB/JBCellEditor$CheckBox.class
Because it is only a subclass of VB/JBCellEditor.class you can say, that of counting the classes, between Rev 105 and Rev 126 is no difference.

Quoted

Also I miss some Classes.

You have all classes. They have only new names.
You have started your project with the old original framework. All classes in Jabaco.jar are automatical loaded. When you saved your project, all loaded classes are written in the project-files. And when you replace the old framework with a new one and load the old project, then it can't find the renamed classes. But they are already again loaded, because they are in Jabaco.jar.

To the files:

• VBA/JabacoEventQueque
  Was renamed by OlimilO in Rev 51 on October 11, 2009 to VBA/JabacoEventQueue.
  Reason: Manuel have written the english word "queue" wrong, OlimilO have corrected it.
  
• VBA/FileSystem
  I renamed the package-path in Rev 57 on March 15, 2010 from VBA to VB.
  Reason: I know, that in VB6 FileSystem is in VBA, but this was the only file, which is written in Jabaco, the source is in VB, but it compiled to VBA.
  After that change, in VBA are only Java-sources and binaries created with the Java-compiler and in VB are only Jabaco-sources and binaries created with the Jabaco-compiler.
  
• VBA/VBFileAccess, VBA/VBFileLock, VBA/VBFileMode
  All three are enums in FileSystem. And so they are compiled in the same package, in which FileSystem is compiled. So with the change from VBA/FileSystem to VB/FileSystem, this three files moves to the VB-package, too.

Greatings
theuserbl

Hey there,

I tried everything ... I can not get the editor to crash

hmmm, did you try to register every *.dll and *.ocx manually?!

Other than that, I don't know, sorry...


Dani