Jump to content

herd

Developers
  • Content Count

    980
  • Joined

  • Last visited

Everything posted by herd

  1. Very good idea. Lets hack it together on github in an open-source manner!
  2. This is rather unlikely, because the website is heavily scripted and does not seem to offer XML-Services. I'd rather try another option if I was you. hth, herd
  3. Just download the ObjectDock docklet SDK from StarDock and implement their interfaces. They are pretty straightforward. That's the way it worked in both AveDesk and RocketDock, if I remember correctly. Since you are going to host C/C++ libraries in .Net, you'll need to catch up reading lots of InterOp (No COM/ActiveX involved, just plain LoadLibrary/GetProcAddress stuff in the Win32 SDK), and forget about going 64-bits. Perhaps a mixed C++/C# assembly will do. good luck, herd
  4. These are linker errors. You'll need to link with user32.dll, too.
  5. Hey Andy, they look excellent. Mail them to me (see your inbox at this board). best regards, herd
  6. Hello Andy, well as said before I can no longer fix it, I can only guess at a queue problem: The docklet works as a recorder and digitizes audio. I have done my best to discard audio samples that I can't render, but maybe buffers holding audio data stay allocated, so that several hours of recording leaks enough memory to destabilize a faulty driver - who knows? If the audio stack crashed, a move/delete of the docklet won't help but a reboot will. Try to use a smaller sample rate (e.g. 8 kHz) in the settings. Of course I'm interested, show us the skin... hth, herd At the note: We both
  7. Hi, good idea indeed. Given the low resolution of netbooks, perhaps fitting two pages is not the best idea: Consider rotating one page 90°s and let the user hold the lightweight netbook like a real book... If it's really going to be cross platform, starting with the Linux version and cross-compiling from there on would be better route to go, like pidgin, gimp and inkscape already do.
  8. Are you doing multiple threads? COM is very stubborn with threading. If not, it still needs to have someone poll the window procedures so that its SendMessage based marshaller can operate...
  9. Just about time. Anything that comes in zeroes and ones can be processed on anything that has the ability to process said zeroes and ones. Everywhere, every time. It's pure arbitrariness that Job's mob can get away with bundling hardware to software, that's soo nineties now
  10. DragDetect simplifies matonga's code somewhat. You'll still need to handle mousemove. However, not every click stays on the same pixel, so there is a margin of error tweaked at the control panel to tell a wobbly click from a real drag attempt or a wobbly double-click. DragDetect will take care of that by asking GetSystemMetrics for the width and height of the drag rectangle, monitor if the mouse stays inside this wobbliness allowance rectangle (for any amount of time) and (if I remember correctly) consume the mouseup event to return FALSE in both of these cases. Once the mouse leaves this re
  11. There is also an API call named DragDetect, for calling in mousedown. hth, herd
  12. ... meanwhile the smirking penguin waddles on to world domination, wearing a double-axe under its wing as well as a calculating expression around its beak ... The titans are ready to fall. Deeply, indeed.
  13. Best way to learn: Get a used analog SLR camera, e.g. a Nikon FT-2. Pluck in 400 ASA film, turn off all automatics, no flash and go. Take notes of which settings you used with each exposure. You'll soon pick up tricks that puts the automatics on any DSLR to shame!
  14. Rotate & TranslateTransform don't rotate the pixels, but the coordinate system. Its like moving the paper before drawing normally. So, translate first to picture.width/2 height/2, then rotate, then draw. hth, herd
  15. The core is lean and mean already since its a *BSD... What we'll witness is some liposuction in the app domain. And I doubt that iPhone and iOtherHardware share a lot of OS code, it's more like the ratio between Windows CE to Windows XP, where the API is similar but not identical. I mean, what use would be multitouch to an iMac?
  16. Well its more than time for another Star Trek serie - until then, the repeats will do. PS: I'm not a Trekkie, I'm a free man. And lots of love for 'the' Doctor.
  17. Good luck with your docklet. Always a pleasure to be here.
  18. Whoa lots of stuff. I'd wildly guess that the repetitiveness is of some problem here. Firstly, does your docklet run in AveDesk or RKLauncher? These two are compatible implementations where you can test this erratic behaviour against. Secondly, whats the point in loading the same image(s) every second again? Load them once in onCreate and combine them later, maybe this gets you on the right track. I'm sure you need to catch up some reading on MSDN: MsgWaitForMultipleObjects, RaiseEvent, EnterCriticalSection and PostMessage APIs are there for a purpose. I read somewhere that GDIPlus (be it
  19. On first glance, you are doing something very dangerous: You create a thread and dispose it in regular intervals. Windows does not like this at all, especially during system bootup where some speed optimizations let apps run in an environment that is not completely set-up. Do a proper worker thread that keeps alive for the life-time of the docklet instead. Also, all UI must be done from within the creation thread, calling DockletWhatEver functions from a non-UI thread is asking for trouble. By all means, create the image in the worker thread, send a WM_USER + X message back
  20. Asking for IE8 to be based on FF is like asking for Windows 7 to be based on *BSD. Only Apple could do that. like in: 'Only Nixon could go to China.' (Mr. Spock)
  21. I'd rather suggest turning off the computer while reading a book on the subject (at a public library) or doing real-world talking to someone who is knowledgeable but not too far away from yourself. From your mates, best kind of learning is.
  22. Yes exactly... MFC is a nice shortcut to getting things done; it will turn WM_INITDIALOG into OnInitDialog and cast the w/lParams for you. Override OnPaint instead of WM_PAINT but be aware that there is the old C-Style underneath -- If you know C++ to the template level, maybe diving into ATL/WTL is more of your liking than MFC.
  23. Read even more MSDN case WM_INITDIALOG: is where you create your controls, give one of 'em the focus and never be called again. Load the Image there but keep it as a member variable of DOCKLET_DATA. Create a child window, e.g. a label with a nice border. Open a new case WM_PAINT: for doing the actual drawing; graphics(hDlg) will likely fail - a dialog resource is definitely not a device context. hth, herd
  24. Manipulation of PNGs under XP/C++ is best achieved with the GdiPlus library available at the MSDN. You'll need recent platform SDK headers for the transparency stuff if you stick to VC++6, but not newer than 2002 since the library format changed. If you go the VC++7/8/9 way, MFC should contain everything you need for displaying Alpha blended windows.
×
×
  • Create New...