PureBasic Forums - English

Once again mesozorn, thanks.

This is a big help for my current project and means my users can stop faffing around cut and pasting text into a word document.

All i've got to do now is understand how you did it :)

No trouble and glad to help. Outlook messages are served by the windows drag-drop ...

Is there any way to drag and drop the just the meassage? maybe as .msg

Well, this took me all mother-flipping day to get right, and I haven't exactly tested it extensively, but it seems to work correctly for dropping any number of emails from Outlook, with or without attachments, and saving those ...

sorry to bump this thread.

I can't get the code to run as it complains that the #PB_Label constant is already declared.

I can comment it out and the code runs, but doesn't do what it's supposed to, so i debuged the value of #PB_label and it returns 56 so is this affecting the code ??

I don't ...

Well, possibly the best work-around for the button is to use a ButtonImageGadget().

That may in fact still be the most viable option, since PB 5.2 still does not natively provide for easily colouring ButtonGadgets, and the PureCOLOR library has the quirk that I mentioned regarding vertical ...

I'm sure we can help but we need to know the exact POLINK error reported. Usually it is either because the lib version does not match the PB version or the sub-system has not been input (e.g. UserLibUnicodeThreadSafe) or that subsystem is incompatible with another PB setting.

Note that PB5.xx has ...

I have used PureCOLOR in the past successfully, however presently I'm trying to use the correct version with PB 4.60, and am getting a PO Linker error upon compile. Any advice or guidance?

The key is the '*this' structure; it is unique for each control that you register for drops with RegisterDragDrop_(WindowID(#Window), *this). This is the 'class template' for the interface and whilst the interface is unique for all iDropTarget objects, the class template need not be and can contain ...

I am not sure what you mean? Are you wishing to get some information on the drag source?

No, but rather the drop target itself. Suppose I create three different controls, and I register them all with the same iDropTarget interface like so:

RegisterDragDrop_(hWND1, *this)
RegisterDragDrop_(hWND2 ...

Glad you got it all working. :)

One other question.. is it all all possible/easy from within the IDropTarget interface to detect the calling window that has activated said interface in any given instance? Normally when sub-classing a window the standard way, the custom WindowProc will report as ...

Okay, here is the complete working version which will successfully accept and handle a Drag-and-Drop of one or more files from either the regular windows filesystem, or as attachments to email messages in Outlook (non-express). Feel free to point out any bugs and I'll update the code with a fix ...

The first argument points to a buffer into which the data will be placed. The second argument is the size of the buffer in bytes. The 3rd parameter is the address of a variable which will receive the actual number of bytes read. You can pass 0 for this last parameter.

Ah right thanks okay I see ...

Well, I am almost the whole way there and just one step away from saving the Outlook attachment data to a file on disk. The last stumbling block is how to invoke the READ operation on the iStream data object.

In regular WinAPI the function istream_read() is implemented as an independent function ...

I notice that if I do:


Structure one
a.l
b.l
EndStructure

Structure two
c.l
d.one[0]
EndStructure

e.two\d[7]\a=55



...It does not throw an "Array Index Out of Bounds" error, even though I've specified zero elements in the static array yet am assigning a value to element number 7. But if ...

Ah okay I see, thanks... to me "memory handle" sounds extremely similar to "memory address/pointer" and the MSDN documentation under StgMedium doesn't exactly specify differently, so I was attacking it as such incorrectly. I was also thrown off by the fact that despite my erroneous approach, I was ...

Well, I have made a bit more progress with regular Outlook, but at this point am getting some extremely odd results. I'm sure I'm doing something wrong but cannot for the life of me figure out what.

I am able to detect and successfully process a FileGroupDescriptor and extract it to a StgMedium ...