PlanetSquires Forums

Support Forums => Other Software and Code => Topic started by: Brian Chirgwin on October 15, 2013, 12:58:21 PM

Title: Simple Feature Requests
Post by: Brian Chirgwin on October 15, 2013, 12:58:21 PM
. Accelerator keys on the Find Dialog -ALT - F for find.
. Accelerator keys on the Replace window - ALT F for find next. ALT-R on Replace.
. When adding code from the Function Library add $CRLF (each function on it's own line). Many times while I am there I add the functions I know I need and then work on the parameters and have to add the CRLF in manually.

I think the above would take about 15 minutes to provide (if that), but improve greatly improve productivity with the IDE.
Title: Re: Simple Feature Requests
Post by: David Kenny on October 15, 2013, 02:36:07 PM
At first glance I thought you meant to launch the dialogs (Ctrl-F and Ctrl-R respectively).   :P

Just wanted to point out that the "Find Next", on both dialogs, is the "default" button and responds to the "Enter" key. While that doesn't take care of the "Replace" you requested, it is even easier than Alt_F to use.

I can see the need for CRLF on your third bullet.  But I would think that it an "Add CRLF" checkbox (or some other way of giving a choice) on the Funtion Library Dialog might be preferable. That way others are not forced to do things the way we might like.

David
Title: Re: Simple Feature Requests
Post by: Brian Chirgwin on October 15, 2013, 03:25:41 PM
No, not launch the dialogs for the buttons on the dialogs. I agree now that I read it, it could suggest that. Of course, there are already shortcuts on the menu items to bring up the dialogs. I've used enter and space before to execute the button having focus. Both these keys though mess up code when the find/replace dialog loses focus.

I agree on a check box for the Add CRLF could be useful. I think most of the time it would be checked. Of course, until I use it I'm not sure. I know most times I want the commands on separate lines or maybe I just notice it then :)

Title: Re: Simple Feature Requests
Post by: David Kenny on October 15, 2013, 04:03:38 PM
QuoteBoth these keys though mess up code when the find/replace dialog loses focus.
I'm not sure the find/replace dialogs would receive the Alt_F and Alt_R once they lost focus. For the same reason the enter and space "mess up code".  FF would also have to support those two accelerator keys, then have to check if either dialog is active and forward them?
Title: Re: Simple Feature Requests
Post by: Brian Chirgwin on October 15, 2013, 04:19:14 PM
Alt F in the editor wouldn't do harm to code. Alt R wouldn't either. Space and Enter do.


Title: Re: Simple Feature Requests
Post by: David Kenny on October 15, 2013, 05:25:33 PM
Sorry Brian, I didn't mean to imply that they would.  Just talking about what dialog would get the input.  You pointed out that the Space and the Enter "mess up code".  That simply means that FF custom editor is getting those keystrokes, not the Find/Replace dialogs. ;)

Seems to me, that to implement what you want, the main FF dialog would have to forward them on.
Title: Re: Simple Feature Requests
Post by: Elias Montoya on October 15, 2013, 09:41:18 PM
 Firefly is great, i almost feel bad for asking for more... but since we are on this...
I dont know if these requests are simple but here i go...


;D ;D ;D

Title: Re: Simple Feature Requests
Post by: Eddy Van Esch on October 16, 2013, 08:44:18 AM
I will add another:
Sometimes a project contains 2 or more forms that are about 90% the same.

You can design the first form, do 'Add Form' and add the first form again into the project in order to make the 10% modifications. Except, FF gives a warning saying that this 2nd forms name is identical to another form in the project, resulting in naming conflicts. Correct.

You can take the first forms .frm file and edit it in some editor (Notepad) to search-and-replace the first forms name and change it into another name (also changing it in the control ID's and handles).
FORM1_WM_CREATE becomes FORM2_WM_CREATE,
FORM1_COMMAND1_BN_CLICKED becomes FORM2_COMMAND1_BN_CLICKED
HWND_FORM1_COMMAND1   -->  HWND_FORM2_COMMAND1
IDC_FORM1_COMMAND1  -->  IDC_FORM2_COMMAND1, etc
(I'm sure you get the picture :) )

Now, it would be great if FF could handle this itself.
If the user tries to add an existing form into the project, let FF give a warning:
"Attention, the project already contains this form. Do you want to add the form under a new name?" <YES> <Cancel>

If the user clicks YES, FF asks the new form name and changes all the old form name references into the new one.
Thanks for considering this.

Kind regards