Author |
Topic: problem with AVICAP and LBB (Read 2029 times) |
|
pierscintilla
New Member
member is offline
Gender: 
Posts: 30
|
 |
Re: problem with AVICAP and LBB
« Reply #9 on: Jul 1st, 2014, 5:02pm » |
|
Hello.
Thank you very much for the alert. Now, with version 2.63, the Avicap problem is solved.
It can also be with the version 6.22 but I did not tested.
I must to give you a monument!
However, I have discovered another problem:
It seems that GETBMP or BMPSAVE not works.
I copy a part of the image of the camera and go to put this in a file "temp.bmp" with the following lines:
PRINT # main, "getbmp screen 40 40 320 240"
BMPSAVE "screen", "temp.bmp"
but the image in the file is completely white ..
Many thanks
Pier
|
|
 Logged
|
|
|
|
Richard Russell
Administrator
member is offline
Posts: 1348
|
|
Re: problem with AVICAP and LBB
« Reply #10 on: Jul 1st, 2014, 6:01pm » |
|
on Jul 1st, 2014, 5:02pm, pierscintilla wrote:| It seems that GETBMP or BMPSAVE not works. |
|
The GETBMP command doesn't read the 'screen', it reads the 'graphics window'. This is documented in the Liberty BASIC help file: "This command will make a bitmap copied from the graphics window at x, y and using width and height".
A feature of LB 4.04 is that the GETBMP command doesn't actually do what the docs say - instead of copying from the graphics window it copies from the screen. This is normally undesirable, because it means if the graphics window is covered by another window GETBMP doesn't work correctly. I have fixed this fault in LBB.
It sounds as though your program relies on LB's faulty behaviour, but it should never have worked. You will need to read the screen using a 'legitimate' method, for example by using the BitBlt API (that will work in LB, too).
It would be neither sensible nor desirable for LBB to reproduce all LB's quirks, especially those which contradict the documentation. Sorry.
Richard.
|
|
Logged
|
|
|
|
pierscintilla
New Member
member is offline
Gender:
Posts: 30
|
|
Re: problem with AVICAP and LBB
« Reply #11 on: Jul 1st, 2014, 6:20pm » |
|
Remarks absolutely shared.
Actually I realized that GETBMP copy the screen and not the graphics window, and this was a problem even if I have accepted the strange behavior.
Now I will try with BitBlt although for me (not a good programmer), is a little more complicated.
Thanks again
Pier
|
|
Logged
|
|
|
|
pierscintilla
New Member
member is offline
Gender:
Posts: 30
|
|
Re: problem with AVICAP and LBB
« Reply #13 on: Jul 1st, 2014, 7:24pm » |
|
Help fantastic.
thank you very much!!!!!!!!!!!
|
|
Logged
|
|
|
|
Richard Russell
Administrator
member is offline
Posts: 1348
|
|
Re: problem with AVICAP and LBB
« Reply #14 on: Jul 1st, 2014, 8:28pm » |
|
on Jun 25th, 2014, 9:18pm, pierscintilla wrote:| If you're interested, it would be nice to include in the list of dll supported by lbb |
|
I have created a page on the Wiki listing those DLLs that I know to be compatible (or incompatible) with LBB:
http://lbbooster.wikispaces.com/DLLs+compatible+with+LBB
This is of course a community-editable Wiki so can I ask that anybody with additional information adds to the page. If you find a DLL which doesn't work with LBB, but you would like it to, please also post a request here.
Richard.
|
|
Logged
|
|
|
|
Richard Russell
Administrator
member is offline
Posts: 1348
|
|
Re: problem with AVICAP and LBB
« Reply #15 on: Jul 2nd, 2014, 6:02pm » |
|
on Jun 25th, 2014, 9:18pm, pierscintilla wrote:
Tried to look there, but membership has to be approved and I think I can predict what would happen if I tried to join. 
Richard.
|
|
Logged
|
|
|
|
pierscintilla
New Member
member is offline
Gender:
Posts: 30
|
|
Re: problem with AVICAP and LBB
« Reply #16 on: Jul 4th, 2014, 6:23pm » |
|
Ok, at the end to save the frame on the BMP file I used the user32 and SendMessageA that work fine.
For the YoingcoDLLs.zip file (with the various nice DLL ) if you want I can myself send it to you (is public domain)  .
Thanks again for the generous advice and for the valuable gift (LBB)
Pier
|
|
Logged
|
|
|
|
|
