Problem with image in upcoming v1.5 (dev build)

[Kernelpanic]

It looks like version 1.5 has a problem with images. The picture will probably not be found. There are no problems with version 1.4.

  [ You are not allowed to view this attachment ]  

[FellippeHeitor]

Please provide the image file you're attempting to use and also paste the code here so we can check it.

[SMcNeill]

Quick question:  Did you copy the image in the 1.5 Folder?

V1.4 would be in one path, v1.5 would be in a different path, so it makes sense that code just copy/pasted from one to the other wouldn't find resource files in the other's folder.

[SpriggsySpriggs]

Quick question:  Did you copy the image in the 1.5 Folder?

Makes sense, seeing as how he's only using the filename rather than the absolute path.

[Kernelpanic]

File and picture are in the same folder.

Code: QB64: [Select]

1. 'Uebungen Bild laden
2.  
3. OPTION _EXPLICIT
4.  
5. DIM NeuesFenster AS LONG, Bild AS LONG
6. DIM Text AS STRING
7.  
8. NeuesFenster = _NEWIMAGE(1024, 768, 32)
9. SCREEN NeuesFenster
10.  
11. 'Vordergrund- und Hintergrundfarbe
12. 'COLOR _RGB32(255, 0, 0), _RGB32(255)
13. 'LOCATE (CSRLIN + 2), POS(0)
14. 'PRINT "Hallo, QuickBasic 64!"
15. 'SLEEP
16.  
17. 'Bild laden
18. Bild = _LOADIMAGE("Marilyn.jpg", 32)
19. _DEST NeuesFenster
20. '_PUTIMAGE (0, 0)-(320, 200), NeuesFenster, 0, (0, 0)-(320, 200)
21. _PUTIMAGE (0, 0), Bild
22.  
23. END
24.  

  [ You are not allowed to view this attachment ]  

  [ You are not allowed to view this attachment ]  

[Kernelpanic]

The same problem. The picture ist in the folder "Bilder". In Version 1.4 no problems.

Code: QB64: [Select]

1. 'Uebungen Bild laden
2.  
3. OPTION _EXPLICIT
4.  
5. DIM NeuesFenster AS LONG, Bild AS LONG
6. DIM Text AS STRING
7.  
8. NeuesFenster = _NEWIMAGE(1024, 768, 32)
9. SCREEN NeuesFenster
10.  
11. 'Vordergrund- und Hintergrundfarbe
12. 'COLOR _RGB32(255, 0, 0), _RGB32(255)
13. 'LOCATE (CSRLIN + 2), POS(0)
14. 'PRINT "Hallo, QuickBasic 64!"
15. 'SLEEP
16.  
17. 'Bild laden
18. Bild = _LOADIMAGE("Bilder\Marilyn-1956.jpg", 32)
19. _DEST NeuesFenster
20. '_PUTIMAGE (0, 0)-(320, 200), NeuesFenster, 0, (0, 0)-(320, 200)
21. _PUTIMAGE (0, 0), Bild
22.  
23. END
24.  

[SMcNeill]

Second Question: In 1.5 (where the glitch appears), have you checked the "export EXE  to source folder" option?

[Petr]

Works as expected under 1.5 and also under 1.4

  [ You are not allowed to view this attachment ]  

try add coma to path (".\bilders\.....")

 

[Kernelpanic]

Second Question: In 1.5 (where the glitch appears), have you checked the "export EXE  to source folder" option?

That was it! Now it is ok.

It would be good to make that the default.

Addendum: I only know of this that the executable file is by default in the same directory as the source file. QB64 behaves here in a really unusual way.

[SMcNeill]

When you compile, the source file, by default, goes in the QB64 folder with QB64.EXE.

What you've done is compiled one EXE in the data folder with the picture with v1.4, and then compiled a separate EXE in the QB64 V1.5 folder.  You're still seeing the EXE in your data folder from a previous build, but the one in the 1,5 folder is what is executing and tossing an error for invalid handles from files not pathing properly.