Moderators: Mathias, Mug UK, moondog/.tSCc., [ProToS], Galvez, Moderator Team
peterlane wrote:Has fVDI then replaced the Falcon's original VDI code in FireTOS?
Faucon2001 wrote:NVDI is used only for the printing side
shoggoth wrote:I don't think NVDI provides offscreen bitmaps if you're using fVDI as an underlaying screen driver.
jfl wrote:shoggoth wrote:I don't think NVDI provides offscreen bitmaps if you're using fVDI as an underlaying screen driver.
Simple, when NVDI is running offscreen bitmpas work, when it doesn’t they don't. Go figure.
shoggoth wrote:On a system where fVDI is responsible for screen drivers, and you run NVDI on top to extend the VDI, NVDI is by definition "running", but you won't get offscreen bitmaps.
jfl wrote:shoggoth wrote:On a system where fVDI is responsible for screen drivers, and you run NVDI on top to extend the VDI, NVDI is by definition "running", but you won't get offscreen bitmaps.
Shoggoth, I'm telling that on my FIreBee, with NVDI I have offscreen bitmaps, without it I don't. And I can't deactivate fVDI since it's inside FIreTOS. Why don't you believe me? I'm not making this up. If you have another explanation, I would be interested. But please stop correcting me on something I know to be true by experience.
shoggoth wrote:I tested it by attempting to open and use offscreen bitmaps in my own code on multiple VDIs, but the best outcome would be that I'm wrong (i.e. my test code was wrong) and you're right. Perhaps the situation has changed (i.e. Didier has put offscreen bitmap support in FireTOS after I made my tests).
How did you test it?
jfl wrote:By running GEMDict (see signature) which uses offscreen bitmaps for it's text display. If I disable NVDI during boot the display is garbled. Exactly like it is with ARAnyM+fVDI. I'm pretty sure Didier hasn't done anything with this.shoggoth wrote:How did you test it?
Mathias wrote:The only person who could enlighten us is Didier. Perhaps somebody should drop him a mail.
peterlane wrote:Thanks everyone for your responses. It seems the situation is not very clear for the VDI part!
From the discussion, the picture I get is as follows:
1. FireTOS uses fVDI, as this supports the Firebee video modes.
peterlane wrote:2. When we install NVDI on top, the situation becomes complex. fVDI retains control over (most?) aspects to do with output to the screen. NVDI provides some additional/improved functionality. This additional functionality includes fonts and (pace shoggoth!) offscreen bitmaps.
shoggoth wrote:jfl wrote:By running GEMDict (see signature) which uses offscreen bitmaps for it's text display. If I disable NVDI during boot the display is garbled. Exactly like it is with ARAnyM+fVDI. I'm pretty sure Didier hasn't done anything with this.shoggoth wrote:How did you test it?
This is potentially great news. What functions did you use? IIRC I tested the return values of v_opnbm()
jfl wrote:Same here. v_opnbm() and v_clsbm(). Be careful that with fVDI you won't get any errors using these functions. So checking return values is not a valid indication. You need to actually have stuff correctly displayed on screen. Which doesn't happen with fVDI alone. Basically, the offscreen bitmaps implementation in fVDI is completely bogus. Rather than returning a valid error so the program knows it should stop there (for example a zero in the third parameter) it craps all over the screen. Not nice.
Code: Select all
/* Doesn't allow the EdDI v1.1 variant yet */
if (!intin[15] || !intin[16] || !intin[17] || !intin[18] || !intin[19])
return;
Users browsing this forum: No registered users and 2 guests