Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
P

Parthiban Appuswamy

@Parthiban Appuswamy
About
Posts
2
Topics
0
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Stuck in 2 loops
    P Parthiban Appuswamy

    I did not see any issue in above code. But what condition you are checking to show the comment - No Issues in voltage?

    C / C++ / MFC help question

  • Does DestroyWindow Parent CDialog destroy all ChildControls
    P Parthiban Appuswamy

    Yes, if you are allocating memory using 'new' to your RichEdit, then yes you have to release it. But you have to do it before your parent window (in this case your CDialog) is destroyed. Override OnDestroy (WM_DESTROY) and destroy your RichEdit followed by 'delete' (to release heap memory) and then call the CDialog::OnDestroy().

    C / C++ / MFC
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups