SiComponents Home Page SiComponents Forums
Here you will be able to get help and share your experience
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Two problems

 
Post new topic   Reply to topic    SiComponents Forums Forum Index -> TsiLang Components Suite
View previous topic :: View next topic  
Author Message
Thrillhouse



Joined: 12 Jan 2010
Posts: 14

PostPosted: Mon Jan 24, 2011 6:16 am    Post subject: Two problems Reply with quote

Hello again.

I have two things to ask about today, the first on behalf of the superior:

When there are multiple projects with forms within our single C++ Builder6 project group, can we import from and export to a single file from all projects in the group at a time?

Now for my question:

We use at least two forms in our application which have other forms embedded in them. As a result, the embedded forms cannot be assigned a TsiLangLinked object, as we then receive errors about being unable to have two TsiCustom objects on the one form. Is there a way to correctly process and translate the embedded forms using this tool?

Looking forward to hearing back from you.
Back to top
View user's profile Send private message
isiticov
Site Admin


Joined: 21 Nov 2002
Posts: 2102

PostPosted: Tue Jan 25, 2011 3:12 pm    Post subject: Reply with quote

Hello,

No, for all project at a time it is not possible to load/export translations. You can only open TsiLang Expert activate the needed project in Project Manager and then use Load Project in TsiLang Expert. This will be needed for all projects in a group.
Could you please specify what do you mean under "embedded"? Do you use frames or place in inside another form at run-time? In case of frames usage just place a TsiLang on the frame, in case of placing a form at run-time just place TsiLang on the from beign embedded at design time. The main pint is that OWNER of the TsiLang shall be different. So if you place formA onto formB then there should be 2 TsiLang components TsiLang-fromA and TsiLang_formB. So later when you create these forms at run-time there won't be the mentioned error message.
Back to top
View user's profile Send private message
Thrillhouse



Joined: 12 Jan 2010
Posts: 14

PostPosted: Sun Jan 30, 2011 10:20 pm    Post subject: Reply with quote

I'll try what you've suggested with the embedded forms when the opportunity presents itself, and get back to you.
Back to top
View user's profile Send private message
Thrillhouse



Joined: 12 Jan 2010
Posts: 14

PostPosted: Mon Jan 31, 2011 5:00 am    Post subject: Reply with quote

That didn't seem to work, though I may have misunderstood the suggestion. It's still giving the same error:


Only one TsiCustomLang component per Form/DataModule allowed!

when we try to put the forms together. Is there anything else you can suggest?
Back to top
View user's profile Send private message
isiticov
Site Admin


Joined: 21 Nov 2002
Posts: 2102

PostPosted: Mon Jan 31, 2011 12:59 pm    Post subject: Reply with quote

I mean something like the following:

TformA * formA = new TformA(Application);
TformB * formB = new TformB(Application);
TsiLang * SI = new TsiLang(formB);
fromB->Parent = formA;
formB->Top = 10;
formB->Left = 10;
fromB->Show();

In this way the fromB will be the owner of the SI (TsiLang) component.
Back to top
View user's profile Send private message
Thrillhouse



Joined: 12 Jan 2010
Posts: 14

PostPosted: Wed Feb 02, 2011 5:20 am    Post subject: Reply with quote

My code noob-iness is coming out now. If this is happening at runtime, how are we populating the translations for both forms?
Back to top
View user's profile Send private message
isiticov
Site Admin


Joined: 21 Nov 2002
Posts: 2102

PostPosted: Wed Feb 02, 2011 8:36 am    Post subject: Reply with quote

Now it is my turn Laughing To populate translations it would be easiest to do this at design-time. But then how do you embedd forms at design-time? If you're able to embedd them at design-time then just place a TsiLang on embedding form before the embedding and then it will be the owner of this TsiLang.
If you do the embedding at run-time the way described above then there is solution like the following:
1. At test build add a code to save the TsiLang created at run-time to the file, like:
siLang_formB->BuildLists();
siLang_formB->SaveAllToBinaryFile('some.sib');
2. After editing the SIB file add a code to your fina build that will load the translations from this file to the TsiLang.

If all of these still non-applicable then I would ask you for the sample project that demonstrates your problem and then we will try to provide you with the solution.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   Reply to topic    SiComponents Forums Forum Index -> TsiLang Components Suite All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by p h p B B  © 2001, 2005 p h p B B  Group