|
Thank you, this has been very helpful, I just have one more question; what about vec3, vec4, etc. This might be a stupid question, there might be a data structure in opengl that can handle data from these types, but what do i do about these data types?
|
|
|
|
|
glBindAttrib*() has versions that accept all types of values.
See examples at: http://www.lighthouse3d.com/opengl/glsl/index.php?ogluniform[^]
...cmk
The idea that I can be presented with a problem, set out to logically solve it with the tools at hand, and wind up with a program that could not be legally used because someone else followed the same logical steps some years ago and filed for a patent on it is horrifying.
- John Carmack
modified on Wednesday, April 21, 2010 2:29 PM
|
|
|
|
|
BOOL result = tb->CreateEx( this
,TBSTYLE_TRANSPARENT | TBSTYLE_FLAT
,WS_CHILD | WS_VISIBLE | CBRS_TOP | CBRS_TOOLTIPS | CBRS_FLYBY | CBRS_SIZE_DYNAMIC) ,toolBarBorder
,TB_ID);
For some reason this crashes in release mode but not debug, where should I be looking for some un-initialized pointers. I can't seem to isolate where it is happening. Can anyone give me some pointers? Using VS2008, by the way no crashes in release or debug in VS2003
Thanks
Ray
|
|
|
|
|
First thing, when you build a release build you should still include debug information. Using Visual Studio 2008: the "Debug Information Format" setting in C++ node of the project properties should be set to "Program Database (/Zi)" for release builds (and "Program Database for Edit & Continue(/ZI)" on debug builds); On the "Linker->Debugging" node set "Generate Debug Info" to "Yes". Once you've got all that set-up debug the program as you normally would - you can't trust the debugger as much as you can in a release build, but all generally works well.
Steve
|
|
|
|
|
|
How to find out exception type in the unexpected exception handler
|
|
|
|
|
GetExceptionInformation[^] combined with typeid (if it has virtual functions) are your best shot for a simple solution; otherwise you may want to look up some articles on exception handling for C++.
|
|
|
|
|
I have a CFormView with several pages. For some reason, if I use
the mouse wheel, a page will scroll up and down using the mouse
wheel. For other pages, the mouse wheel doesnt work. I have studied
the 2-pages ad nausem and I cant figure out what is different from
one page to the other; why one page uses the mouse wheel and the
other doesnt.
Any ideas? Any direction any one can give me will be greatly
appreciated.
Sincerely,
Danielle Brina (an overworked graduate student)
|
|
|
|
|
Check if your CFormview still owns the scrollbar. If not, no scrolling.
Also there is a bug in MFC 7.1 and 8.0 which can cause this behaviour. If all else fails implement your own ::OnMouseWheel.
|
|
|
|
|
Normally the View should scroll by default. Mostly you have such problem when you have some control over the form, you will need to handle Scroll messages in the control in this case.I can scroll with the wheel in a CFormView application. If no controls is placed in your form too, then I suggest you to try your application on a different machine, see if there is any changes?
|
|
|
|
|
in my Pocket PC (MFC VS2009) app, I am trying to open/read a txt file, but most of the read file commands are not included. The only one seems to work for me is ReadFile, which is not that easy to use if I want to read lines of text.
Any ideas?
|
|
|
|
|
Please get and try the class on the bottom of the article[^] 
virtual void BeHappy() = 0;
|
|
|
|
|
|
Software2007 wrote: Any ideas?
Can you use fopen() and fscanf()?
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"Man who follows car will be exhausted." - Confucius
|
|
|
|
|
I got DLL injection example from youtube. http://www.youtube.com/watch?v=H3O3hmXkt1I
For some reason it says: "Injection failed" (under indows 7) and under win xp this exe doesn't even start (i see msgbox telling me to reinstall this app).
It compiles w/o errors
Injector.exe
#include <iostream><br />
#include <direct.h><br />
#include <windows.h><br />
#include <tlhelp32.h><br />
using namespace std;<br />
<br />
char* GetCurrentDir()<br />
{<br />
char* szRet = (char*)malloc(MAX_PATH);<br />
<br />
_getcwd(szRet, MAX_PATH);<br />
<br />
return szRet;<br />
}<br />
<br />
LPCTSTR SzToLPCTSTR(char* szString)<br />
{<br />
LPTSTR lpszRet;<br />
size_t size = strlen(szString)+1;<br />
lpszRet = (LPTSTR)malloc(MAX_PATH);<br />
mbstowcs_s(NULL,lpszRet,size,szString,_TRUNCATE);<br />
return lpszRet;<br />
}<br />
<br />
void WaitForProcessToAppear(LPCTSTR lpcszProc, DWORD dwDelay)<br />
{<br />
HANDLE hSnap;<br />
PROCESSENTRY32 peProc;<br />
BOOL bAppeared = FALSE;<br />
<br />
while (!bAppeared)<br />
{<br />
if((hSnap = CreateToolhelp32Snapshot(TH32CS_SNAPPROCESS,0)) != INVALID_HANDLE_VALUE)<br />
{<br />
peProc.dwSize = sizeof(PROCESSENTRY32);<br />
if(Process32First(hSnap, &peProc))<br />
while(Process32Next (hSnap, &peProc) && !bAppeared)<br />
if(!lstrcmp(lpcszProc, peProc.szExeFile))<br />
bAppeared = TRUE;<br />
}<br />
CloseHandle(hSnap);<br />
Sleep(dwDelay);<br />
}<br />
}<br />
<br />
DWORD GetProcessIdByName(LPCTSTR lpcszProc)<br />
{<br />
HANDLE hSnap;<br />
PROCESSENTRY32 peProc;<br />
DWORD dwRet = -1;<br />
<br />
if((hSnap = CreateToolhelp32Snapshot(TH32CS_SNAPPROCESS,0)) != INVALID_HANDLE_VALUE)<br />
{<br />
peProc.dwSize = sizeof(PROCESSENTRY32);<br />
if(Process32First(hSnap, &peProc))<br />
while(Process32Next (hSnap, &peProc))<br />
if(!lstrcmp(lpcszProc, peProc.szExeFile))<br />
dwRet = peProc.th32ProcessID;<br />
}<br />
CloseHandle(hSnap);<br />
return dwRet;<br />
}<br />
<br />
BOOL InjectDLL(DWORD dwPid, char* szDllPath)<br />
{<br />
DWORD dwMemSize;<br />
HANDLE hProc;<br />
LPVOID lpRemoteMem, lpLoadLibrary;<br />
BOOL bRet = FALSE;<br />
<br />
if((hProc = OpenProcess(PROCESS_VM_OPERATION | PROCESS_VM_WRITE | PROCESS_CREATE_THREAD, FALSE, dwPid)) != NULL)<br />
{<br />
dwMemSize = strlen(szDllPath) +1;<br />
if((lpRemoteMem = VirtualAllocEx(hProc,NULL,dwMemSize,MEM_COMMIT,PAGE_READWRITE)) != NULL)<br />
if(WriteProcessMemory(hProc, lpRemoteMem, (LPCVOID)szDllPath,dwMemSize,NULL))<br />
{<br />
lpLoadLibrary = GetProcAddress(GetModuleHandleA("kernel32.dll"), "LoadLibraryA");<br />
if(CreateRemoteThread(hProc, NULL, 0, (LPTHREAD_START_ROUTINE)lpLoadLibrary, lpRemoteMem, 0, NULL) != NULL)<br />
bRet = TRUE;<br />
}<br />
}<br />
CloseHandle(hProc);<br />
<br />
return bRet;<br />
}<br />
<br />
int main()<br />
{<br />
char szProc[MAX_PATH],szDll[MAX_PATH];<br />
char* szDllPath = (char*)malloc(MAX_PATH);<br />
LPTSTR lpszProc = NULL;<br />
for(;;)<br />
{<br />
cout << "Proccess: ";<br />
cin >> szProc;<br />
cout << "DLL: ";<br />
cin >> szDll;<br />
szDllPath = GetCurrentDir();<br />
strcat_s(szDllPath,MAX_PATH,"\\");<br />
strcat_s(szDllPath,MAX_PATH,szDll);<br />
cout << "Waiting for process..." << endl;<br />
WaitForProcessToAppear(SzToLPCTSTR(szProc), 100);<br />
if(InjectDLL(GetProcessIdByName(SzToLPCTSTR(szProc)),szDllPath))<br />
cout << "Injection succeeded!" << endl;<br />
else<br />
cout << "Injection failed!" << endl;<br />
cout << "\n";<br />
}<br />
<br />
return 0;<br />
}
test.dll
#include <windows.h><br />
<br />
BOOL WINAPI DllMain(HANDLE hInstance, DWORD dwReason, LPVOID lpReserved)<br />
{<br />
switch(dwReason)<br />
{<br />
case DLL_PROCESS_ATTACH:<br />
MessageBox(0, L"I'm injected!",L"injxOrz", MB_OK);<br />
}<br />
<br />
return TRUE;<br />
}
any ideas?
|
|
|
|
|
Try to run the code with administrator privileges.
|
|
|
|
|
>Try to run the code with administrator privileges.
still fails.
Does that code work for you?
|
|
|
|
|
You should try to debug it and find out what fails exactly.
|
|
|
|
|
try setting debug priviledges
|
|
|
|
|
whats the debug privileges?
In youtube tutorial is used win xp but i hav win 7, would that be a problem?
if i debug variables to console i will probably get just some numbers that doesn't say any thing for me but, I will try it.
edit1: why doesn't this exe run on win xp?( copied binary (didn't recompile it))
"This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem"
in win 7 it runs but doen't inject.
modified on Tuesday, April 20, 2010 3:04 PM
|
|
|
|
|
Why don't you give us something to go on? How far does execution get? If something fails, are any error being returned? What are the errors? Has the code ever worked? Is something catching fire?
Steve
|
|
|
|
|
i think OpenProcess need just PROCESS_ALL_ACCESS, that is enough.
Please check whether it is failing on that location
Check this article API Hooking (LoadLibrary)[^] for more info.
Величие не Бога может быть недооценена.
|
|
|
|
|
>Why don't you give us something to go on? How far does execution get? If something fails, are any error being returned? What are the errors? Has the code ever worked? Is something catching fire?
Proccess: inject.exe
DLL: test.dll
Waiting for process...
Injection failed!
Proccess:
http://autoit.pri.ee/downloads/dllinject.zip
>i think OpenProcess need just PROCESS_ALL_ACCESS, that is enough.
>Please check whether it is failing on that location
'I tried that, same result as above
|
|
|
|
|
Hi,
I was wondering when using a operator
such as "+" in order to be invoked does the
code being executed have to be part of
that class where the operator was defined or
with regards for example a "+" operator
if one the operands is of a type where
the operator has been defined then the
opertor code will get invoked. So.....
CString + (LPSTR) invoked in any method
of any class will execute the CString operator +
code
thankx
|
|
|
|
|
hmmm... not certain I understand correctly, but ...
If there's an operator defined for a class it will be called when it is referenced in the code; if the types are not allowable then the compiler will report an error (or warning).
In you example, there is an operator that allow the operator+ between a CString and a L(C)PSTR.
friend CStringT operator+(
const CStringT& str1,
PCXSTR psz2
);
Watched code never compiles.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
