Forum Replies Created
-
Posts
-
Hi Ray,
Here are settings for both FormState & Ini components:
So all I ever do with this setup is connect the FormState to the INI file and give the Section a unique name. I’ve done the exact same on many other forms and they all work. Most of the other forms in my project connect their own FormState components to the INI file in this main form and work correctly.
This sounds like another one of those oddities in 10.3, like I’ve ‘unearthed’ before, that work fine in some projects and not in others, with no discernable difference (like the VersionInfo, or retaining the Language settings). I only hope 10.4 has addressed these issues.
I can add something, which might help … I run with 3 screens on my development PC. I have had the main form set to ‘Position = poScreenCenter’ – which I’m thinking now may be the screen centre of the 3 screens together, rather than the screen centre of my main (central) screen, as it first appears tp the left of my main screen.
However, it doesn’t make much difference what the ‘Position’ setting is, the main form starts somewhere else and eventually goes to where the FormState component tells it to.
Ray,
HaHa, wondered if you had missed it, but thought you were ay too busy doing other stuff to get round to it. Many thanks.
Ray,
Many thanks, as ever. I’m building up a list of ‘simple’ examples of how to use your controls ‘properly’, so one day I won’t need to ask you 🙂
Hi Ray,
I’m using 10.4 with the update, Windows 10 (all at latest update level), and all the Raize components downloaded and installed from GetIt when they were available a week or so ago (the components say they are v6.2.3). So can’t be more up to date with anything.
I tried on a different project and only get 3 lines of help on that as well.
Ray,
Something interesting. I removed your FormState component from the Main form and added some INI code, which reads and writes to the INI file. Tracing through debug all 4 positions were read correctly, and assigned to the correct properties on the form. When closing, the correct form positions are written back to the INI file – so all that seems to work as it should.
However, what happens when I open the application now is that the Top and Left values are ignored but the height and width properties are used! Top and Left always revert (on my screen) to 52 and 52, no matter what the values are in the INI file.
As a point of maybe interest, in the Forms setting this is the only visual form that is auto-created (I also auto-create a data-module and some report forms). Could that have a bearing I wonder.
Hi Ray,
From this form there is no code in the OnClose or OnShow events, but I have the following code in the OnCreate event:
Procedure TfMain.FormCreate(Sender: TObject);
var
cStyle: String;
begin
lb.Height:= 100; lb.Width:= 300;
lb.Items.AddStrings( TStyleManager.StyleNames );
//get last used Style from INI file …
cStyle:= INI.ReadString(‘STYLE’, ‘LastUsedStyle’, ‘Windows10’);
TStyleManager.SetStyle( cStyle );
end;I commented this code out and tried again, but no change. The read is done, but it doesn’t write back any changed position. This is in 10.4 as well, so no ‘fix’ there.
When I’ve time I’ll re-create this mainform ensuring the formstate is saved during the process, then replace the existing main form. It’s another of those ‘Delphi things’ I think, not major just an annoyance. Certain it’s nothing to do with your component, but thanks for thinking about what it could be.
Ray,
Enabled is set to True, FormState works on all other forms in project but this one.
What I did was add this:[MAINFORM]
Maximized=0
Left=824
Top=209
Right=1272
Bottom=880
Saved=1… to the Ini file, and the Main form does obey these positions, so it is reading the INI file on start up. It also writes new values to the INI file as I move the forms about. All except the Main form, though. I can move the Main form about and exit and the time on the INI file doesn’t change.
Because it is the Main form, and just a starting place to do other things, I’ve set the Window Position to poDeskTopCenter, so this issue doesn’t really affect me now (and hopefully not my Users of this app either). Just a curious thing. I was going to rebuild the Main form from scratch, checking the position of the new form was saved correctly but not sure the extra work doing this is worth while.
I’ll wait until I’ve migrated it to 10.4 and see if that makes any difference.
Agree, no apology needed, we can see you are just as frustrated with Embarcadero as we users are. Let’s hope this is a lesson they learn on any future releases.
Hi
Just seen that these are now available in GetIT for Sydney, version 6.2.3, Just downloading now. Whoopee!
Might be worth pointing out that the files in the RAR seem to be from a much earlier version of KSVC. The ‘What’s New’ documentation talks about support for XE2. The ReadMe.txt mentions ‘Minimum requirements’ of 10.2 Tokyo.
It may be that the components are the very latest, but if they aren’t, even though they could well install into 10.4 I think some of the components may well have been improved since then and could cause issues when porting over to 10.4.
Personally, while I welcome this ‘unofficial support’ I’m going to hang on for a little while until some definite answer comes out of E.
