Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - moises1953

Pages: [1]
1
QB64 Discussion / Deployment of application with DLL in Windows 10 in v2.0.1
« on: October 31, 2021, 07:19:37 am »
Search for DLLs in development and deployment:

In version 1.4 you could declare a DLL simply by name and place it at the executable address, in system32, or at a specified address.

In later versions the IDE has been denying the compilation if the executable is not in QB64, even though the option has been chosen to locate the executables with the sources, and these outside of QB64, which does not seem to be correct.
This is the wiki text: The dynamic library file can be located in the QB64 folder (alongside your programs' .EXE '), in Windows' system32 folder, or in a relative / absolute path specified along with the library name
The consequences that this has in the deployment of an application with DDL's, is that it can no longer be located with the executable, but it can be done:
1. in a QB64 folder, which will have to be created, even if it is not necessary.
2. in system32
3. in a predefined address, for example C: \ AppName, for which it will be necessary to have the same path in the development environment.

Could it be a bug in the IDE?

2
QB64 Discussion / Deployment of application with DLL in Windows 10
« on: May 22, 2021, 02:25:42 am »
Use and deployment of external DLL's in QB64 version 1.4:
The DECLARE DYNAMIC LIBRARY ["DLL name1", "DLL name2", ...] instruction allows the use of any type of dynamic library, both in Windows (DLL) and in Linux (SO), as long as it is declared below the call structure with the correct data types. For example (Windows):
DECLARE DYNAMIC LIBRARY "kernel32"
  FUNCTION GetThreadUILanguage% ()
  FUNCTION LCIDToLocaleName% (BYVAL LCID &, lcidName $, BYVAL length%, BYVAL dwFlags ~ &)
  FUNCTION GetUserDefaultLocaleName% (pwsLocale $, BYVAL LocaleLength%)
END DECLARE

These language functions are in the Windows 'kernel32' module, but since they have not been used by QB64, they need to be declared, as well as the call structure of the functions to use.
To use a library from a provider, it should be enough to copy it to the application folder, and call it by its name, without more, for example:
DECLARE DYNAMIC LIBRARY "NmxDLLx64"
 SUB NMX_GetDllVersion_1 (usMajor ~%, usMinor ~%, usPatch ~%, usBuild ~%)

Unfortunately, if it is only in the application folder, the IDE cannot find it and therefore does not allow it to be compiled, so it is necessary to copy it to system32 for the IDE to find it. On the other hand, the use of a relative location address such as ". \ NmxDLLx64" makes it work when compiling, but not when deploying the application, since the absolute address is resolved at compile time and makes the application not find the DLL in its own folder, but instead looks for the address where it was located when it was compiled.
For the generated executable to be able to use an external library with a simple name declaration, it must be located in C: \ windows \ system32 or in the same folder as the application, and this is sufficient for most cases, But for the IDE to find it and allow compiling, it must be in system32, however the generated executable will look for it in the application folder itself, so it will be enough to copy the application and the DLL together.
In my opinion it is necesary to make the IDE look like the executable.

3
QB64 Discussion / Deployment of application with DLL in Windows 10
« on: March 18, 2021, 03:42:33 am »
Environment:
64-bit Windows 10 version 2004 PC. 64-bit QB64 is installed, and a dynamic library named NmxDLLx64.DLL is added, which as its name indicates is 64-bit, in the same folder as the executable.
A program is created that uses the library without problem, even if it is copied to another folder
Library declaration
DECLARE DYNAMIC LIBRARY ". \ NmxDLLx64"

Laptop with Windows 10 version 1909 64-bit. Do not have QB64 installed.

Tests:
1) Copy program and DLL to laptop and run. Result: Cannot find the DLL (popup with message: 'Cannot find dynamic library file'.
2) Install QB64 on laptop. Copy the source of the program and compile it. Then the program works correctly.
3) Copy the executable again from the PC and run. The message box not found message appears again.
4) Create on the PC a path equal to the destination of the laptop where I want to install the application and its DLL. Compile it there. Copy it to the laptop and now it works.
5) One last test: Rename the folder where the executable and the DLL are located and it stops working

Conclusion:
The load address of the DLL is resolved in the compilation and linking process, from unit level.
Therefore, to deploy the application with its DLL, it must be copied to the same address relative to the computer that it was occupying when it was compiled.

¿There is another option?

