![Delphi-PRAXiS [en]](https://en.delphipraxis.net/uploads/monthly_2018_12/logo.png.be76d93fcd709295cb24de51900e5888.png){kind=logo}
rvk
-
Content Count
168 -
Joined
-
Last visited
-
Days Won
3
Everything posted by rvk
-
Why should I try it???? But alright... I tried and it works. With this source file Test <div id=content> Some other content </div> <script type = "text/JavaScript"> document.getElementById("content").innerHTML = "Changed content"; </script> I got this in Delphi for var d: OleVariant; begin d := WebBrowser1.Document; Memo1.Lines.Text := d.documentElement.outerHTML; end; <HTML><HEAD></HEAD> <BODY>Test <DIV id=content>Changed content</DIV> <SCRIPT type=text/JavaScript> document.getElementById("content").innerHTML = "Changed content"; </SCRIPT> </BODY></HTML> Note the "Changed content" between the divs of id=content !! The javascript itself obviously stays there because it's part of the source but the content itself is the way it is represented to the end-user after executing the javascript. The DOM even places the missing HTML, HEAD and BODY tags in there.
-
Shouldn't this be possible with just TWebBrowser? Look at https://stackoverflow.com/a/22518562/1037511 So its seems like OuterHtml should give you the rendered HTML. Make sure to get this after the document is completed loading.
-
If you can put together an example and the virtual channels work the same on RDP on win10, I can take a look. I take it this should do the same as TSScan and RemoteDesktopTwain but then directly from your own local utility program.
-
Ah. But it does not not crap out There is definitely some alignment problem. You say "RDS" DLL. How is that DLL different? Is there something done with the calls? Could you share the code? Maybe if that problem is fixed, the other method with ttmNative is fixed automatically too.
-
Then there still could be some other type mismatches in there. Did you also try the TransferMode := ttmMemory; method already?
-
So the call gives a TWRC_XFERDONE (successful) but the handle could still be invalid. The handle (hNative) is a TW_UINT32 (which is a Cardinal/32bit). I wonder if it shouldn't be a TW_Handle (which should be a NativeUInt and UInt64 on 64 bit). At least GlobalLock expects a THandle (which is UInt64 on 64 bit). Doesn't seem really wise to stuff a handle in an Cardinal/32bit on 64 bit (which like David already mentioned, could be just a simple 32/64 bit truncation error). Strange this worked locally on the machine itself but fails on RDP. Maybe the handle-numbers are much larger and it fails.
-
Are your connecting client, the used mstsc.exe and RDP-session (including your app) ALL 64 bit? (If not, you can't rely on the Virtual Channel Client DLL) Did you check the numerical value of hNative (i.e. not being 0)?
-
So, the drivers are not loaded on the server itself? I'm not familiar with Virtual Channels in RDP, but I think this would mean you have the DLL on the local client and want the application, which runs on the server side in RDP, have access to the local scanner through the Virtual Channels-technology? Just like a Redirected Printer uses Virtual Channels. That's a whole lot of places where things can go wrong (that's why I asked if the scanner and drivers and DLL where locally on the server side in the RDP session itself). What was the value of the return-code on this line (in TTwainSource.TransferImages for TransferMode ttmNative): rc := Owner.TwainProc(AppInfo, @Structure, DG_IMAGE, DAT_IMAGENATIVEXFER, MSG_GET, @hNative); That seems to be where hNative gets its value (which fails). It seems the value is not checked for success there ( if rc <> TWRC_SUCCESS then ... should give error )
-
YIKES. $474/year for a Code signing certificate ????? Shouldn't be any more than $100/Year or so via some Sectigo reseller. Examples here and here. You'll need a Code signing certificate ("SSL" EV won't do and I've never needed an EV Code certificate). I also never seen the icon disappear. What tool do you use to sign and what command line options?
-
Are you using a redirected scanner in WTS? Or is the scanner-software (and 64bit driver) directly installed on the WTS machine? Does the DelphiTwainDemo2 example work in WTS? Not sure what you mean by this? In Windows Terminal Services (now called Remote Desktop Services, RDS) you also just run plain applications, don't you? Or do you mean it's running under Windows Services? (which is hugely different)
-
Hard to say what could be the cause without example-source of DLL and calling procedure.
-
On 64 bit it worked for me but I did't have any scan-sources. WIA sources are 32-bit and not visible in 64 bit for me. Installing the VueScan gave me a 64 bit source. What Delphi version do you use? Are you using VLC of FMX? Did you try the DelphiTwain\examples\VCL2\DelphiTwainDemo2 example? (which worked for me on 64 bit)
-
So you provided a "bad value" Here it works fine with VueScan as 64 bit scan-sourcedriver. What/which scannerdriver did you try/use?
-
But that's how we recognize the administrators 😁 (although that information is also under the avatar-hoover.) I find that information useful to see in one glance. Hovering over the avatar hides it too much for me. +1 for the other suggestions although I wonder how much the layout can be changed from the default via themes (because this is based on standard forumsoftware). Ah well, there is always greasemonkey
