My bad, the log was disabled in release mode. I've uploaded a new build. Can you try it and see what appears in the log? If that doesn't work, can you try another scripting plugin and see if it works? There is DXVolumeControl or the scriptable email plugin included with DesktopX. If none of those two work, then it's probably a problem on your side or DesktopX acting strange... Do you r
Good to hear! I'm waiting for CaptainBeaker to test it on his Vista computer before uploading it on WC. Build 217 is a release build and won't expire, so if you're confident it will work, you can start building and distributing things based on it.
Hopefully last build before releasing it on Wincustomize. It should feel a little bit faster [e digicons]:ninja:[/e]
Great idea! Might be better to check for XP and use WMI only there, since it probably won't work with Windows 7 either.
You need to put your docklets in a subfolder of the DotNetDocklet folder. It doesn't check the standard docklets folder at this time. As for the guid, if you want to create your own .net docklets, you will need to generate new ones. But if you only want to run existing ones or test the samples, you don't need to do anything.
Are you running anything from McFee ? This looks like your antispyware is catching it for some reason. Can you try disabling it and test again? What was the latest working build for you? IIRC using the plugin alone never worked for you, right?
OK, so it's creating the surface and context allright. How come you get null when asking for the context? I forgot to ask you for the crash details (the contents of the crash dialog). Did you extract the new version to a new folder or to the same folder as the old version? Is the dxpack doing the same thing and crashing DesktopX too? If you have a debugger installed on the machine, getting a stack trace would be nice too (if you don't, don't worry about it).
Can you send me the DXCanvas.log file?
Another build is available with a lot of small bugs and a few crashes and leaks fixed. The only new feature is support for % notation with rgb/rgba colors and a few new color definitions.
It's in the WinCustomize library now. Get it here .
New Build with a little bit of logging. See DXCanvas.log in AppData folder if using the widget or the currentTheme folder if using the dxpack (don't forget to copy the DXCanvas dll to your DesktopX SDPlugins folder if using the later!). The problem with stroked text always showing at coordinates (0,0) should be fixed. There is also a slight change with the default text position. If you want to get the old behaviour, set the text baseline to "top" (ctx.textBaseline = "top"). Yo
Mmmh, not good. I'm going to add some logging to the next beta so we can track down that problem. There is an error when creating the cairo surface and context for some reason (and it's strange that it's not crashing, given that this part is done earlier and lacks some error checking... oops [e digicons]:|[/e] )
Sorry for the garbled script (and the edit button is not working [e digicons]X([/e] ). Good job on the widget. Looking forward for a version using the canvas [e digicons]:-"[/e]
Hey CaptainBeaker! A little bit of feedback: creating a file at the root folder isn't really nice (plus you might not have the rights to do it anyway). It might be better to put that file in the temp directory. You can get it with the following script: [code="vbscript"] Dim tempFolder Set WshShell = CreateObject("WScript.Shell") tempFolder = WshShell.ExpandEnvironmentStrings("%temp%") [/code] you can probably save the whole file creation a
I haven't had time to look further into that problem yet. I'm using Vista myself and it works fine here. I included a dxpack in the latest build in case you want to take a look. Good work on the scripts. Are you working on a widget already? I'm going to publish another test build soon as there is a problem with stroked text in the current public build (fixed internally).
New (almost final) build. Flickering should be reduced a bit (I'm no longer asking for redraw every time an operation is done on the canvas). Error handling is also much closer to the canvas spec now (use debugMode if you want to get an error on invalid parameters). I'll try to see if I can fix the damn flickering for the final version, but otherwise this build should be what will be uploaded on WinCustomize. Let me know if you find any showstopper bugs! On my todo list f
This part is DX-specific [e digicons]}:)[/e]
loadImage returns an object reference, so you need to use Set . This should work: [code="vbscript"] Sub Load_and_Show Dim ctx Dim img set ctx = canvas.getContext("2d") set img = ctx.loadImage("C:\frame.png") ctx.drawImage img, 100,100 End Sub [/code]
A small DesktopX plugin that has been sitting unfinished for 1+ year in my experiments folder... DXDragDropExtended adds true OLE drag&drop to your DesktopX objects. This means you can now drop text onto a DesktopX object in addition to files (ie. select some text in you browser, drop it on a DesktopX object and your script will get called). The API for files is the same as the one already included in DesktopX (Object_OnDropFiles) and you get a new callback DragDrop_O
[quote]Gah...why can't I insert a link? The code button is disabled, grr.[/quote] Select some text... [e digicons]:bebi:[/e]
Huh, strange [e digicons] Can you try to download it again? Extract it in a new folder (ie. not overwriting an old version) and see if it works. I removed some test code (that should not execute when exported as a gadget).
Did you try checking the "reset position" box in preferences?
A little bit better than the version you got... It still defaults to uncompressed video if no FourCC code is specified, but if you have FFDShow you can compress in real time. Which gives you much saner file sizes :)
New build with several bugs fixed (images were not working correctly from VBScript). Finished implementing put/get/createImageData. Check the Edge Detection filter for an example of what is possible.
If you check the "Scripted" option in the animation panel, you get access to the property Object.CurrentFrame. You can then create a loop in your script and check for frame number 56 For i = 0 To 145 Object.CurrentFrame = i If i = 56 Then 'play your sound here End If Next
WinCustomize Forums