4
QB64 Discussion / Flush File Buffers
« on: August 01, 2020, 02:59:00 am »
Windows has a FlushFileBuffers function to move the pending data from cache to file, without closing the file:
https://docs.microsoft.com/en-us/windows/win32/api/fileapi/nf-fileapi-flushfilebuffers
I'm interested in implement this function but need the windows file handle, and FILEATTR has not been implemented.
There is any way to perform fileflushing?.
Posible to add a _FILEFLUSH statement (or similary) to QB64?

5
QB64 Discussion / BUGS: display of special characters and keyboard mapping
« on: June 05, 2020, 05:25:26 am »
Display of special characters and keyboard mapping are a pending subject in QB64. It applies to both the IDE and the INKEY $, KEYHIT, INPUT ... functions.
Regardless of the IDE language that is selected, the screen output uses the CP437. So if you configure Windows CP1250, you can see what you write, but when you run the program it will show the character corresponding to the extended ASCII code represented by CP437. Therefore, the page chosen for the IDE is not taken into account to generate the text outputs of the compiled program, therefore it is useless to choose another one than CP437. And so it should be to preserve compatibility.
Regarding the presentation, let's take an extended character from page CP437, for example º has the code 167, however when typing º on a Spanish keyboard you receive, both in the IDE and in the executables, with the code 186 that represents as ║, and therefore should be mapped to  167 to show º.
As for the keyboard, some [AltGr] keys, like {} [] work well in the IDE, but not in the INPUT, and in neither case can you type accented letters, which requires a KEYHIT process.
I am attaching an example for a Spanish keyboard.
Code: QB64 $NOPREFIX: [Select]
  2. DEFLNG H-P
  3. 'CONST Phor = 1366, Pver = 768 ' WXGA
  4. CONST Phor = 1600, Pver = 900 ' HD+
  5.  
  6. TITLE "Inkeyhit" 'Version 1.0
  7. hscr = NEWIMAGE(Phor, Pver, 256)
  8. SCREEN hscr
  9. 'Permite comprobar el mapeado del teclado.
  11.  
  12. PuedeFull = (Pver = DESKTOPHEIGHT)
  14. 'Para poner a pantalla completa basta pulsar <Alt><Intro> un par de veces.
  15.  
  16. fontpath$ = "Lucon.ttf": fontsize% = 24 'Windows lucida console 24x14
  17. style$ = "MONOSPACE"
  18. hfont = LOADFONT(fontpath$, fontsize%, style$)
  19. IF hfont THEN FONT hfont
  20.  
  21. LOCATE , , 1 'mostrar cursor solo funciona en modo texto
  22. PRINT "Inkeyhit & display (128-175): €‚ƒ„…†‡ˆ‰Š‹ŒŽ‘’“”•–—˜™š›œžŸ ¡¢£¤¥¦§¨©ª«¬­®¯"
  23. PRINT "                   (176-223): °±²³´µ¶·¸¹º»¼½¾¿ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏÐÑÒÓÔÕÖ×ØÙÚÛÜÝÞß"
  24. PRINT "CP437 extended     (224-254): àáâãäåæçèéêëìíîïðñòóôõö÷øùúûüýþ"
  25. PRINT "Puede comprobar si el mapeado del teclado es correcto"
  26. PRINT CHR$(254);
  27. LOCATE , 1
  29.   in$ = Inkeyhit$ 'emulates quickbasic INKEY$
  30.   IF LEN(in$) THEN
  31.     PRINT in$;
  32.     pcol = POS(0)
  33.     PRINT CHR$(254);
  34.     LOCATE , pcol
  35.   END IF
  36. LOOP UNTIL in$ = CHR$(27)
  38.  
  39. FUNCTION Inkeyhit$ STATIC 'Emulates INKEY$ for spanish keyboard
  40.   DIM i, iaccent AS INTEGER, car AS UNSIGNED BYTE, doblecar AS STRING * 2
  41.   i = KEYHIT
  42.   IF i THEN
  43.     car = 0
  44.     keyalt = KEYDOWN(100307) OR KEYDOWN(100308)
  45.     keyctrl = KEYDOWN(100305) OR KEYDOWN(100306)
  46.     keyshift = KEYDOWN(100303) OR KEYDOWN(100304)
  47.     IF iaccent THEN
  48.       SELECT CASE iaccent
  49.         CASE 1
  50.           SELECT CASE i
  51.             CASE 97: car = 160 '
  52.             CASE 101: car = 130 '‚
  53.             CASE 105: car = 161 '¡
  54.             CASE 111: car = 162 '¢
  55.             CASE 117: car = 163 '£
  56.             CASE 69: car = 144 '
  57.           END SELECT
  58.         CASE 2
  59.           SELECT CASE i
  60.             CASE 97: car = 133 '…
  61.             CASE 101: car = 138 'Š
  62.             CASE 105: car = 141 '
  63.             CASE 111: car = 149 '•
  64.             CASE 117: car = 151 '—
  65.           END SELECT
  66.         CASE 3
  67.           SELECT CASE i
  68.             CASE 97: car = 132 '„
  69.             CASE 101: car = 137 '‰
  70.             CASE 105: car = 139 '‹
  71.             CASE 111: car = 148 '”
  72.             CASE 117: car = 129 '
  73.             CASE 65: car = 142 'Ž
  74.             CASE 79: car = 153 '™
  75.             CASE 85: car = 154 'š
  76.           END SELECT
  77.         CASE 4
  78.           SELECT CASE i
  79.             CASE 97: car = 131 'ƒ
  80.             CASE 101: car = 136 'ˆ
  81.             CASE 105: car = 140 'Œ
  82.             CASE 111: car = 147 '“
  83.             CASE 117: car = 150 '–
  84.           END SELECT
  85.       END SELECT
  86.     END IF
  87.  
  88.     IF car = 0 THEN
  89.       SELECT CASE i
  90.         CASE 48 TO 57 'numeric heys 0-9
  91.           IF keyalt = 0 THEN car = i
  92.         CASE 97 TO 122 'CTRL a-z: 1-26
  93.           car = i
  94.           IF keyctrl THEN car = car - 96
  95.         CASE 128: car = 238 '€î   'spanish keyboard keys maping
  96.         CASE 161: car = 173 '¡­
  97.         CASE 170: car = 166 'ª¦
  98.         CASE 183: car = 249 '·ù
  99.         CASE 186: car = 167 'º§
  100.         CASE 191: car = 168 '¿¨
  101.         CASE 199: car = 128 'ç€
  102.         CASE 209: car = 165 'Ñ¥
  103.         CASE 231: car = 135 'ç‡
  104.         CASE 241: car = 164 'ñ¤
  105.         CASE 1 TO 255
  106.           car = i
  107.         CASE 256 TO 65535 'double byte chr$(0)+
  108.           doblecar = MKI$(i&)
  109.           car = ASC(doblecar, 2)
  110.           IF keyalt THEN
  111.             SELECT CASE car
  112.               CASE 59 TO 68 'F1-F10: ;-D
  113.                 MID$(doblecar, 2) = CHR$(car + 45)
  114.               CASE 133, 134 'F11,F12; …,†
  115.                 MID$(doblecar, 2) = CHR$(car + 6)
  116.               CASE ELSE
  117.                 MID$(doblecar, 2) = CHR$(0)
  118.             END SELECT
  119.           ELSEIF keyctrl THEN
  120.             SELECT CASE car
  121.               CASE 59 TO 68 'F1-F10: ^-g
  122.                 MID$(doblecar, 2) = CHR$(car + 35)
  123.               CASE 71 'Home
  124.                 MID$(doblecar, 2) = CHR$(119)
  125.               CASE 73 'RePag
  126.                 MID$(doblecar, 2) = CHR$(132)
  127.               CASE 75 'Left
  128.                 MID$(doblecar, 2) = CHR$(115)
  129.               CASE 77 'Right
  130.                 MID$(doblecar, 2) = CHR$(116)
  131.               CASE 79 'End
  132.                 MID$(doblecar, 2) = CHR$(117)
  133.               CASE 81 'AvPag
  134.                 MID$(doblecar, 2) = CHR$(118)
  135.               CASE 133, 134 'F11,F12
  136.                 MID$(doblecar, 2) = CHR$(car + 4)
  137.               CASE ELSE
  138.                 MID$(doblecar, 2) = CHR$(0)
  139.             END SELECT
  140.           ELSEIF keyshift THEN
  141.             SELECT CASE car
  142.               CASE 59 TO 68 'F1-F10
  143.                 MID$(doblecar, 2) = CHR$(car + 25)
  144.               CASE 71 TO 81
  145.               CASE 133, 134 'F11,F12
  146.                 MID$(doblecar, 2) = CHR$(car + 2)
  147.               CASE ELSE
  148.                 MID$(doblecar, 2) = CHR$(0)
  149.             END SELECT
  150.           END IF
  151.           IF CVI(doblecar) THEN
  152.             Inkeyhit$ = doblecar
  153.             iaccent = 0
  154.           END IF
  155.           car = 0
  156.         CASE -100308 'Alt up
  157.           IF LEN(buf$) THEN
  158.             car = VAL(buf$)
  159.             buf$ = ""
  160.           END IF
  161.         CASE -222 'accent and dieresis
  162.           IF keyshift THEN
  163.             iaccent = 3
  164.           ELSE
  165.             iaccent = 1
  166.           END IF
  167.         CASE -186 'backaccent and circumflex
  168.           IF keyshift THEN
  169.             iaccent = 4
  170.           ELSE
  171.             iaccent = 2
  172.           END IF
  173.         CASE -57 TO -48 'numeric keys, also numeric keypad with numlock
  174.           IF keyalt THEN
  175.             IF LEN(buf$) > 2 THEN buf$ = RIGHT$(buf$, 2)
  176.             buf$ = buf$ + CHR$(ABS(i&))
  177.           END IF
  178.       END SELECT
  179.     END IF
  180.     IF car THEN
  181.       Inkeyhit$ = CHR$(car)
  182.       iaccent = 0
  183.     END IF
  184.   END IF
  186.  

