Bugs concerning keyboard shortcuts plus one suggestion

Hi,

I downloaded Filter Forge because I wanted to try it out on a (personal) project of mine. During this project I noticed that some keyboard shortcuts are not behaving as expected:

1) For example Cmd+1 to Cmd+6 adjust the Anti-Aliasing Samples settings in "Filter > Anti-Aliasing" but those shortcuts don't show up in the menu beside the setting they are supposed to change to.

2) Probably related, I then tried to use the global overide ability of Mac OS X which you can find in the System Settings.app > Keyboard & Mouse > Keyboard Shortcuts tab.
Under "Shortcuts For Other Applications" I specified an override by adding Filter Forge to the drop down list and for example setting the "Show Original" menu item to Cmd+Ü (thats a German u umlaut).
Switching back to Filter Forge the new shortcut this time displays in the menu next to "Show Original" (as it should) but Filter Forge doesn't reckognize it. It only reacts when pressing the default shortcut of Cmd+R.

Expected behaviour was that it will now trigger "Show Original" by pressing Cmd+Ü.
Actual behaviour: Filter Forge ignores global keyboard settings.

My personal opinion (and that of many of my professional work collegues) is that, being a good Mac citicen app, it should probably support the global keyboard shortcut override as this helps quite a lot with taming applications that have default keyboard shortcuts layed out for US keyboards.

3) On topic of being a well usable Mac app I have a litle suggestion:

Please make the filter category browser pane (left side) resizable.
And more importantly, please make the preview pane on the left side of the filter editor resizable. I have lost count how many times me and my collegue have tried to subconciously resize that pane while trying out a few quick ideas. Of course this is not high priority, it is irritating at most.

I will conclude with saying that we were both impressed with the current state of Filter Forge for the Mac and that we will continue to pay close attention to its process of development.

Kind Regards,

A. Berg
Freelance Compositor, Stereographer and CGI-Artist.

PS:

System Specs:

Mac Pro 8-core
12 GB RAM
4 TB HD
nVidia GeForce 8800 512 MB RAM
Mac OS X 10.5.6 German
Filter Forge 1.015


EDIT:

Encountered a reproducable crash while working in the component editor:

Steps:

1) Start FF.
2) Download the "Corrugated Steel" filter preset.
3) Edit it in the filter editor
4) Activate or click on the Perlin Noise component highest up in Y axis on the canvas.
5) Click the link "Mapped with Profile Gradient".
6) A crash occurs (three times now for me).

I'll attach the info reported by the Apple crash reporter.

EDIT:

Well, seems I can't... Please let me know how I can send it to you if you need it...


Here's a short snippet:

Process: Filter Forge [24813]
Path: /Applications/Filter Forge/Filter Forge.app/Contents/MacOS/Filter Forge
Identifier: com.FilterForge.FilterForge
Version: ??? (1.0)
Code Type: X86 (Native)
Parent Process: launchd [538]

Date/Time: 2009-02-04 02:12:13.957 +0100
OS Version: Mac OS X 10.5.6 (9G55)
Report Version: 6

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000c5b46a23
Crashed Thread: 0

Thread 0 Crashed:
0 com.FilterForge.FilterForge 0x0059a0ef XFW::Mixins::TypeNameIdentifiable::get_object_description() const + 33
1 com.FilterForge.FilterForge 0x0040faed Controls::Control::get_handle() const + 69
2 com.FilterForge.FilterForge 0x00411015 Controls::Control::is_enabled() const + 27
3 com.FilterForge.FilterForge 0x00416b75 Controls::Control::on_window_proc(Controls::MessageEvent&) + 7503
4 com.FilterForge.FilterForge 0x0043e93d Controls::Form::on_window_proc(Controls::MessageEvent&) + 1233
5 com.FilterForge.FilterForge 0x0040dcfc Controls::Control::process_event(void*) + 26
6 com.FilterForge.FilterForge 0x00594b56 XFW::Kernel::process_function(void (*)(void*), void*, std::auto_ptr<XFW::Exception>*, bool) + 50
7 com.FilterForge.FilterForge 0x0041045b Controls::Control::events_handler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 103
8 com.apple.HIToolbox 0x94200143 DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1181
9 com.apple.HIToolbox 0x941ff57d SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 405
10 com.apple.HIToolbox 0x9421bed2 SendEventToEventTarget + 52

Hi GMM,

Thanks for the reply. Mentioning that 3) is a feature is interesting. Can you explain the idea behind supporting this feature?