@tyglik : Sorry can you post a little image of the action result of these 2 new files?

surely, Pilou....... i am not planning to go your computer down............

Petr

Hi Petr, you even figured out how to tie it to being full screen or not!

I thought it would be cool for people to be able to modify the UI in this way.

There are a lot more possibilities as well - it is possible to write pretty sophisticated commands and tools that operate the same as MoI's regular commands. You've probably already seen that each command has a .js and .htm file for it. The only problem is that I don't think that I'm going to be able to get this area really documented properly for the V1 release, this type of expandability will probably be more of a focus in later versions.

- Michael

@tyglik : Ah! OK I See now :)
I had never used MoI in full screen! :)
So now testing your plug in, seems work fine!
In theory the use of this plug can interfering with the normal program (decrease slowdown possible) or it's negligible?

The double arrows on the right bottom side (expand / reduce )is also your plug or not ?

Hi, Pilou

>>plug in,...
it's merely a little (poor) triviality. i am not software engineer...

>>In theory the use of this plug can interfering with the normal program (decrease slowdown possible) or it's negligible?
it seems not to be noticeable, it just reloads some functions/methods each 1000miliseconds, though

>>The double arrows on the right bottom side (expand / reduce )is also your plug or not ?
no!, you might read the introductory documentation more carefully......hehe... look here ..\MoI\MoI_Introduction.htm (point five - options/help))


Petr

Point 5 : you entierely right! Completly forget to see it :X
Look this a famous french car and the model of the button :)
http://www.fotosearch.com/comp/SIX/SIX012/TRA-475.jpg

PS We can also press the little rectangles right upper corner side for Expand/ reduce screen :)
Maybe this can wins some place for Michael !
Double "same function" is maybe not necessary :D

> it seems not to be noticeable, it just reloads some functions/methods
> each 1000miliseconds, though

It should be fine. But since there is no seconds readout, I think the only reason why you've got it checking once a second is so that it can appear or disappear fairly promptly when window is switched between fullscreen or not?

There is a different way to do this called "binding", which you can use to trigger something when a variable inside of MoI changes. By using binding to control the visibility of the clock, the clock update interval can then be changed to only once a minute (as in the attached version).

- Michael

>>I think the only reason why you've got it checking once a second is so that it can appear or disappear fairly promptly when window is switched between fullscreen or not?

You are absolutely right, Michael. Thank you for your improvement!
I just wanted to show how MoI is fully customizable, nothing else...

Petr

> I just wanted to show how MoI is fully customizable, nothing else...

Well, this is actually a pretty cool customization. Someone has previously requested this exact thing.

If you can just implement a few more user requests, maybe I can take a vacation or something! ;)

Let me know if you have any questions about doing any other customizations.

- Michael

Cool functions seems better and useful than an outrageous possibilities of customization :D

Hi Michael,

When we were discussing world/plane coordinates input recently, you mentioned that there isn't a "concept of active view" in MoI currently. However, I have been going through discussion forum and I have discovered 'getViewportUnderMouse()' method. Considering tablet users and their way of working without mouse, I guess this is somewhat like special-purpose method, not widely used one.

Petr

> Considering tablet users and their way of working without mouse, I guess this
> is somewhat like special-purpose method, not widely used one.

Well, that method works with a tablet as well, since the tablet also functions as a mouse. I guess I should have called it getViewportUnderCursor() to be more exact.

That was added in to make it possible to make a keyboard shortcut that would maximize the viewport the cursor was over when pushing the space bar.

Internally there isn't really anything that is particularly controlled by the viewport under the mouse. A few things pay attention to it for some smaller details, like redrawing that viewport first.

- Michael