6
QB64 Discussion / Mousemove bug on fullscreen mode
« on: May 30, 2020, 05:53:44 am »
Bug: MOUSEMOVE on FULLSCREEN works in Desktop coordinates, but can't exceed screen coordinates.
If your Screen resolution and Desktop resolution are equal, works OK.
Else if your app runs on her window, also works OK.
But if you use [Alt][Enter] to put it in FULLSCREEN mode, you can't use de readed mouse coordinates to MOUSEMOVE, so you need to reescale.

Example: fine mouse move with keyboard arrows
Code: QB64: [Select]
  1. 'fine mouse move with arrows
  2. 'Bug: MOUSEMOVE on FULLSCREEN works in Desktop coordinates,
  3. '     but can't exceed screen coordinates
  4. 'press [Alt][Enter] to show FULLSCREEN
  6. DEFLNG H-P
  7. PhDtp = DESKTOPWIDTH
  8. PvDtp = DESKTOPHEIGHT
  9.  
  10. PixHor = 1366: PixVer = 768
  11. 'PixHor = 1728: PixVer = 972
  12.  
  13. SCREEN NEWIMAGE(PixHor, PixVer, 256)
  14. 'FULLSCREEN , SMOOTH
  15. SCREENMOVE 0, 0
  16. pxcenter = PixHor \ 2
  17. pycenter = PixVer \ 2
  18.  
  19. PhCar = FONTWIDTH
  20. PvCar = FONTHEIGHT
  21. pyps = PixVer - PvCar
  22.  
  23. LOCATE 1, 1
  24. PRINT "Desktop:"; PhDtp; PvDtp; "Screen:"; PixHor; PixVer
  25. ifull = FULLSCREEN
  26. LOCATE 1, 48: PRINT "FULL:"; ifull
  27. PRINT "Use Keyboard arrors to fine position the mouse cursor, press any key to mark with +, [Backspace] to retrive last mark, click to draw."
  28. PRINT "Test in FULLSCREEN, presing [Alt][Enter]: Now MOUSEMOVE works on Desktop coordinates"
  29.  
  30. mx = 0
  31. my = 0
  32. markx = PixHor \ 2
  33. marky = PixVer \ 2
  34. MOUSESHOW
  35. MOUSEMOVE pxcenter, pycenter 'center mouse
  36. PRINTSTRING (pxcenter - PhCar \ 2, pycenter - PvCar \ 2), "X"
  38.   nfull = FULLSCREEN
  39.   IF nfull - ifull THEN
  40.     LOCATE 1, 53: PRINT nfull
  41.     ifull = nfull
  42.   END IF
  43.   DO WHILE MOUSEINPUT
  44.     mx = MOUSEX
  45.     my = MOUSEY
  46.     mClick = MOUSEBUTTON(1)
  47.     ' mouseRight = MOUSEBUTTON(2)
  48.     ' mouseMiddle = MOUSEBUTTON(3)
  49.     ' MOUSEWHEEL
  50.     PRINTSTRING (0, pyps), STR$(mx) + STR$(my) + SPACE$(6)
  51.  
  52.     IF mClick THEN
  53.       PSET (mx, my)
  54.       PRINTSTRING (120, pyps), "Click:" + STR$(mx) + STR$(my) + SPACE$(6)
  55.     END IF
  56.   LOOP
  57.  
  58.   in$ = INKEY$
  59.   IF LEN(in$) THEN
  60.     '...  capture arrows & do mouse move
  61.     SELECT CASE in$
  62.       CASE CHR$(0) + "H" 'Up
  63.         IF my THEN move = 1 ELSE move = 0
  64.       CASE CHR$(0) + "K" 'Left
  65.         IF mx THEN move = 2 ELSE move = 0
  66.       CASE CHR$(0) + "M" 'Right
  67.         IF mx + 1 < PixHor THEN move = 3 ELSE move = 0
  68.       CASE CHR$(0) + "P" 'Down
  69.         IF my + 1 < PixVer THEN move = 4 ELSE move = 0
  70.       CASE CHR$(8) 'Backspace
  71.         move = 9
  72.       CASE ELSE
  73.         PRINTSTRING (mx - PhCar \ 2, my - PvCar \ 2), "+"
  74.         markx = mx: marky = my
  75.     END SELECT
  76.  
  77.     IF move THEN
  78.       mxi = mx: myi = my
  79.       PRINTSTRING (380, pyps), "Last move:" + STR$(move)
  80.       IF FULLSCREEN THEN '1:stretch, 2:squarepixels
  81.         mxmovi = CINT(mx * PhDtp / PixHor) 'scale conversion for mousemove
  82.         mymovi = CINT(my * PvDtp / PixVer)
  83.  
  84.         SELECT CASE move
  85.           CASE 1: my = my - 1
  86.           CASE 2: mx = mx - 1
  87.           CASE 3: mx = mx + 1
  88.           CASE 4: my = my + 1
  89.           CASE 9
  90.             mx = markx
  91.             my = marky
  92.           CASE ELSE
  93.         END SELECT
  94.         mxmov = CINT(mx * PhDtp / PixHor)
  95.         mymov = CINT(my * PvDtp / PixVer)
  96.         IF mxmov >= PixHor THEN move = 0
  97.         IF mymov >= PixVer THEN move = 0
  98.         IF move THEN
  99.           PRINTSTRING (480, pyps), STR$(mxmov) + STR$(mymov) + SPACE$(6)
  100.           MOUSEMOVE mxmov, mymov
  101.         ELSE
  102.           PRINTSTRING (480, pyps), STR$(mxmovi) + STR$(mymovi) + SPACE$(6)
  103.           mx = mxi: my = myi
  104.         END IF
  105.       ELSE
  106.         SELECT CASE move
  107.           CASE 1: my = my - 1
  108.           CASE 2: mx = mx - 1
  109.           CASE 3: mx = mx + 1
  110.           CASE 4: my = my + 1
  111.           CASE 9
  112.             mx = markx
  113.             my = marky
  114.           CASE ELSE
  115.         END SELECT
  116.         PRINTSTRING (480, pyps), STR$(mx) + STR$(my) + SPACE$(6)
  117.         MOUSEMOVE mx, my
  118.       END IF
  119.       move = 0
  120.     END IF
  121.   END IF
  122. LOOP UNTIL in$ = CHR$(27)
  124.  

