Re: Fiji Wiki upgrade

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: Fiji Wiki upgrade

dscho
Hi all,

On Mon, 3 Feb 2014, Johannes Schindelin wrote:

> I just upgraded the Fiji Wiki (http://fiji.sc/) to a newer Wiki version.
> Hopefully few people were affected by it (the upgrade lasted about 4
> minutes, thanks to the five hours of preparation).
>
> Please let me know if you encounter a problem with it!

As suggested by Jiří Borovec I upgraded yet again so that the VisualEditor
functionality could be enabled. This allows logged-in users to edit pages
in-place, using a WYSIWYG editor.

Enjoy,
Johannes

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html
Reply | Threaded
Open this post in threaded view
|

Re: [fiji-devel] Re: Fiji Wiki upgrade

ctrueden
Hi everyone,

> As suggested by Jiří Borovec I upgraded yet again so that the
> VisualEditor functionality could be enabled. This allows logged-in
> users to edit pages in-place, using a WYSIWYG editor.

Thanks Johannes!

If, however, you are like me and find WYSIWYG web editors to be vile forces
of corruption and suffering, note that the new "Edit source" button does
what the "Edit" button used to do.

Regards,
Curtis


On Tue, Feb 4, 2014 at 10:15 AM, Johannes Schindelin <
[hidden email]> wrote:

> Hi all,
>
> On Mon, 3 Feb 2014, Johannes Schindelin wrote:
>
> > I just upgraded the Fiji Wiki (http://fiji.sc/) to a newer Wiki version.
> > Hopefully few people were affected by it (the upgrade lasted about 4
> > minutes, thanks to the five hours of preparation).
> >
> > Please let me know if you encounter a problem with it!
>
> As suggested by Jiří Borovec I upgraded yet again so that the VisualEditor
> functionality could be enabled. This allows logged-in users to edit pages
> in-place, using a WYSIWYG editor.
>
> Enjoy,
> Johannes
>
> --
> --
> Please avoid top-posting, and please make sure to reply-to-all!
>
> Mailing list web interface: http://groups.google.com/group/fiji-devel
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Fiji-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [hidden email].
> For more options, visit https://groups.google.com/groups/opt_out.
>

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html
Reply | Threaded
Open this post in threaded view
|

unexpected failure of keyboard shortcuts for zoom in a custom StackWindow

Mark Bentley
In reply to this post by dscho
Greetings,

I am experiencing an unexpected failure of the Zoom>In and Zoom>Out
default keyboard mapping as described here,
http://rsb.info.nih.gov/ij/docs/shortcuts.html , when extending a
ij.gui.StackWindow in a Plugin.  Why is it being extended, you ask?  The
plugin features several awt.Button objects added to a Panel that is then
added to the window.  So, the custom StackWindow also implements
ActionListener.  There are two sets of Buttons, each representing a
menu, each menu has a Button designed to switch back to the other menu.  
The code looks something like this...

void actionPerformed(ActionEvent e) {
     if (e.getSource() == currentPanelsSwitchMenuButton) {
         remove(theCurrentPanel);  //remove the panel currently displayed
         add(theOtherPanel); //add the other panel, both panels have
already had the buttons, listeners, etc. added.
         pack();
     }
}

The plugin operates as expected, and the buttons within each menu carry
out their correct functions, including the 'menu switching' mentioned
above, BUT upon switching menus the keyboard shortcuts for zoom stop
working.

Now, AFTER doing a menu switch and thus breaking the zoom shortcuts, the
shortcuts can be restored by manually clicking the magnification tool in
the ImageJ main window.  Once that has been clicked everything is back
to normal; the shortcuts work as they should even when the mag tool is
no longer selected.  BUT a 'menu switch' will break the zoom keys again
until the Magnification tool is manually selected again.  The users of
the plugin switch menus frequently, and this problem is really slowing
them down.

I have already tried including a 'dirty fix' like the one below:

private void fixZoom() {
     String currentTool = IJ.getToolName();
     IJ.setTool(Toolbar.MAGNIFIER);
     IJ.setTool(currentTool);
} /* end fixZoom() */

where fixZoom() is called after pack() in actionPerformed.  Also, just
calling IJ.setTool(Toolbar.MAGNIFIER) and then expecting the user to
select their desired tool afterwards, an even simpler 'half fix,' does
not work.  It seems that the user must actually CLICK ON the mag tool or
CLICK WITH it at least once to restore the keyboard shortcuts.

Any suggestions?

Thank you all,

Mark Bentley
[hidden email]

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html
Reply | Threaded
Open this post in threaded view
|

Re: unexpected failure of keyboard shortcuts for zoom in a custom StackWindow

Michael Schmid
Hi everyone,

the phenomenon of the zoom shortcuts sometimes not active after a while of working with ImageJ seems to be a more common one.
Occasionally, it also happens to me (Mac OS X 10.6, Java 1.6.0.65; all ImageJ versions since years).  I have not found a specific action that triggers it.

It is interesting that in this case also a macro that I have for zooming in stops working. The macro moves the image up on the screen to allow ImageJ use a larger area for the image:

//shifts the image if this would allow to have a larger area
macro "Zoom In [n+]" {
  zoom = getZoom();
  getLocationAndSize(x, y, width, height);
  if (width*1.01>getWidth()*zoom && (height-screenTop)*1.01>getHeight()*zoom && width*1.33<screenWidth && height*1.33<screenHeight) {
    if (x+1.51*width > screenWidth)
      x = maxOf(0, screenWidth-1.51*width);
    if (y+1.51*height > screenHeight)
      y = maxOf(screenTop, screenHeight-1.51*height);
    setBatchMode(true);
    setLocation(x, y, width+1, height+1); //'+1' avoids rounding-down errors
  }
  run("In");
  setBatchMode(false);
}

Would be great if someone could find out why this happens (so one can fix it).

Michael
________________________________________________________________
On Feb 5, 2014, at 16:54, Mark Bentley wrote:

> Greetings,
>
> I am experiencing an unexpected failure of the Zoom>In and Zoom>Out default keyboard mapping as described here, http://rsb.info.nih.gov/ij/docs/shortcuts.html , when extending a ij.gui.StackWindow in a Plugin.  Why is it being extended, you ask?  The plugin features several awt.Button objects added to a Panel that is then added to the window.  So, the custom StackWindow also implements ActionListener.  There are two sets of Buttons, each representing a menu, each menu has a Button designed to switch back to the other menu.  The code looks something like this...
>
> void actionPerformed(ActionEvent e) {
>    if (e.getSource() == currentPanelsSwitchMenuButton) {
>        remove(theCurrentPanel);  //remove the panel currently displayed
>        add(theOtherPanel); //add the other panel, both panels have already had the buttons, listeners, etc. added.
>        pack();
>    }
> }
>
> The plugin operates as expected, and the buttons within each menu carry out their correct functions, including the 'menu switching' mentioned above, BUT upon switching menus the keyboard shortcuts for zoom stop working.
>
> Now, AFTER doing a menu switch and thus breaking the zoom shortcuts, the shortcuts can be restored by manually clicking the magnification tool in the ImageJ main window.  Once that has been clicked everything is back to normal; the shortcuts work as they should even when the mag tool is no longer selected.  BUT a 'menu switch' will break the zoom keys again until the Magnification tool is manually selected again.  The users of the plugin switch menus frequently, and this problem is really slowing them down.
>
> I have already tried including a 'dirty fix' like the one below:
>
> private void fixZoom() {
>    String currentTool = IJ.getToolName();
>    IJ.setTool(Toolbar.MAGNIFIER);
>    IJ.setTool(currentTool);
> } /* end fixZoom() */
>
> where fixZoom() is called after pack() in actionPerformed.  Also, just calling IJ.setTool(Toolbar.MAGNIFIER) and then expecting the user to select their desired tool afterwards, an even simpler 'half fix,' does not work.  It seems that the user must actually CLICK ON the mag tool or CLICK WITH it at least once to restore the keyboard shortcuts.
>
> Any suggestions?
>
> Thank you all,
>
> Mark Bentley
> [hidden email]
>
> --
> ImageJ mailing list: http://imagej.nih.gov/ij/list.html

--
ImageJ mailing list: http://imagej.nih.gov/ij/list.html