...slightly related...

Michael, was there ever an update that you know of for the "FullScreen" script that allows for the UI to be toggled on and off?
The one I have doesn't work for V3.

Oh happy day!

Installed. They work beautifully. So simple, so precise; yet incomprehensible and impossible to achieve for
a script-illiterate like me.

Btw, in regard to my UI color request: there is a color picker in Moi3d. Options>View>Color>click on any color
window and you have an RGB color picker. Select your color modification, copy and paste the readings into the .ini file.
Saves the trouble of going to Photoshop etal.

Thank you.

Rich (a happy moier)

Rich,

Here are two different flavors of "parallel" view:

Here is Parallel view at that 30/60 degrees thing... "Dimetric"

 script:var vp = moi.ui.mainWindow.viewpanel.getViewport('3D'); vp.projection = 'Parallel'; var as13 = Math.asin(1/3); vp.setAngles( 90 - (Math.asin(Math.tan(as13)) * 180/Math.PI), as13 * 180/Math.PI ); 

Here is a Parallel view at 45 degrees... "Isometric"

 script:var vp = moi.ui.mainWindow.viewpanel.getViewport('3D'); vp.projection = 'Parallel'; vp.setAngles( 90 - (Math.asin(Math.tan(30 * Math.PI/180)) * 180/Math.PI), 45 ); 

And to get things back in Perspective...

 script:var vp = moi.ui.mainWindow.viewpanel.getViewport('3D'); vp.projection = 'Perspective'; 

Really good for when you're trying to get that "old school" look.

Hi Mike - re: FullScreen for V3, check out here:
<....> Note -

And Rich - you're welcome and I'm glad those scripts are working for you!


EDIT: note - the full screen version linked to previously didn't work quite right if you had the scene browser in "inside" mode, see the updated one a bit further down in this thread for a fixed version:
http://moi3d.com/forum/index.php?webtag=MOI&msg=5141.17

- Michael

Thanks Michael,

Found out that V3 doesn't seem to like the ".js" on the end of "FullScreen.js" for a key command.
But I don't know why or why not it was there. I'm guessing it didn't care in V2.

Okay, noticed a problem with FullScreen.js - on first activation it adds a large blank area to the left of my command pane (which is on the right).
The next activation clears the UI and does what it's supposed to do. The next activation still comes back with the added panel.
You have to re-load MoI to get get rid of it.

Hi Mike,

> Found out that V3 doesn't seem to like the ".js" on the end of
> "FullScreen.js" for a key command.

What are you putting in for the shortcut? Are you maybe starting it with script: at the front of it? That prefix script: is actually only meant to be used when the script code itself is directly in the shortcut, when it refers to a separate .js file don't put script: in the front, just put the whole path to the .js file like: c:\scripts\FullScreen.js . It will also try to automatically add the .js when it checks to see if that shortcut is actually a file that can be loaded though too.


> Okay, noticed a problem with FullScreen.js - on first activation it adds a
> large blank area to the left of my command pane (which is on the right).

It's probably something to do with the scene browser pane - over here I don't get a blank area but it does show the scene browser pane even though it's supposed to be turned off.

Do you get normal operation if you turn the browser pane on before doing FullScreen ? Or do you maybe have the browser in "inside" mode?

- Michael

Hi Mike, so it looks like FullScreen did not work quite right with the scene browser in "inside" mode.

I've attached an updated version of FullScreen.js which I think should fix that up.

Copy the FullScreen.js somewhere on your system and then for the shortcut key put in the full path (and only the full path, no "script:" at the front) to the file, like: c:\scripts\FullScreen.js

- Michael

Thank you very much, Michael!

Yes, I keep the browser inside.

It works again! ...kind of...
So it does hide the UI, effectively enlarging the current window scheme to full screen, however:

On the first activation it will not hide the UI, but only closes up any expanded open tool options.
On the second activation it will hid the entire UI.

Then after that will will then both hide the UI and close any expanded tool option simultaneously.

Hi Mike, could you describe a bit more exactly what you mean by "expanded open tool options" ?

Do you mean options for a command that is currently running?

Are you running it under version 3 or version 2? I've been testing it under v3 and I can't seem to get the behavior you are describing, does it only happen to you in v2?

- Michael

Using V3's beta.

It's the sub-palette that carries more tools. Life for "Boolean" you get the layout that has the icons for "Diff", "Union", "Isect", & "Merge"

