Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - a1ex

#11426
There is also rec_notify_trigger - called when Canon firmware announces "recording" - shoot.c, PROP_HANDLER(PROP_SHOOTING_TYPE).

Or you may want to enable it when you send the button press.

Polling is used to keep the LED on, if some other events happen to turn it off.
#11427
Another thing to keep in mind. Many users are working outside in full sunlight - a strong contrast is needed so they can read the menu. Light gray on dark gray may not be that easy to read in difficult conditions.

The darkened gray may be useful to suggest edit mode - when you only change one option, not navigate around.
#11428
General Development / Re: ARM Toolchain
July 03, 2012, 04:59:13 PM
Great, so there is now an easy way of building ML!
#11429
http://magiclantern.wikia.com/wiki/StateObjects and state-object.c - no need to reinvent the wheel.
#11430
General Development / Re: ARM Toolchain
July 03, 2012, 04:00:53 PM
#11431
For shutter count: I think Indy found the property data in ROM at ff80000.

http://groups.google.com/group/ml-devel/msg/831b0c9ee8765fca
#11432
Two problems I see with that design:
- tiny font: it looks OK on large screen, but probably too small on camera.
- displaying all possible choices is not always easy (and feels cluttered IMO).
#11433
General Development / Re: ARM Toolchain
July 03, 2012, 03:35:19 PM
If you can force the arm-toolchain to build a 32-bit compiler, please post the patch so I can commit it.
#11434
Done.
#11435
Looks like if you hijack EMState you will get all the info you need.

You only need to intercept emDeliverMulticastEvent.

http://a1ex.bitbucket.io/ML/states/5Dc-alt/sm3.htm

Look in state-object.c and print the arguments you receive via the state object spy function.
#11436

ff8ac3e8: '[FSS] fssSW1On'
ff8b735c: '[EM] Already SW1ON'
ff8b7370: '[EM] Already SW1OFF'
ff8b7450: '[EM] emDeliverMulticastEvent : SW1ON'
ff8b7478: '[EM] emDeliverMulticastEvent : SW1OFF'
ff9f5db8: '[RapiSW]  CompRapiActive SW1'


or with memspy, though I don't know how you can run this with display off. Maybe print the results to log file?

In dryos, it's somewhere around main_ctrl_task data structures.
#11437
In this case, I'd say this: you can come up with a design that requires max 255 colors (as one of them has to be transparent), and if it's worth the effort, I think I'll be able to implement it in the next few months. There are no restrictions about what colors are used. There will be a ugly flicker when you change the palette (because ML menu sits on the top of some Canon menu, and you can often see both of them figthing on redraws) - that's the main technical issue.

Semitransparent entries seem possible too, though I don't fully understand how to setup them.

Some of the previous work on this: http://groups.google.com/group/ml-devel/browse_thread/thread/d1e273de2490f5e5.
#11438
The first 80 entries are always the same (in all cameras, all modes used by ML). So, grayscale is only required if we want to use gradients (which you said it's optional).
#11439
Calling Canon's ChangeColorPalette is not safe (causes ERR70 if called at the wrong time).
#11440
The other entries are camera- and dialog-specific, and I prefer not to change them. It is possible, but it requires a few ugly hacks which I'd rather avoid.
#11441
If it works, let me know so I can enable it again. Make sure you use the latest source code (hg pull).
#11442
There is already a proportional font used by ML - the one for menu headers.

Switching to proportional requires refactoring more than half of menu entries - not quite straightforward. But if the design is worth it, we may consider it for 2.4 or 2.5. But for now we'll leave it unchanged.

This is the color palette that can be used - actually only the first 80 entries:

http://magiclantern.wikia.com/wiki/File:Palette.jpg

so grayscale gradients are possible.
#11443
General Development / Re: Compiling on a Mac
July 03, 2012, 11:25:31 AM
It's some problem with building the docs. Not sure what causes it, but I think it can be safely ignored.
#11444
Yes, the code base is the common to all cameras (evolving chronologically) and there are small user interface changes for each camera (what features to include etc).

Nobody has leaked the sources, but... http://magiclantern.wikia.com/wiki/Decompiling ;)

Interesting that the backend API wasn't changed from years (like file I/O, semaphores, properties, dialog API) - these functions work well from 5Dc (2005) to 5D3 (2012) :)

This thread should probably split.. it went a bit offtopic, no?
#11445
Feature Requests / Re: Multilanguage and nice GUI
July 02, 2012, 05:03:02 PM
See http://www.magiclantern.fm/forum/index.php?topic=1130.msg1827#msg1827 .

The code is not yet ready for translation.
#11446
I think the 60D and 600D have almost identical Canon playback code, 5D2/50D/500D are very similar among them, and 550D is somewhere in between but closer to 60D/600D.
#11447
Probably the top-right point is not at the middle point between the top and the right ones. Does it zoom close to that point, or far away?
#11448
Good, so it's just like 60D/550D. I must have copied the 5D2 values by mistake.
#11449
In this case, write down the values of IMGPLAY_ZOOM_POS_X and IMGPLAY_ZOOM_POS_Y for the following cases:
1) center (just press zoom in and print the values)
2) left AF point (manually zoom all the way in to something focused with that AF point)
3) top AF point (same as 2)

Those numbers will need to be changed in consts.h.
#11450
To show something on screen, I add a bmp_printf line in debug_loop_task (there' one already commented).

Zoom on AFP is OK after all?