Fixes for current and Future FF

[Roger Garstang]

Every once in a while the Delete key doesn't do anything when pressed with a control selected.  I have to select the control a couple times.

INIT Function for Custom Controls isn't created automatically.  Seems since it is needed it would be logical to add it whenever a control is added or during compile if not present...maybe even link it to the control say when you right click it a window opens up with the init code...perhaps even not having it in the main source.

FRX file changes still could be improved...seems sometimes adds/deletes of resources don't commit to file till compile.

Is there/should there be a way to change the background color of a picture control?  If I change the background of my window the picture control doesn't match it.  I guess it doesn't hurt to much if it uses the ButtonFace color so it looks the same when standard colors are used, but would be nice to have other colors.  Also, for some reason the docs say LR_Shared shouldn't be used with non-standard sizes...in the future it might be nice to have a Custom option in the icon size dropdown as well as no pref and have the style default off if either are selected or detect the size of the icon and determine everything automatically along with the custom option in case we want to stretch/shrink the icon.

[Roger Garstang]

And my other options mentioned a few times before that I keep running into needing in a project:

*Additional property to set the parent of a control for things like controls in a statusbar, controls in a listview, setting a frame control as a parent and moving controls in a group...and of course being able to move them as children of another control in the IDE.

*Non-AutoButton styles for buttons/radio button/checkboxes.

[TechSupport]

Thanks Roger  Lots of work to do... I have copied your suggestions into the bug tracker so I can deal with them as FireFly3 progresses.

[Roger Garstang]

When changing the bground color of a frame control the text area of the frame goes completely black until I change the BackStyle property.  Its like the IDE doesn't redraw the new color until that property is changed???

Label Controls have the two WS_CLIP... styles.

Can't remember if I mentioned it before, but the SelText property of an Edit/Text box doesn't appear to do anything.  Could be the new way the events are handled since it isn't done with FF generated code anymore.

[Roger Garstang]

After looking at generated code, appears ff.SelText isn't set in the code when the control is created...

[Roger Garstang]

Wanted to report something that has happened for a while now and you probably already fixed in the new ways of FF3, but for some reason every once in a while either on reload of a project or after changing something in one of the many editors (Statusbar, Menu, etc) it seems things are forgotten-  Menu item checked states don't show up in compiled, but when going back in the menu editor they are there then on recompile they are back.  Statusbar is set to simple, but shows like divided until going in and back out of its editor.  Seems when one happens the other does as well like the code that sets up all the values is reading them wrong.

[TechSupport]

Hi Roger,

Better wait until FireFly 3 goes into beta testing before we deal with those design environment issues. Most (all) of the built in designers are being rebuilt from scratch. Lots(!) of old bad code in those designers that need to be fixed. It is easier for me to simply rewrite them because the internal FireFly engine has changed anyway.

[Roger Garstang]

Yeah, hence the "current and future" title.  Just making a list of things in the current to remember not to included them in the future.  And small things that are quick fixes in the mean time like the SelText which I need for a current project, etc...

[Marty Francom]

With Windows Themes turned off the problem when away.    I can live with Themes turned off,  at least 'til a solution is found.  Strange problem though.

I don't beleive it is a video card problem because each of these IBM computers have a different brand of video card.  I even went out and purchased a very high video card for 1 of the machines and the problem still persisted,  until Themes was turned off and I recompiled the program.

[Roger Garstang]

Wrong thread, but yeah, Themes seem to cause all kinds of problems.  I have an app I'm making right now that uses AVI graphics and if I turn themes on the graphic goes nuts and flickers all the time while playing.  Plus all the Tab Control Issues Themes make.

[TechSupport]

Can't remember if I mentioned it before, but the SelText property of an Edit/Text box doesn't appear to do anything.  Could be the new way the events are handled since it isn't done with FF generated code anymore.

Roger, I have uploaded a simple test program that we can work on to figure out what exactly is the problem you are seeing. The sample is at: http://www.planetsquires.com/files/Roger_SelText.zip

The example program shows the textboxes correctly highlighting the text on initial creation and then when they are tabbed into.

[Roger Garstang]

I think you are thinking backwards from what I want...in your example set SelText to False and it does the same thing as if it was set to True.  I did find that the value is in fact set...you just never set it to %FALSE since it is init to 0 by PB, and when True the value is set...but the flaw is that you assume on focus no text is selected, but for some reason the message loop for dialogs selects all on focus, so no matter what the value is set to it selects the text either by dialog or by FF code, so you need to reverse the logic and UnSelect if False and leave alone if True.  Unless it is only an XP thing...Then you'll have to include both sides in FF Code to Unselect and to Select if in other OS's it isn't selecting text on focus no matter what.

I posted source code in the other thread in Source about Coloring dropdowns.

[Roger Garstang]

Once this is fixed, I noticed you don't check for type/class of control there either, which as it stands doesn't hurt cause code isn't ran unless True, but since you'd have to Deselect Text no matter what the code would execute on other controls.  Since this could also be used in other controls like Combos, DTpickers, etc with Text Boxes in the future/now, it may be better to use 0, 1, 2 for values so 0 ignores and 1, 2 are True, False so you can add the property to other controls.  Or you could just test for the 3 classes, whatever works.

[TechSupport]

Okay, I think I see what you mean about the text being highlighted regardless of the SelText setting. I made a change to the code generator. See if the new FFengine correctly handles it.

http://www.planetsquires.com/files/Roger_SelText.zip

http://www.planetsquires.com/files/FFengine.zip

[Roger Garstang]

That Fixed it, instead of 0,0 though, do it like my code in the source with one being -1, 0 and the other being 0, -1...that way the cursor is at the end of the text instead of the beginning when not selected.