7
QB64 Discussion / INKEY$ was unable to capture accented vowels, nor al keyboard symbols
« on: April 04, 2019, 02:54:16 pm »
Contrary to INKEY$ function of Quickbasic, wich performs very well, the INKEY$ function of QB64 was unable to capture accented vowels, like 'áéíóú'.
Also INKEY$ was unable to capture to capture the <AltGr> symbols, and the spanish 'ñ'  or the french 'ç'.
I think this is a bug.
However some maping is posible:
Code: QB64: [Select]
  1. FUNCTION Inkeymap$
  2.   in$ = INKEY$
  3.   IF LEN(in$) THEN
  4.     SELECT CASE ASC(in$)
  5.       CASE 0
  6.         IF LEN(in$) = 2 THEN '...spanish keyboard
  7.           SELECT CASE ASC(in$, 2)
  8.             CASE 26: in$ = "["
  9.             CASE 27: in$ = "]"
  10.             CASE 43: in$ = "\"
  11.             CASE 121: in$ = "@"
  12.             CASE 122: in$ = "#"
  13.             CASE ELSE
  14.           END SELECT
  15.         END IF
  16.       CASE 161: in$ = CHR$(173) '"¡­"
  17.       CASE 170: in$ = CHR$(166) '"ª"
  18.       CASE 186: in$ = CHR$(167) '"º"
  19.       CASE 191: in$ = CHR$(168) '"¿"
  20.       CASE 209: in$ = CHR$(165) '"Ñ"
  21.       CASE 231: in$ = CHR$(128) '"ç"
  22.       CASE 241: in$ = CHR$(164) '"ñ"
  23.       CASE ELSE
  24.     END SELECT
  25.   END IF
  26.   Inkeymap$ = in$
  28.  

Pages: [1]