Hi, everybody!
Please look at my code a little:
The problem is the variable "DroppedImage". I checked its value, it is:
Image: "C:\a.jpg
That's everything, I do not know where the rest part is. Someone help me, please. Thanks!
I am using DesktopX 3.1 on Windows XP SP3 32 bit.
I haven't the foggiest. But I sent sViz a PM for you. She can sort anything out. She's real good at this stuff!
I used your script as is, and it worked fine. Where are you showing the DroppedImage message? Are you using a message box, or...?
Hi Eve....knew I'd see you here...
The lengths a guy has to go to just to see his .
lol...Howdy Jim Still keeping up the good work with DX, I see.
Oh, thank you, RedneckDude and sViz!
You say my code works fine? I have problem with DroppedImage variable, just look at the screenshot http://imageshack.us/photo/my-images/844/unleddvi.png/. That variable does not show the whole string as expected, it shows a part of the expected string only. I do not know why? Please help me. I hope you understand what I say. Thanks, waiting for your reply...
Strange, the code is fine. I'm on Vista and DX 3.5. You may need a later version, but I shouldn't think that would affect it. Seems everything after the second Chr(34) is cut off; can't say I know what the problem is. A long time ago, iirc, someone once said to use spaces between the "&"s , instead of everything running together. Wish I remember where I read that. Have you tried it without the quotation characters? Also, do you need the message; does it apply the picture to the object without any problems? Oftentimes, when I run into oddities like this, I'll simply remove them from the equation.
I think this is a bug on DesktopX 3.1. About my situation: I want to get the path of the image dropped onto current object as a parameter in a string to be processed later. And the value of that string will be the beginning of that string and the image path only, the rest part of that string will be cut off, regardless what it is, that is the problem. My code was just an illustration for that bug, no more. Now, I move to DesktopX 3.5, my code works without that bug any more. Love DesktopX forever!
Thanks a lot for your help, sViz. Good time!
Glad everything's working for you. Happy DXing
There are many great features available to you once you register, including:
Sign in or Create Account
