Yeah, that's a question I was about to ask. Why do the settings show 4 and 6 instead of 5 and 7. And after you mentioned, I've just did another test and it wasn't that the first time worked, but not anytime after that. It was just that it turned out, as a coincidence, that every first time I tried I was trying with an odd number (3 or 9).It actually works fine all the time with an odd number, so basically the problem is what you said, it's allowing me to set even numbers and it freaks out.Thanks a lot for addressing this!
Fixed in the 20130414-01 release; thanks for reporting!
Quote from: eduperez on 02 / May / 2013, 16:42:32Fixed in the 20130414-01 release; thanks for reporting!Awesome! Thanks a lot!By the way, is it possible for end users to create scripts, like in CHDK? I don't know if the same applies or it works differently. If it is, is Lua supported?Thanks again!
I understand why you changed 0x800000 to 0x7E0000. My question is how does it work without it?
Here is some info about "vmBaseGlobalMapInit" which I disabled to save cache-hacks: http://www.vxdev.com/docs/vx55man/vxworks/ref/vmBaseLib.html
0xAF, can 400plus catch "trash_button_released" or "jump_button_released" events? If not, check cSetSendButtonProc(&My_SendButtonToMC, 0); in my code. Could be useful for something.
I started to work on IR remote code. Right now I can make camera respond to any remote on any key but can't make it respond only on specific keys. Looks like firmware only checking for pulse width and time between pulses. Code is in remote.h:http://hostr.co/0MiULSEGLdt3
I see you have IR_Log() function, can you log all signals with it ?I mean when you press some button on a remote, can you distinguish between different remotes/buttons ?If so, this is great. If not, the enabling of all IR signals is still a good feature.
BTW, do you know what this MachineCell is and what is it's purpose ?It looks like it is for some Factory Tests ?
I took the vram_copy() routine from your code, to invert the OLC colors.It seems to work, but not when you start the camera for the first time, it draws white first, then after i force any gui update it draws black.I guess this is because we cannot detect (GUIMode == OLC_MODE) in the first moments. I will try to find a solution.EDIT3.1:I've found it... It was because at the start the camera is changing the mode for a while, to draw the animation for sensor cleaning... so the check should be:if (FLAG_GUI_MODE == GUIMODE_OLC || FLAG_GUI_MODE == GUIMODE_ACTIVESWEEP_OLC) {...}
Started by gdharmraj General Chat
Started by Foldesa General Discussion and Assistance
Started by krillik General Chat
Started by searchlight DSLR Hack development
Started by koy1 DSLR Hack development