Posted by member 42328 on 2003-06-25 12:03:44
I'll start here but if anybody has any suggestions for a better development resource, please direct me.
I have the source code and I'm currently working through building it and trying to just execute the shell. First of all, I decided I'd try to build it in Visual Studio .NET since it catches some previously unnoticed errors in V C++ 6.0. Here is what I have found thus far: the code compiles without error in 6.0, but in .NET it catches an improper use on an iterator, it finds a function that was defined to return a CString but actually returns a bool, and has trouble locating one file which is probably nothing more than a path being lost on conversion up to .NET. Those problems are easily fixed and I don't know that they have much affect on stability. Now, my real questions begin when trying actually debug.
I have not tried executing under VC 6.0, but I have under .NET and I am coming to problem after problem. Can somebody run litestep right after compiling with 6.0? I would like to know if the problems I'm dealing with are source code related or IDE related. It _might_ be my theme which is turning into a heavily modified version of Utterance. Guess I could try the default theme.
It seems the code is kind of picky and likes to throw unhandled exceptions. First and foremost, the stack is being corrupted when a bool is passed into a Windows API function when it should be a BOOL. It doesn't seem to have affected performance in any way but its just something I've noticed. Next, due to the lack of development documentation, I had some troubles actually getting the .rc files all set up to load my theme. What I found is litestep will throw an exception after finding an undefined variable. It seems to work ok when just running the release build, but it should probably be addressed since its showing up while debugging. It is possible the exception is surpressed in release mode and so I don't see it otherwise. I have to investigate further. My theme uses lsbox.dll and I've emailed the author to see if it's been heard of before, but I noticed that if I load up a .PNG file into photoshop 5.0, save it out, then have it load through the .box shortcut, litestep hangs and must be forcefully closed. I can't debug this yet but I'm wondering if anybody else has heard of this? My final problem thus far, and where I stopped last night, was an unhandled exception when trying to obtain the color ref of systraybghuecolor.
I'm just kind of confused that the release can run so well but have so many problems while debugging. Is it just my configuration, my theme selection, my choice to go with .NET or is this noticed by others?
-Jon
I have the source code and I'm currently working through building it and trying to just execute the shell. First of all, I decided I'd try to build it in Visual Studio .NET since it catches some previously unnoticed errors in V C++ 6.0. Here is what I have found thus far: the code compiles without error in 6.0, but in .NET it catches an improper use on an iterator, it finds a function that was defined to return a CString but actually returns a bool, and has trouble locating one file which is probably nothing more than a path being lost on conversion up to .NET. Those problems are easily fixed and I don't know that they have much affect on stability. Now, my real questions begin when trying actually debug.
I have not tried executing under VC 6.0, but I have under .NET and I am coming to problem after problem. Can somebody run litestep right after compiling with 6.0? I would like to know if the problems I'm dealing with are source code related or IDE related. It _might_ be my theme which is turning into a heavily modified version of Utterance. Guess I could try the default theme.
It seems the code is kind of picky and likes to throw unhandled exceptions. First and foremost, the stack is being corrupted when a bool is passed into a Windows API function when it should be a BOOL. It doesn't seem to have affected performance in any way but its just something I've noticed. Next, due to the lack of development documentation, I had some troubles actually getting the .rc files all set up to load my theme. What I found is litestep will throw an exception after finding an undefined variable. It seems to work ok when just running the release build, but it should probably be addressed since its showing up while debugging. It is possible the exception is surpressed in release mode and so I don't see it otherwise. I have to investigate further. My theme uses lsbox.dll and I've emailed the author to see if it's been heard of before, but I noticed that if I load up a .PNG file into photoshop 5.0, save it out, then have it load through the .box shortcut, litestep hangs and must be forcefully closed. I can't debug this yet but I'm wondering if anybody else has heard of this? My final problem thus far, and where I stopped last night, was an unhandled exception when trying to obtain the color ref of systraybghuecolor.
I'm just kind of confused that the release can run so well but have so many problems while debugging. Is it just my configuration, my theme selection, my choice to go with .NET or is this noticed by others?
-Jon