SkinBrowser Plugin

[nintwala]

Originally Posted by Zorro

Yes there is a way for 2.0, not for 1.4x, which makes it impossible right now to add this feature.
I will move all my plugins to 2.0 soon (which means 1.4x will not be supported anymore).

Is it possible to check for the CF version information in the code? So, if its 2.0 or above, it will do some method to disable gestures. If not, it will ignore it.

[Zorro]

Originally Posted by malaki86

Now - can ya come up with one to disable my screensaver & display power management while the vehicle is in motion? Or even just disable it while CF is running?

Nope.

[Zorro]

Originally Posted by nintwala

Is it possible to check for the CF version information in the code? So, if its 2.0 or above, it will do some method to disable gestures. If not, it will ignore it.

Don't you think, if there was a way I would have done it in first place?

[nintwala]

Originally Posted by Zorro

Don't you think, if there was a way I would have done it in first place?

I shouldn't have doubted the mighty Zorro.

My apologies.

[MarcelP]

Thanks Zorro, great work!

[Zerach]

Originally Posted by Zorro

Don't you think, if there was a way I would have done it in first place?

Whoah! Was that a cranky day or does your ego need a little whittling?

Let me provide the code to do so...it's not at all as clean as I'd like it but it does the job.

Your going to have to port the few lines from Delphi.net to your language of choice...

Plugin_Init
...
DLLVersion:=Test.LoadFrom('C:\Program Files (x86)\Flux Media\Centrafuse\cfplugin.dll').GetName.Version.major.ToString;

Test.free \\we really don't need this anymore, free up some memory

\\DLLVersion is a string Test is Class System.Reflection.Assembly  I use major version you could use version.minor as well for future bulids
...

Plugin_Show
...
    if DLLVersion = '2' then
    Begin
     CF_SetGraffitiRecognition(False);
    End;
...


//Then create an close button action to CF_SetGraffitiRecognition(True)

Plugin_Close
...
    if DLLVersion = '2' then
    Begin
     CF_SetGraffitiRecognition(True);
    End;

Think this will do what you want it do, works for me.

[Zorro]

Originally Posted by Zerach

Whoah! Was that a cranky day or does your ego need a little whittling?
Think this will do what you want it do, works for me.

Neither the one nor the other.
As .NET loads the plugin it'll check the existance of the methods used against the referenced assemblies and since the graffiti methods don't exist in 1.47 it'll raise an Thread exception and the whole plugin becomes "invalid".

[nintwala]

Once everyone and everything is switched over to CF 2.0 everything will be A-OK.

No need to stress over my silly issue. I have patience... I think somewhere... I just have to find it.

[Zerach]

Originally Posted by Zorro

Neither the one nor the other.
As .NET loads the plugin it'll check the existance of the methods used against the referenced assemblies and since the graffiti methods don't exist in 1.47 it'll raise an Thread exception and the whole plugin becomes "invalid".

Ahh I see...I thought you were saying you could not turn off grafitti. I did not check the lower CF plugin out.

You could always go with a simple solution and build 2 different dll's one for 1.47 and one for 2.0. You could even go farther and create a dll which checks the CFPlugin.dll version and then loads the correct assembly for your dll in plugininit and executes the correct procedures.

I'm going to have to try a few things out now, got me curious

Once everyone and everything is switched over to CF 2.0 everything will be A-OK.

No need to stress over my silly issue. I have patience... I think somewhere... I just have to find it. Yesterday 02:32 AM

Oh pish posh....stoking the fires for debate in the name of one up-manship is what makes life worth living....programming worth doing and competition worth competing in.

No Harm no foul, no ones stressing...at least I hope not

[nintwala]

hmmm.... pish posh.... Its been a very long time since I have heard that term.