PureBasic Forums - English

Thanks

Hi everyone,
I am trying to store a long list of hashes (> 1000) in a DataSection like so:

DataSection
SecretHashes:
Data.s "e92210bf29196ffd45c9f22cfbc0c999c29b8363",
"6673d115a1dafaea51892d9d7328cd09d9919a6c",
"34b24a46f1fc13257c7f4c7e098c294a7418b7c3 ...

Thanks for the replies, I will wait and watch. Just so you know, the x64 pb editor works fine emulated on WinArm64, including ASM and 3D, though 3D can be hit or miss. A native version at some point would be nice.

Hi everyone, I haven't been here for a long time, and "arm" is not a good keyword to search for, so please excuse the question if it has been already answered.

I recently got a Volterra Dev Kit for Win11 on ARM(64) and was wondering whether there were any plans to make a native PB version for that ...

Fred wrote:all the work is done in the DLL

that sounds even better! how would the changes on the c++ side look like?
- does MyUTF8StringReturn return a standard int?
- if so, just cast to char*?

i did that and it seems to work, I just thought i'd ask.

faaantastic! it works now. for future reference, here's the solution I ended up with from back to back:

1. SETTING
- PB compiles to unicode UTF-16 DLL
- program using the DLL accepts only UTF-8, both input and return

2. STRINGS TO PB
- utf-8 input needs to be converted: use PeekS() with the #PB ...

If PureBasic is not displaying its own strings in its own message box properly
PB does display everything correctly in its own message box, as proven by the blue box in the screenshot. in case you are confused by the code snippet i posted earlier: it is missing the debug messagebox and the ...

So, pg_translate() receives the three parameters properly, but the returned string, pg_returnTranslatedString , is garbled?

exactly. step by step:

1. MSVS feeds parameters into pg_translate into the PB DLL
2. pg_translate receives it, does PeekS with utf8, and translates the string: that is ...

make sure that the DLL is receiving the values lc, pc, bl properly
it does. it also translates correctly (blue messagebox below). the error must be in the return:

http://somepic.someserver.de/pics/big/6ce904ba208db3de8853ae6956c8bdac.png

both red underlined strings should be the same.

in ...

thanks for all the help! unfortunately, I have to be difficult as I can't get it to work. since it's no secret what I am working on, i will share some more code.

from the header:
extern "C" {
__declspec(dllimport) int __stdcall pg_init (const char* XMLFOLDER, const char* SCHEME, int VERSION ...

great, that seems to be a step in the right direction. i now override all string-arguments in the procedures with your PeekS-UTF8 tip, and it seems to work: all strings get to the DLL intact.
since i also have strings for return values, i need to do the same thing in reverse, as the output is ...

thanks for your reply!

1. The DLL should be compiled with UNICODE disabled .

uh-oh. that was unexpected. with the unicode flag set, i get this lovely string for a file path:

http://somepic.someserver.de/pics/big/18162f2ae60787713a290af643f857d6.png

if i disable unicode, i get at least the ...

ok, i really think the problem lies in my "const char* parametername". I try to pass a windows file path to my PB-made DLL ("D:\something\somethingelse"), and since backslashes have to be escaped in C/C++ strings, I use ("D:\\something\\somethingelse"). However the DLL does not find the folder ...

i now have
does that look correct to you? it compiles, but for some reason the string i plug into const char* parametername does not appear to get through to the plugin.

hi all,

i made a dll with PB and tested it with PB (OpenLibrary, GetFunction, CallFunctionFast), so i know it works at least in there. Now I want to use the DLL in a MSVSC++12/13 project, however I am not sure how to do this correctly. my steps so far:

- Properties>Linker>General>Additional ...