i have build cegui 7.0 source code and all samples successful, but failed initialize a new instance because the follow error:
LDR: LdrpWalkImportDescriptor() failed to probe ..\CEGUI\CEGUI-0.7.1\CEGUI-0.7.1\bin\CEGUIBase_d.dll for its manifest, ntstatus 0xc0150002
And i have installed the netframework compents and the vs2005 sp1,but cannot solve this problem, i wish you give some suggestions to me, TKS!
7.0 Sample run failed
Moderators: CEGUI MVP, CEGUI Team
- CrazyEddie
- CEGUI Project Lead
- Posts: 6760
- Joined: Wed Jan 12, 2005 12:06
- Location: England
- Contact:
Re: 7.0 Sample run failed
Did you use the correct dependency package? Other than this, I have no ideas a all.
CE.
CE.
Useful Links: Forum Guidelines | Documentation | Tutorials | HOWTO | Videos | Donate to CEGUI | CEGUI Twitter
Re: 7.0 Sample run failed
thanks a lot! I got it
Another question is 7.0 support embed image into string ,could you show a simple sample ,i'm sorry because this is a Rookie
Another question is 7.0 support embed image into string ,could you show a simple sample ,i'm sorry because this is a Rookie
- CrazyEddie
- CEGUI Project Lead
- Posts: 6760
- Joined: Wed Jan 12, 2005 12:06
- Location: England
- Contact:
Re: 7.0 Sample run failed
I'll try and force myself to write a tutorial for this sometime soon - but such things are not easy
To embed an image, you use the 'image' tag, and set it's value using the same format you do for image properties in layouts and such. So, for example, to embed a TaharezLook MouseArrow image the tag is:
To embed and image named "MyImage" from the image set named "CustomImageset" you would use:
and to combine that with some normal text, the final string would look something like:
Note that all the tags currently supplied with the built in parser are of the form:
and <value> is always contained within single quotes.
HTH
CE.
To embed an image, you use the 'image' tag, and set it's value using the same format you do for image properties in layouts and such. So, for example, to embed a TaharezLook MouseArrow image the tag is:
Code: Select all
[image='set:TaharezLook image:MouseArrow']
To embed and image named "MyImage" from the image set named "CustomImageset" you would use:
Code: Select all
[image='set:CustomImageset image:MyImage']
and to combine that with some normal text, the final string would look something like:
Code: Select all
"This is some text with an embedded image, [image='set:CustomImageset image:MyImage'] using the CEGUI formatting tags."
Note that all the tags currently supplied with the built in parser are of the form:
Code: Select all
[<name>='<value>']
and <value> is always contained within single quotes.
HTH
CE.
Useful Links: Forum Guidelines | Documentation | Tutorials | HOWTO | Videos | Donate to CEGUI | CEGUI Twitter
Re: 7.0 Sample run failed
i try it,and find it worked at satictext 、falbutton etc, all these components have the textcompoent in looknfeel,
but it cannot work at editbox、multilineeditbox because these compents have not the textcompoent property,
so the function Renderedtextstring->draw() is Invalid, and the compents which was appended on the renderedstring
of the window should not be rendered, can you tell me why, may be i have a wrong understand of the conception , TKS!
but it cannot work at editbox、multilineeditbox because these compents have not the textcompoent property,
so the function Renderedtextstring->draw() is Invalid, and the compents which was appended on the renderedstring
of the window should not be rendered, can you tell me why, may be i have a wrong understand of the conception , TKS!
- CrazyEddie
- CEGUI Project Lead
- Posts: 6760
- Joined: Wed Jan 12, 2005 12:06
- Location: England
- Contact:
Re: 7.0 Sample run failed
Hi,
It has nothing to do with looknfeel or TextComponent or anything else. The fact that the tags do not work in Editbox type widgets is by design because by their nature the text of these controls are editable by the user and allowing the tags to function therein would be a disaster in the making.
CE.
It has nothing to do with looknfeel or TextComponent or anything else. The fact that the tags do not work in Editbox type widgets is by design because by their nature the text of these controls are editable by the user and allowing the tags to function therein would be a disaster in the making.
CE.
Useful Links: Forum Guidelines | Documentation | Tutorials | HOWTO | Videos | Donate to CEGUI | CEGUI Twitter
Re: 7.0 Sample run failed
then if i want embed a image into the text of a editbox or change it's colour ,what can i do? parse the text of a editbox by myself?
- CrazyEddie
- CEGUI Project Lead
- Posts: 6760
- Joined: Wed Jan 12, 2005 12:06
- Location: England
- Contact:
Re: 7.0 Sample run failed
It's very unlikely that simply parsing the text yourself would yield satisfactory results, except in what I imagine would be very rare circumstances.
In order to create a viable solution, the text that is set to the Editbox - the one with the control tags in it - would need to be totally separate to the text that is 'edited' by, and displayed to the user.
If you simply use the same text string for all three situations, things will quickly become unacceptable. For example, a couple of basic scenarios you may have overlooked…
1) What happens when the user enters text for a control string?
2) What happens when - visually - part of the text that forms a control tag is replaced by an image, a colour change or a font change instruction? The internal string still contains the actual text for the control tag, and so caret positioning operations and editing operations will be operating based on indexes within a string that contains the text that forms the control tag; visually something entirely different will be happening.
Obviously these - and any other - issues are not insurmountable. However they would pretty much dictate a complete rewrite of the Editbox classes.
CE.
In order to create a viable solution, the text that is set to the Editbox - the one with the control tags in it - would need to be totally separate to the text that is 'edited' by, and displayed to the user.
If you simply use the same text string for all three situations, things will quickly become unacceptable. For example, a couple of basic scenarios you may have overlooked…
1) What happens when the user enters text for a control string?
2) What happens when - visually - part of the text that forms a control tag is replaced by an image, a colour change or a font change instruction? The internal string still contains the actual text for the control tag, and so caret positioning operations and editing operations will be operating based on indexes within a string that contains the text that forms the control tag; visually something entirely different will be happening.
Obviously these - and any other - issues are not insurmountable. However they would pretty much dictate a complete rewrite of the Editbox classes.
CE.
Useful Links: Forum Guidelines | Documentation | Tutorials | HOWTO | Videos | Donate to CEGUI | CEGUI Twitter
Re: 7.0 Sample run failed
thanks a lot for your patience,Merry Christmas
- CrazyEddie
- CEGUI Project Lead
- Posts: 6760
- Joined: Wed Jan 12, 2005 12:06
- Location: England
- Contact:
Re: 7.0 Sample run failed
Thanks... Happy new year!
Useful Links: Forum Guidelines | Documentation | Tutorials | HOWTO | Videos | Donate to CEGUI | CEGUI Twitter
Who is online
Users browsing this forum: No registered users and 13 guests