GUI Prototyping thread...

[Carbonflux]

Here is a update of what I am working on...

The buttons are small like that because they don't have bitmaps assigned to them yet. Also these are just quick prototype controls, we can change them around.

The next thing to test is abstracting these into a sub class that can be instantiated from C++.

If it seems like the basic concept is workable I am going to proceed with implementing the C++ backend for this, this also might require having to rearrange some of the class organization in wxluxgui which I will know more about once I get into it.

I will update the status ASAP.

[Poncho]

Please also add an option that when you are full screen you can quite it by pressing Esc (in case pleople don't know the shortkey ctrl+f).

Also a small 'bug', when you press info and get the splash screen and you alt+tab to another program the splash screen will stay on top.

[Carbonflux]

I will take care of both of these issues before the release, thank you for reporting them

[psychotron]

Hi,

/requests warning /

please, can GUI be enriched with a color picker tool? something like Blender have - you can pick color from render window and view its RGB values in 32bit float range...
it would be very useful for exposition setting and tone mapping tools which are *crossing fingers* definitely coming to LuxRender
and what about manually paint out unwanted fireflies with colors picked directly from render (even in 'stop' time and maybe available only with 'write fleximage' option)? it would be cheating and not very unbiased approach or can it ruin whole image synthesise? but if something like this can accelerate convergencing it would be nice feature to operate with in times when deadline is coming close

With all that great tonemapping stuff around it would be nice when there could be a camera exposure control in terms of ISO/f-stop/shutterspeed too please? btw where can I find in LuxBlend somekind of ISO settings for fleximage (I assume it's like analog film only in digital format packed with crazy possibilies) and why is shutterspeed setting only in 'motion blur' submenu - can I use it "without harm" even on static stills? It's not necessary to have it in 'realistic camera' submenu anymore?

and would be there histogram too? please?

thanks for your time everybody

[Poncho]

That wxFormBuilder program looks nice.

I do have a stupid question, where can I download the current and latest code/ wx-project of the LuxGUI ?

[Carbonflux]

there is a file in lux/renderer, wxluxframe.fbp that generates the wxluxframe.cpp and .h files, then wxluxgui.cpp and .h contain the child classes with the overloaded event functions and stuff.

[Abel]

I do have a stupid question, where can I download the current and latest code/ wx-project of the LuxGUI ?

Look for a file called wxluxgui.cpp in the LuxRender cvs.

[Poncho]

Never worked with CVS before, but I got the files with that Tortoise program (on Vista).

I also found the file that can be opened with wxFormBuilder. The cpp file for compiling with DevShed didn't work, it can't find the .h... I'll figure that out once...

I just hope I didn't break anything during my adventure with the CVS program, lol...

[Carbonflux]

I just hope I didn't break anything during my adventure with the CVS program, lol...

Heh, you can just delete everything and start over, or have several copies, I keep a pure copy and then spawn variations of it etc.

[Poncho]

Is it an idea to put some info of the rendering in an exif (in the image)? Perhaps the S/px amount or render time or simple the date or ... basic render settings used or dof used? Perhaps also put in it that it's renderd with Luxrender and what version?

You know what exif is? If you take picture with digital camera it will put info in your jpg with exif and so you can read (years later, haha) what you used for settings, camera or when you shot the image.

Also it would be nice if there is a button on GUI that will copy all the info (like mentioned above) of rendering (S/px, time, date, lux version, cpu?, basic render setting?) to clipboard. This way, if someone post an image on forum it can put "standard" info with it. This can help with bugs and this also prevents all the "what settings, how long etc." questions.

What do you think of the two idea's?