Even when not it use and last open. They close up too (along with the whole UI) when the FullScreen.js is activated. Except during the first event upon after program start, only the sub -palette closes.
FS has to be activated again.

Hi Mike, hmmm weird - I can't replicate anything like that over here.

But it sounds like you have an easy solution for it, just trigger full screen again when you see that anomaly and things are ok for the entire session after that?

- Michael

Hi Mike, also maybe double-check what you have put in as the shortcut key for full screen.

Have you possibly copied it to the commands sub-folder? If so move it out from there, you can put it into a scripts folder somewhere, and then in the shortcut key put the entire path to the script file like "c:\scripts\FullScreen.js", and _not_ just the name FullScreen like is done for commands.

Does that then solve this start-up anomaly for you?

My guess is that maybe you were getting it launched as a "command" instead of as a script, which are managed in slightly different ways - commands have some other things that happen for them part of which is handling that sub-palette stuff.

- Michael

Thanks!

Yup, cool! It now works in one shot and the open palettes stay open.
All I did was move the script to the "scripts" folder. Didn't need to say anything by "FullScreen" in the shortcuts.

Hmmm, guess it wasn't go in the "commands" folder. :-)

Mike

Hi Mike, yeah if you put it in a "scripts" folder that you put as a sibling to the commands folder, it will find it in there.

Basically a command is a kind of script that is set up to have things like sub palettes and options UI and stuff like that, and for this particular function you don't want it to run with those other things getting involved.

- Michael

Magic,

Thank you. A few more reasons not to need using ViaCad.

Rich

I have done as above but when it returns from the full screen it mangles the right hand side , it comes back as double width
If I go into options general and change the scene browser position from inside to opposite and back again it fixes it
Any ideas
thanks
shayne

Hi shayne, there's an updated version posted a bit later down in the thread, make sure you're using the newer one as it should be tuned up to fix that problem you're showing there. Grab the one from here:
http://moi3d.com/forum/index.php?webtag=MOI&msg=5141.17

- Michael

Shayne,

The solution is to first get the new "FullScreen.js" posted earlier.
Second, make sure there is a folder named "scripts" in the MoI program folder.
Third, make sure that the command for Full Screen in the keyboard shortcuts list is "FullScreen.js"


Well, Michael, I'm having trouble getting the way cool AutoRotate2 script to work at home. Comes up with a nasty js error, lots of stuff missing.
I'll have to send you something later. Just know it works on my work PC and everything down to MoI's ".ini" is the same at home,
except for the fact that I'm running win7 at work and XP at home. hmmm, maybe it was the .ini file I copied to my home PC.
AutoRotate2 is a pretty cool script. It's like a mini-spinning showroom platform. Works great with FullScreen!

I also have a long time mystery where the "Delete" key and the numeric key pad "Del" does not work for deleting stuff in MoI even though is it programmed correctly in the shortcuts list, but the button works.
But in both cases, there may be a thousand subtle configurations of things on my old XP machine to contribute to Murphy's law.

Hi Mike,

re: Autorotate2 - there should be 2 files for that one, a .js file and an .htm file as well - is it possible you have only copied the .js file and not the .htm file over? Also that one should go into the "commands" folder - not the "scripts" folder.

If it wasn't either of those things can you please post the particular script error that is being triggered? That may help me to figure out what to look at.


re: Delete key not working - I don't really know what might be going on with that, do you have any kind of additional software running on that machine that might try to handle shortcut keys itself and might intercept certain keystrokes? In the shortcut key editor in MoI the key name should just read:   Delete . You can also set Backspace up as well if that helps.

Also does your delete key work in other places, like when editing text?

- Michael

Thanks Michael, I think I figured some things out, at least.

I got the AutoRotate2 to work by taking the files out of the "scripts" folder and placing them in the "commands" folder.
Then I had to take the ".js" off the end of "AutoRotate2" in the keyboards shortcuts list.
Funny, it worked the other day, until I copied an updated MoI .ini file from work. ??

So, aside from trial and error, is there a way to tell where a script is supposed to go and how to tell Moi to 'see' it? ;-)

Also, MoI here at home would not see the Del or Delete key presses. The shortcuts menu says "Delete" in both columns.
When I went to do something simple, like use delete to delete character in Notepad, now it works in MoI again too.
This is obviously some kinds of resource or resident app in my PC... so at least it's probably not a MoI issue.
Fun fun fun...