Thanks for the answers. Actually i was editing the post on purpose in order not to spam you because otherwise you are going to start hating me :) hehe Getting feedback from users is not a reason to hate, in fact it is the opposite. Open as many threads as you want. I cannot guarantee you fast respo...

An example, creating a texture filled in red #include <NsRender/IRenderSystem.h> #include <NsDrawing/Image.h> #include <NsDrawing/ImageSet.h> #include <NsDrawing/Color.h> using namespace Noesis; using namespace Noesis::Core; using namespace Noesis::Drawing; using namespace Noesis::Render; Ptr<ITextu...

Jesus (i think it's your name), I'm not sure i understand what you are saying here. Eliminating the Background does not result in the desired behavior. I need to get the MouseEvents on the full screen, on the root. A control doesn't send MouseEvent if there is no background nor "foreground&quo...

We have a ticket to implement this in Unity but in C++ it can already be done. Although I would like to test it before if you can try these are the steps: 1. Create a texture using the rendersystem Ptr<ImageSet> imageSet = *new ImageSet(ImageSetLayout_2D, 1); imageSet->SetImage(image.GetPtr()); text...

I think this is confusing... Having the property BackGround to Transparent means that control starts with a background set to (0,0,0,0). This is not the same as having the control background being transparent. So the behavior when the control fills the screen is correct although the result when it i...

Hi!

I just sent you a hotfix for this problem.

Thank.

The functions passed to NsProp must use const NsString&: const NsString& MyClass::GetText() const { return GetValue<NsString>(TextProperty); } void MyClass::SetText(const NsString& text) { SetValue<NsString>(TextProperty, text); } ... NsProp("Text", &MyClass::GetText, &...

Hi, Excellent work! I see that there are more codes in OIS but many of them were intentionally omitted in Noesis. For example KC_LBRACKET and KC_RBRACKET don't correspond to a physical key in a Spanish Keyboard. We tried to avoid those conflicting keys. Although may be we should extend our enumerati...

I think we don't have to change anything, the current architecture is correct.

• You register your components in a new function called as you wish.
• You implement the required exported function NsRegisterReflection. It is implemented by invoking the function defined above.

Yeah, I would put it in the OgreBindings logic. I was mainly curious if Noesis already had that array defined so that I could paste it into my version of the bindings as a hot-fix (as opposed to me writing it by hand). If you don't already have it written though I can wait until the update goes out...