LiveCode Forums

I've added a "recent targets" function to Navigator (it's not out yet, but soon). So far I'm putting the 7 most recent card/group targets near the top of the "which card" menu (the third from left. That makes sense to me as a location for it, since the recents always include either a group or a card...

Thanks! Apparently a message needs 10 characters, so thanks a lot!

I checked, and apparently I had an optimistic impression of how Navigator used to handle the highlighted lines when dragging and dropping. I didn't find a version with any retention of highlighting at all. So while there's still room for improvement, what I have now is better than before.

I forgot -- I also added in-line editing of properties identified as single-line in Navigator's property editor. Meaning: 1. If the property is "colors" (this would only be displayed if you add colors to the control's properties in Navigator's preferences dialog) then Navigator will immediately open...

As usual, you can get Navigator here . Or grab it from GitHub . Phew! I discovered a brutal bug in Navigator while coding this update. Everyone should either update, or avoid the "Save All" and "Save Stackfiles" popup menu options. The code that iterated over the stackFiles of a stack to save them a...

As usual, you can get Navigator here . Or grab it from GitHub . I'm stunned at the impact this update to Navigator has had for me. I'm excited to post this update. While I was building the Size/Location Editor I had to repeatedly edit the rects and locations of the various bits, and edit the tooltip...

Glad to hear it's functioning properly. I'm testing an update now that should make it even better.

Removed the need for the option key in both the stack menu and the card menu. Menu selections now allow for the functionality previously managed by the option key. Option key is still an option (heh) for the stack menu. In the stack menu, there is now an option for showing IDE stacks, and a separate...

I made a mistake setting Navigator up to edit fillGradients. It will work for any control that already has a fillGradient, but cannot add a fillGradient to a control that doesn't already have one. I've corrected that in my working copy. I'm updating the color editor and the whole thing should be rea...

Could RevNavigator edit a fillGradient? This turned out to be easier than expected, in that the fillGradient can be treated as oddly-named properties. So all I had to do was modify the routine that generates the list of properties-in-common for a set of controls, and if "fillGradient" is there, rep...

With 9.0.1.15103 (I think the most recent version) on a Mac, I'm seeing this. Is this what I should be seeing, or a demonstration of the error you're talking about?

From Gradients01.ai


From Gradients02.ai:

I think things are working properly in 9.0.0 dp11 -- the .ai files seemed to import correctly, with gradients intact?

Could RevNavigator edit a fillGradient? I came across this while I was coding this update, actually, since I use fill gradients in the colors editor. The fillGradient is a pain in the neck, since it is (as far as I know) the only property that's actually an array. I could custom-code a way of deali...

Updated to alpha 4. Updated the prefs format. Prefs now use a custom encode/decode routine so only cr and tab are encoded. The result is simpler to modify as a text file. This version of Nav will still correctly read the old format. Had already updated in alpha 3 to fix an issue with custom values i...

​...and updated to alpha 2. Found and fixed a bug with proportional resizing, and removed an unnecessary visual element from the resizing dialog.​