Menu

#106 Guiguts 1.0.25: "Fixup Page Separators" breaks height of Search box

v1.0.26
open
nobody
None
5
2014-04-27
2013-12-01
No

"Fixup Page Separators" causes the Search-and-Replace box dimensions to become invalid.

This is what's in setting.rc after "Fixup Page Separators" is used (in Auto-advance, 80%, or 99%):

$positionhash{searchpop} = '587x166+68+-3';

This is what it's supposed to be:

$positionhash{searchpop} = '+138+19';

Discussion

  • Charlie Howard

    Charlie Howard - 2013-12-01

    This happens when the Search-and-Replace window is open during "Fixup Page Separators." In one test, it did not happen when that window was closed during the operation.

     
  • Anonymous

    Anonymous - 2014-04-26

    I can't reproduce this, you probably need to give a bit more detail about what you're doing, and what file you're doing it on.

     
  • Charlie Howard

    Charlie Howard - 2014-04-26

    The problem occurs when the top of the Search box is above the top of the screen when "Fixup Page Separators" and various other operations occur. The non-programming way to fix it is to move the box down so it's entirely on the screen, then close it. The next time a Search is initiated, the problem will be gone.

     
  • Anonymous

    Anonymous - 2014-04-26

    Still no luck here. I also can't move the Search window above the screen - it immediately jumps down to line up with the top of the screen. What are your steps?
    1. Open a file with some page separators/empty file?
    2. Search > Search & Replace
    3. Move Search & Replace window so the top is outside of the screen?
    4. Tools > Fixup Page Separators
    5. Do you need to run anything within that window, or does the Search window go bad as soon as you launch the other window?
    How can you see that there's a problem - does the Search window move or resize itself, or do you close and reopen either the window or Guiguts before you see there's a problem?

     
  • Anonymous

    Anonymous - 2014-04-26

    Tested just now, using the simplified procedure below, and got the error in three consecutive tests:

    1. Open a file;
    2. Ctrl-F;
    3. Move Search box to top of screen so that it's topmost edge is barely (as in "accidentally") above the top of the display area;
    4. Use it (maybe not needed, but why else would it be open?);
    5. Close Search;
    6. Ctrl-F to reopen Search;
    7. Switch Search box to Multi: the bottom of the Search box is not visible, and setting.rc has a negative value similar to what's shown in my original post.

    As mentioned in one of my follow-up posts, when it does happen, moving the defective Search box down so it's entirely on screen, then closing/reopening it, fixes the problem, because GG has saved its new position, which has valid values. The fix works whether single or multi is selected when the defective Search box is closed.

    Also, moving it so that the top edge is off-screen does not cause it to jump back down: it stays where it was put, even when reopened after being closed.

     

    Last edit: Charlie Howard 2014-04-26
  • Anonymous

    Anonymous - 2014-04-27

    I can get it now. There's a Windows Control Panel setting that must be switched on for this to happen. When it's off, it isn't possible to move the search window out of the screen in step 3.

    Control Panel > Ease of Access Center > Make the mouse easier to use > Prevent windows from being automatically arranged when moved to the edge of the screen

     

Anonymous
Anonymous

Add attachments
Cancel





Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.