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
CODE PROJECT For Those Who Code
  • Home
  • Articles
  • FAQ
Community
O

Ori 0

@Ori 0
About
Posts
5
Topics
3
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • RTF language support
    O Ori 0

    Hi, I have a dialog with an RTF formatted text. Right now it only supports English. How do I detect a diffetent character set, and set it accordingly? I also may have to swtich right-left reading if it's a right to left oriented language, how do I switch in the directions back and forth? I have read some of the RTF documentation, but couldn't get the whole thing to work right. Thank you,

    C / C++ / MFC question

  • Thread & Message pb?
    O Ori 0

    The MSG is defined as WM_APP + 2. There is no other equivalent MSG value that might collide with this. I have thought of the option of 16 BIT trancation, but if that is the case, isn't it supposed to happen more often? It only happens on a very specific scenario, and not 100% reconstructable (Timing?). Is there any solution for this? specifing the use of 32 bit addresses?

    C / C++ / MFC help tutorial question

  • Thread & Message pb?
    O Ori 0

    I also forgot to mention one more important thing: This only happens on Win9x\ME and not on the NT series.

    C / C++ / MFC help tutorial question

  • Thread & Message pb?
    O Ori 0

    Hi, I have a strange bug in something I'm working on: The main program gets a message every few seconds from a different thread that does ::PostMessage(MY_MSG, (WPARAM)sString, LPARAM(nNumber); The function that handles this message in the main thread, gets the sString address correctly 99% of the times except from a unique scenario that causes the sString adderss to be cut in half - I'm getting only the LOWORD value of the address. For example: When running correctly, (WPARAM)sString is at 0x0172F6B8 When the bug happens it's only F6B8. The bug happens when you cause the message to be posted twice with little time in between. Any clues? I'm a bit helpless here... Ori

    C / C++ / MFC help tutorial question

  • Paint problems
    O Ori 0

    Ok, I'm aware that it lacks in details, but that's what I have so far: Someone here implemeted a skin mechanism for an application. He uses a script and compiles it into a resource list. I'm pretty sure he used bitmap streching for resizing. The problem is this: Resizible windows that he defines as Dialogs leave ugly background color marks when resizing them. This only happens on Win9x (Inferior GDI performance?). Windows that are defined as CWnd and not CDialog do not leave the color traces. Any leads on where to start solving the color traces of the dialogs? How is Dialog resizing different from windows resizing? Thank you, Any help would be great. Ori

    C / C++ / MFC graphics help tools performance question
  • Login

  • Don't have an account? Register

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