Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Solved it, although I'm sure this isn't optimal. Firstly, as Chris Becke suggested, you shouldn't respond to the WM_PAINT message and should only update using the 'UpdateLayeredWindow'. One of the problems I had was that gave UpdateLayeredWindow some bad coordinates, specifically I'd swapped the source and destination around (doh!)</p> <p>Here's the code for calling UpdateLayeredWindow from a GDI+ surface. It's not optimal but it works.</p> <pre><code>void TOPLEVEL_FLOATING_WINDOW::update_layered_window() { BLENDFUNCTION blend_func = { 0 }; //build the blend function object... I guess microsoft doesn't/didn't like constructors blend_func.AlphaFormat = AC_SRC_OVER; blend_func.BlendFlags = 0; blend_func.SourceConstantAlpha = 255; blend_func.AlphaFormat = AC_SRC_ALPHA; POINT_2i pt = m_screen_pos; VECTOR_2i dim = m_bounds.dimensions(); POINT_2i pt_src (0,0) ; Gdiplus::Color bg(0,0,0,0); m_gdip_offscreen_bm-&gt;GetHBITMAP(bg, &amp;m_offscreen_bm); //get the Hbitmap from my GDI+ bitmap - I think this is allocating a whole new bitmap off the heap. Yuck, very inefficient! HDC splash_dc = CreateCompatibleDC(m_display_dc); //create a temporary HDC HGDIOBJ oldobj = SelectObject(splash_dc , m_offscreen_bm); //'select' the bitmap. UpdateLayeredWindow(m_hwnd,m_display_dc, (POINT*)&amp;pt, (SIZE*)&amp;dim, splash_dc , (POINT*)&amp;pt_src, 0 ,&amp;blend_func,ULW_ALPHA); //this call works and updates our splash screens hidden buffer SelectObject(splash_dc, oldobj); //some tidy up code DeleteObject(m_offscreen_bm); //free the bitmap. Memory fragmentation HO! DeleteDC(splash_dc); //Delete the DC } </code></pre> <p>And here's what I <em>think</em> should work but does not. I'll hand out some points to anybody who can tell me why not! I imagine this is because HDCs are not born equal and the UpdateLayeredWindow function can only accept HDCs created by a certain source in a certain way. It would be nice if the rules for this were more obvious.</p> <pre><code>void TOPLEVEL_FLOATING_WINDOW::update_layered_window_in_an_ideal_world() { m_refresh_needed = false; BLENDFUNCTION blend_func = { 0 }; blend_func.AlphaFormat = AC_SRC_OVER; blend_func.BlendFlags = 0; blend_func.SourceConstantAlpha = 255; blend_func.AlphaFormat = AC_SRC_ALPHA; POINT_2i pt = m_screen_pos; VECTOR_2i dim = m_bounds.dimensions(); POINT_2i pt_src (0,0) ; HDC gdi_HDC = m_screen_gdi_dc-&gt;GetHDC(); //I have a GDI+ 'Graphics' object whose back buffer is the image I want to composite on to the desktop UpdateLayeredWindow(m_hwnd,m_display_dc, (POINT*)&amp;pt, (SIZE*)&amp;dim, gdi_HDC , (POINT*)&amp;pt_src, 0 ,&amp;blend_func,ULW_ALPHA); m_screen_gdi_dc-&gt;ReleaseHDC(gdi_HDC); //be nice and release the gdi_HDC } </code></pre> <p>The only other alternative is to ignore GDI+ and render everything using my own raster library, which is quite happy to render to any offscreen buffer. However, that's kind of overkill for this project.</p>
    singulars
    1. This table or related slice is empty.
    1. POWindows splash screen using GDI+
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USLuther
    1. USLuther
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWindows splash screen using GDI+
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload