[Obsolete] FredoScale 1.0e (Free Scaling, Taper Scaling)
-
By the way, could some Mac User open the Ruby console and type the following command.
FreeScale;;T6[;FSC_FREE_Menu] -
..more icons coming soon.. as i can
-
Manny thanks.....
Elisei
-
Hi Matt, not the best, but here's a couple to start..
not much on line lately but i'll be back sometime soon - (got a couple of surprises)
-
Hi Fredo, got some pictures for you.
This is what you get with 'Customise Toolbar', so what you would see if they were on the normal toolbar (instead of floating, like they do on the Mac).
This is the drop-down from the plugins menu, showing the blank lines (which do work if you click on them and are ticked if you have already selected the tool from the toolbar).
The context menu failing to fly out
Mouseover works
The real problem is the shortcuts
The half covered preferences window. The bottom bit scales with the window, always covering half, if you stretch to twice the length you can see everything.I hope that makes things a bit clearer. I did try the Ruby thing as well and it returned Free Scale, which is confusing.
I noticed in FreeScale.def that there was the line:
T_DEFAULT_ToolbarName = "Freescale"
I tried capitalising the S, but it seemed to make no difference.I did change the language to both French and Spanish and the problems appeared to be the same.
Also, Tab doesn't work, but I can right-click for the dimensions box. I am not too bothered about that, but I thought you might want to know anyway. It might just be bound to something else on the Mac, I will let you know if I find it.
Thanks again for a great plugin, it is now my default scale tool
-
Oops. Sorry, I forgot to mention that all the instructions show up fine in the status bar. I think everything works fine, apart from the bits in the screen caps.
-
james,
i have had problems with non appearing icons (which nonetheless worked if you clicked on the blank space) with other scripts. in most cases the problem went away with simply moving the script to user/library/application support/google sketchup/sketchup/plugins.
for some reason 2 plugins folders are created when you install skp on a mac. some scripts work better at the user level plugins folder.
-
Thanks Edson. I gave that a go, even migrating all my plugins, but that didn't seem to work this time. It did make me think about permissions and ownership, but they all seem fine. I think the rubies only need to be readable, as SU just reads them on startup and presumably then runs things from memory.
My own scripts work fine, despite having no execute permissions (644, must be something to do with Aquamacs, I will have to check the settings).
-
As always, excellent work, CadFather! Thank you!
-
I couldn't help but notice that James' toolbar has four icons.
Mine only has two! And not just 2 blank and 2 showing, but only 2.
The rest of my behaviors match what James has posted.
I, too, migrated all of my plugins to the user library from the root library with no noticeable change to Freescale.
-
Mine originally had two, but I changed it to show all of them down at the bottom of the preferences. You have to scroll down and resize the window in order to see it. I'll use the normal two more, but the target ones will be handy to have around.
-
Thanks James, I don't know how I missed that!
-
Dear James,
Can you be a bit more specific about where the icons are? I'm not too sure what you mean by 'at the bottom of the preferences'.
Regards,
Bob -
@watkins said:
Dear James,
Can you be a bit more specific about where the icons are? I'm not too sure what you mean by 'at the bottom of the preferences'.
Regards,
BobTools > Fredo6 Collection > Freescale > Default Paparameters
Scroll down to Icons visible in the toolbar, click on the two that are unchecked.
-
Dear Johnsenior,
Many thanks,
Bob
-
to James and other MAC Users
Many thanks for this detailed report.
On the menu issue, I really don't know what could be the difference between Mac and Windows. Just in case, I modified the code taking care of that (see attached file).
on TAB, I thought the key code on Mac was 9, as in Windows. Could a ruby programmer equipped with a Mac confirm (or not) that this is what is got when getting the key in the onKeyDown and onKeyUp methods (and also to tell if we get the key on both Down and Up events).
For the web dialogs, I need to see how I could overcome the problem (SU 7 has also a different behavior on Mac vs. SU6).
Thanks again
Fredo
-
That's excellent Fredo, I have all the labels and the shortcuts are bound. I assume it was just splitting that line in declare_command, although I am not sure why that should affect it.
Tab seems to highlight different tools, which can then be selected using space. It does something similar with Georeferencing sometimes. I think it is a Mac thing and it is Really Annoying, as space is the default (and most useful) binding for select. I really wish Google would choose the best aspects of the Windows and Mac versions and then make them both the same.
But anyway, thank you for all your hard work, I am glad it is now working.
-
James,
On the menu, I am glad it's work. I assume you got back the context menu as well. Like you, I don't understand why the Ruby syntax would affect the interpretor differently on Mac and on Windows.
On TAB, I am interested to understand more, because I usually use this key to call dialog boxes (this was already the case for JPP, RoundEdge, TOS and BezierSpline). So:
- What does it do exactly?
- Do you think there would be an alternate key that could be handy to use instead on Mac?
By the way, the key F2 and F3 are assigned to toggle the live deformation and the wireframe. Do they work on Mac?
More generally, I am interested in other potential problems that could be Mac specific.
Thanks
Fredo
-
Ok, now I am really confused.
Things are fine in the plugins menu and the toolbars, but the context menu is still the same. Also, Tab works fine in JPP, but not in this. That does use the old version of LibTraductor (Dec 2007), although the section on keys appeared to be the same (I only looked briefly, so I might have missed something.
F2 and F3 don't seem to do anything, although if selected from the menu (context menu when using the tool works, but not for selecting the tools at the start), it behaves as you would expect. The ASCII code for Tab does seem to be 9, but, interestingly, for F2 and F3 it is 120 and 99, which is the same as for x and c. The hex keyboard codes are 78 and 63 (rather than 7 and 8 for x and c). I don't know if this is the same on the PC or how things work in the rubies, but hopefully that will help you a bit.
Here is a picture of the highlight thing, on the line tool at the moment, if I press it again it will move to the rectangle tool. It does that if you Tab with other tools in normal use, so maybe JPP was grabbing the input in another way?
-
Also, About Centre is toggled by Option (Alt) on the Mac, but that is fine as it is consistent with other tools (Ctrl is used to right click, in case you really feel the need to use a single button mouse).
Advertisement