PCL: ImageInspection > AberrationInspector

[NKV]

Hi,

The module do same as script version:

This module generates a n x n panel mosaic of subsections of a view.
Subsections are organized along horizontal and vertical bands across the view, including its corners, edges and central areas.

+ module can be applied to ImageContainer.
+ easy run via Alt+S.

Best regards,
Nikolay.

Source Code v1.1.2
bin Linux64
bin Win64

[Enzo De Bernardini]

Works perfect in W32. Thanks!

Best,

Enzo.

[Nocturnal]

Nice work Nicolay! PCL has a steep entry barrier but it's certainly worthwhile.

[Yuriy Toropin]

Win x64 module. b0002

Works fine under Win7 x64 Ultimate SP1.
Thanks a lot!

[Juan Conejero]

Hi Nikolay,

Hmmm, I'm afraid Ctrl+A isn't a good idea here. I was thinking on using this key for the AutoSTF feature, which has been requested recently by many users. Sorry...   

[NKV]

I'm afraid Ctrl+A isn't a good idea here.

What about Alt+S ?

[Juan Conejero]

What about Alt+S ?

That would be fine; I can't see any conflicts. You might consider allowing the user to select a custom key combination. This would require reimplementing MetaProcess::CanEditPreferences() and MetaProcess::EditPreferences().

[NKV]

What about Alt+S ?

That would be fine; I can't see any conflicts.

Done. 
See post #1.

[NKV]

You might consider allowing the user to select a custom key combination.

I can define ComboBox via code:

Code: [Select]

   KeyModifier_ComboBox.AddItem( "Shift key" );
   KeyModifier_ComboBox.AddItem( "Control key" );
   KeyModifier_ComboBox.AddItem( "Alt key" );
   KeyModifier_ComboBox.AddItem( "Space bar" );
   KeyModifier_ComboBox.AddItem( "Meta key (Mac OS X)" );Also I can define Array and manipulate via "Control::OnKeyPress".

 Juan, can you show me more elegant way to populate "name" and "value" of KeyModifier and KeyCode?

[NKV]

allowing the user to select a custom key combination

But, how to check conflict with other PI modules?
I mean: If user chose "Ctrl+A" in my module - it will conflict with your AutoSTF.

How to GetAccelerator for all PI modules?

[Juan Conejero]

How to GetAccelerator for all PI modules?

You cannot. You have to leave this responsibility to the user. If she defines a keyboard combination that is already being used by another module or the Core application, the combination in question will become ambiguous and will cease to work.

Hopefully we'll have this feature in PCL 2.0.

[Juan Conejero]

can you show me more elegant way to populate "name" and "value" of KeyModifier and KeyCode?

Actually... no I would do it exactly the same way you're doing: populate a ComboBox item by item. It isn't too much code (about 30 ComboBox::AddItem() calls), and if you use PCL symbolic constants (KeyCode::A, KeyCode::Zero, etc.) your code will be compatible with future PCL versions.

[NKV]

You have to leave this responsibility to the user.

I think it's very dangerous way... because 99% PI users don't familiar with current PI keyboard combination. 

Anyway, next version b0007: Now possible to store current settings permanently.

[Nocturnal]

I added the ability to store settings to my debayer module. I think it should be a standard feature on all modules. You can save all manner of fonts and colors with almost absurd detail but you can't save preferences for most of your processes. Sure you can save processes as psm files but that's not the same.

[Alejandro Tombolini]

Anyway, next version b0007: Now possible to store current settings permanently.

Hi Nikolay, Thank you for this tool!

The setting are saved in the module, but they do not have effect when Alt+S. The previous ones remain.

Saludos. Alejandro.