Intermediate
Date of registration: Jan 1st 2009
Location: Hanover, Germany
Occupation: Software Engineer
Hobbies: Hilbert Curves
Jabaco Source |
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 |
Option Explicit Public Form1 As Form1 Public Sub main(ByJava args() As String) Dim laf As String Dim myArgs() As String myArgs = args ' laf = javax#swing#UIManager.getCrossPlatformLookAndFeelClassName() laf = javax#swing#UIManager.getSystemLookAndFeelClassName() ' laf = "com.sun.java.swing.plaf.windows.WindowsLookAndFeel" Debug.Print "laf=" & laf UIManager.setLookAndFeel laf Form1 = New Form1 Form1.SetDefaultClose() Form1.Show() End Sub |
What is the effect of modifying Module1 to something like this?
Quoted
Would this help around WinLAF?
Quoted
Why doesn't the WinLAF problem blow *my* applications?
Source code |
|
1 2 3 |
13.02.2011 18:02 <DIR> jdk1.6.0_23 10.10.2010 16:40 <DIR> jre1.6.0_20 13.02.2011 18:02 <DIR> jre6 |
Intermediate
Date of registration: Jan 1st 2009
Location: Hanover, Germany
Occupation: Software Engineer
Hobbies: Hilbert Curves
Jabaco Source |
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 |
Implements IJabacoClass Public Sub Class_Initialize Call setDefaultLookAndFeel() End Sub Public Sub setDefaultLookAndFeel() setLookAndFeel( getSystemLookAndFeelClassName() ) Dim myOS As String = LCase(SysInfo.OperatingSystem) If InStr(1, myOS, "windows") > 0 Then If SysInfo.SecurityMode = False Then 'If LCase(myOS) <> "windows vista" Then Call net#java#plaf#LookAndFeelPatchManager.initialize() 'End If End If End If End Sub Public Function setJabacoLookAndFeel(v As String) As Boolean Call UIManager.setLookAndFeel(v) SetJabacoLookAndFeel = True End Function Public Function isInitialized() As Boolean isInitialized = True End Function |
Source code |
|
1 |
DesktopProperty(String paramString, Object paramObject, Toolkit paramToolkit) |
It would probably make sense to remove or change the "Call net#java#plaf#LookAndFeelPatchManager.initialize()".
Quoted
The difference between standard L&F and WinLAF is described in the WinLAF files.
Source code |
|
1 |
An alternative repair would be to add the missing 3rd parameter to the instantiation of DesktopProperty() |
Ok, I have no tried myself to rename the old Java-directory. It have no effect. Jabaco works still fine.
But the WinLAF-mysterious go on: I have tried here in an Internetcafé (where I can nearly all install, without to need to deinstall later all) to delete the complete WinLAF-part in Jabaco.jar.
I expected, that Jabaco now will no loger run. But thats not true.
If I create a SDI program and start it, there comes an Jabaco-error window
index.php?page=Attachment&attachmentID=265
But after that, Jabaco runs further on, without any problems!
And I see no difference of the running program with or without WinLAF.
Here a screenshot of a little test program without WinLAF:
index.php?page=Attachment&attachmentID=266
But the Jabaco.jar is without WinLAF more then 100kB smaller then with WinLAF.
Intermediate
Date of registration: Jan 1st 2009
Location: Hanover, Germany
Occupation: Software Engineer
Hobbies: Hilbert Curves
Oh, an additional thread, where the solution isn't posted.I'm curious about a couple things... This NoSuchMethodError rather forced me to be done with Jabaco for a while, since I was hoping to build some utilities, but couldn't have the error popup be part of my compiled app
For future plans of Jabaco have a look at the thread atQuoted
Next a more general question: I notice the jabaco download release is still from 2009... is this project still alive as far as the author(s) are concerned? It appears the community is still active, and I'd like to get involved again, the error popup is a killer for me though...