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
K

KnaveWave

@KnaveWave
About
Posts
4
Topics
3
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Releasing MFC projects
    K KnaveWave

    Can anyone point me to some good articles about realeasing mfc projects. Ive searched around but im not sure exactly what im looking for. Ive compiled my proj for release and ive learned how to bundle it with an installer, but i dont know what mfc DLLs (my proj used mfc shared DLL) i need to include and where i need to go about copying them on install.

    C / C++ / MFC c++ tutorial announcement

  • Shell doesnt give long filename
    K KnaveWave

    Thank you very much! GetLongPathName was exactly what i needed. Just out of curiosity, do you have any idea why id be getting a short filename? I manually setup the registry so that when someone right clicked on the file type it ran my program and passed the file as a parameter. Whenever my program would get the command line data itd be in the form: and by short path i mean the old school dos type w/ ~'s in the path

    C / C++ / MFC linux workspace

  • Shell doesnt give long filename
    K KnaveWave

    Im trying to setup my app so that when a user right clicks on a associated file type then selects "run with myApp" itll open my app passing the files full path. Ive tried getCommandLine() and directly accessing m_lpCmdLine but both of these return the short file name.

    C / C++ / MFC linux workspace

  • ShellExecute and execl woes
    K KnaveWave

    Im writing a front end for a console prog in VCPP and am having a hell of a time trying to pass params. For some reason whenever i use ShellExecute to pass params the programm receiving them interperates all params as a single param and fails (according to its log). If i use _execl it works perfectly only my app terminates for some odd reason. Im a fairly experienced programmer and have just started out w/ windows programming. This is also my first windows app thatll serve a purposed btw :) Heres the ShellExecute code that doesnt not pass the params correctly: ShellExecute(NULL, "Open", "C:\\Program Files\\UT2004\\System\\ucc.exe", "compress AS-Convoy.ut2", NULL, SW_SHOWNORMAL); And heres the _execl that works but kills my app: execl("C:\\Program Files\\UT2004\\System\\ucc.exe", " compress", "AS-Convoy.ut2", NULL); * note the space before " compress" if i leave out this space the called prog fails. ive tried the same thing w/ ShellExecute but it still fails. If anyone has an idea about how i should go about getting ShellExecute to pass the params different or how i can stop _execl from killing my app id be very greatful. Oi! Oi! Oi!

    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