Call to Mac users for script portability
-
i tried the two new files and nothing changed as far as the dialog box goes.
with those files, the arrow keys no longer work nor does the shift key for locking protractor orientation but the tab key does. also, no change to the function keys.
the reset icons do not show up but in the video, you'll see that there is a space designated by a square and it is functional. i can reset the individual default parameters by clicking the square.
@unknownuser said:
- If Function Keys are not ideal on Mac, do you have any suggestion of other shortcuts than could be used instead ?
if those functions (ie- activate slicer, toggle wireframe, etc.) were placed in the menu or a submenu then we could assign our own keys but that pretty much defeats the purpose of what you're trying to do..
like i said earlier, i can assign the F keys as shortcuts and they work fine. (i tried F4 as the protractor shortcut and it works as expected).. Torben is probably right in that the keycodes are different than with windows.
if it helps at all, here are the key identifiers for the F keys on macs:F1 - 63236
F2 - 63237
F3 - 63238
F4 - 63239
F5 - 63240
F6 - 63241
F7 - 63242
F8 - 63243 -
@unknownuser said:
with those files, the arrow keys no longer work nor does the shift key for locking protractor orientation but the tab key does. also, no change to the function keys.
Do you mean that the Arrow keys, Shift and Ctrl were working fine before the new file?
-
@unknownuser said:
@unknownuser said:
with those files, the arrow keys no longer work nor does the shift key for locking protractor orientation but the tab key does. also, no change to the function keys.
Do you mean that the Arrow keys, Shift and Ctrl were working fine before the new file?
yes, before i replaced the files with the two you posted in this thread, i was able to use the arrow keys to change the protractor's orientation (up-blue, left-green, right-red) or i could get the orientation by putting the protractor on a certain plane and locking its position via the shift key...
after i replaced the files with the new ones, none of those functions worked..
i've since changed back to the original files
-
Jeff,
Sorry for that.
Would you mind to try with the attched file.
Please open the Ruby console, where I trace the keys typed up and down.
If you can try with the Function key, say F2, F3, then I could figure out what are the code and flags sent by Sketchup.
I hope I have at least restored the arrows and Shift / CTRLFredo
PS: on Mac it is appently normal that CTRL maps to Command key, as in native Sketchup
-
For Web dialogs, I really don't know what's going on.
By chance, is there on Mac, like in Windows, a contextual menu where you can do a Refresh and see the source code?Fredo
-
I think, with the new "Lib6Traductor_31.rb", arrow keys work, Fkeys that are not assigned shortcuts in SU work, Alt/Option key still works as Ctrl key. I couldn't test Shift key.
Below I copied and pasted what was in Ruby console when I typed Fkeys.F2
Key Mac 63237 flags = 0 up = false
Key Mac 63237 flags = 8388864 up = true
F3
Key Mac 63238 flags = 8388864 up = true
F4
Key Mac 63239 flags = 0 up = false
Key Mac 63239 flags = 8388864 up = true
F5
Key Mac 63240 flags = 8388864 up = true -
@unknownuser said:
Jeff,
Sorry for that.
Would you mind to try with the attched file.
Please open the Ruby console, where I trace the keys typed up and down.
If you can try with the Function key, say F2, F3, then I could figure out what are the code and flags sent by Sketchup.
I hope I have at least restored the arrows and Shift / CTRLFredo
PS: on Mac it is appently normal that CTRL maps to Command key, as in native Sketchup
the function keys now function! shift works, the arrow keys work.. everything with the keys work
-
@takesh h said:
I think, with the new "Lib6Traductor_31.rb", arrow keys work, Fkeys that are not assigned shortcuts in SU work, Alt/Option key still works as Ctrl key. I couldn't test Shift key.
Below I copied and pasted what was in Ruby console when I typed Fkeys.Glad to see that this works now.
That was an error on the codes for Function keys on MAC.
To test Shift, just use any of the tool and toggle SHIFT to either select all connected geometry or just an edge or face. That will show if this works.Attached is the file without the trace
Fredo
-
For Web Dialogs, I have made a slight change to open the windows in a bigger size, and then try to resize.
Do you notice any difference.
Fredo
PS: actually, the test is also to know if I have a problem with SU Web dialogs or with Safari.
-
@takesh h said:
I think, with the new "Lib6Traductor_31.rb", arrow keys work, Fkeys that are not assigned shortcuts in SU work, Alt/Option key still works as Ctrl key.
a little info about macs and F keys... the keys became programmed as volume, brightness, etc. because of the laptops.. there wasn't enough space on the keyboards for these controls so apple took over the F keys for that purpose..
on your keyboard, you'll notice a key called fn.. that's basically like a shift key for the function keys.. it allows F4 etc to perform double duty..
if you want to use F4 in freescale, you have to push fn/F4 together.. if you push F4 by itself, the dashboard will pop up.. in the system prefs (i mentioned this earlier in the thread), you can flip this around to where the F keys will work as they used to and the assigned functions will only work if you press the fn key as well (ie- fn/F10 for mute)
-
@unknownuser said:
For Web Dialogs, I have made a slight change to open the windows in a bigger size, and then try to resize.
Do you notice any difference.
Fredo
PS: actually, the test is also to know if I have a problem with SU Web dialogs or with Safari.
ok, so the window opens up nearly twice the size as it use to but it very quickly goes back to the original size only now it's near the bottom of the screen.. nothing has change other than the location of where it's at on the screen.. it happens so fast that i can't see if the save/reset buttons are appearing or not on the initial opening.
also, i'm not sure if you have this going straight to safari or not but earlier, i tried setting my default browser to firefox and everything stayed the same...
earlier you asked "By chance, is there on Mac, like in Windows, a contextual menu where you can do a Refresh and see the source code?"
i don't really know my way around that stuff but it does exist. i pretty much keep it on the GUI side of things.. i wouldn't be much help with code[EDIT]-oh wait, you said 'code' and i started getting scared .. if you mean is there a way to view the source code for a page in safari then yeah, it's easy.. right-click/view source
-
Jeff and Takeshi,
If you can right-click in the dialog box, then could you select the menu "Refresh" if there is one.
Attached is an updated file to avoid the resizing, so that you can possibly check whether the whole content of the dialog box is displayed or not. Keep the previous Lib6Config_31.rb (which open the box with a big size).
I am still wondering why SU does not show the full content, unless there is another problem, but with Safari.
Thanks again
Fredo
PS: SU uses Safari, regardless of the setting of your preferred browser on your MAC. So changing to Firefox would have no influence.
-
here's a screenshot of the dialog using the latest file.
that's exactly how it opens up and it's the best version yet.. the entire red outlined box is now visible but i still have to stretch the window to get to the save/reset buttons.
as far as i'm concerned, everything is totally fine as is but i can understand the confusion by a mac user that is just installing freescale.. regardless, all of the tools work perfectly and that's my main concern.
as far as safari's context menu, these are my options with a normal web page:
with the freescale dialog, i only have one option which it 'reload'.. if i click on that, everything stays the same.
-
Several plugins on the mac, including yours, won´t remember the state of it´s toolbars (opened or closed), between sessions. Someone at google told me that this can be fixed by including something similar to this:
Show toolbar if it was open when we shutdown.
state = toolbar.get_last_state if (state == TB_VISIBLE) toolbar.restore end
Santiago
-
Santiago,
Do you mean that this is specific to the Mac platform?
On Windows, just callingtoolbar.show
is sufficient to take into account the previous state when Sketchup is closed.Anyway it's easy to fix, based on your example.
Thanks for the tip
Fred
-
that would be great to find out a way i could turn the toolbars on and off and have their status remembered.. the only toolbars i have that will do this are the ones that come with SU (sandbox, dynamic components, etc.).. two of the rubies containing toolbars that i have (skin.rb and kerkythea exporter) will not appear upon launch of sketchup and the rest of them will not 'hide' upon launch -- regardless of how they are set up prior to closing the app..
speaking of dynamic components fredo, have you by any chance looked at the code for it (or is it even possible?).. that has a web dialog and there are no problems with it on macs.
-
@unknownuser said:
that would be great to find out a way i could turn the toolbars on and off and have their status remembered.. the only toolbars i have that will do this are the ones that come with SU (sandbox, dynamic components, etc.).. two of the rubies containing toolbars that i have (skin.rb and kerkythea exporter) will not appear upon launch of sketchup and the rest of them will not 'hide' upon launch -- regardless of how they are set up prior to closing the app..
I made a small modification to follow the advice from Santiago (attached file). This problem may be specific to the Mac, because, on Windows, toolbars are well 'remembered'.
@unknownuser said:
speaking of dynamic components fredo, have you by any chance looked at the code for it (or is it even possible?).. that has a web dialog and there are no problems with it on macs.
Thanks for this good idea. Difficult to tell however, because it is done differently (mostly in Javascript for the displays). Also their ruby code is encrypted and I suspect my problem precisely lies in the way the dialog box is configured from Ruby.
-
For the display of Web dialog boxes
Sorry to bother again, I made a slight modif to shift the content down, because it seems that on Mac the top of the HTML content starts under the title bar.
Maybe the attached file will correct this.Fredo
-
Fredo
Thanks for all this work you are doing on the Mac versions.
I have just tried your last update which should remember the last position of the toolbars on Quit. Tools on Surface and Free Scale work OK but BZ_Toolbar, Round Edge and Null Transform still have the problem of returning to there previously displayed position.
Tasman
-
haha, nice
one of the 3-4 toolbars i would like to keep open at all times now has the ability to stay closed..
question: did you have to write something specifically related to this script or is there a generic piece of code i can add to (or request that the writers add) the other toolbar containing rubies.
Advertisement