Pages: « 1 2 3 4 5 6 7 8 9 10 »
 61 
 on: April 09, 2018, 12:35:08 PM 
Started by Jaadelman - Last post by Jaadelman
I have an issue with Windows 10 Pro adn Internet Explorer 11 users who select a word but then all of the text gets highlighted in the editable area.
We use XMetal 11.0 Client, I have tested by removing, reinstalling. Checked the IE 11 settings.

 62 
 on: April 03, 2018, 09:47:26 AM 
Started by lerche - Last post by lerche
This is a good advice.

But there is certainly one disadvantage. The command line switch doesn't get any feedback from visual studio.

Probably I can examine the build completion by writing the build output into a log file. By observing the changes I will get my feedback. I will check it out.

Thank you, Derek!

 63 
 on: April 02, 2018, 11:38:19 AM 
Started by lerche - Last post by Derek Read
XMetaL Developer cannot be run standalone as it is a plugin for Visual Studio. The Microsoft documentation for "devenv" should let you control Visual Studio from the command line. I suspect you likely need either the /build or /rebuild switch, or perhaps one of the others documented here:

https://msdn.microsoft.com/en-us/library/xee0c8y7.aspx

The following works for me:
"C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\devenv.exe" "C:\Visual Studio Projects\Project1\Project1.sln" /build

 64 
 on: April 02, 2018, 05:01:17 AM 
Started by lerche - Last post by lerche
Hello at all,

First of all: Happy easter!

Currently I am working with XMetaL Developer on a XMetaL Author Enterprise project that contains a lots of different JavaScript files. Some of them are XMetaL macros (means that goes to a mcr file) and the others are used for the Resource Manager (Shell.Explorer.2). The visual studio build compiles all necessary files into the output directory, but does not minify or optimize the JS code. Thats why I created a gulpfile to do all necessary stuff automatically. There is only one step I do not know how to do. I want to trigger the build of visual studio with the msbuild command line at first. But I get this warning message by trying it:

Quote
*.xdp.metaproj: warning MSB 4078: The project file "*.xdp" is not supported by MSBuild and cannot be build.

The command was:

Quote
msbuild solutionName.sln

Obviously xdp files are not supported by msbuild. I think the correct build tool is hidden somewhere in my installation path of XMetaL developer. Can you give me a hint how to trigger the build with the command line correctly? This would be very helpful to automate my build and release process with just one gulp command.

I would be very grateful for every advice.

My system is the following:
XMetaL(R) Author Enterprise 12.0.0.077
XMetaL(R) Developer Version 12.0.0.077
Visual Studio 2015 (Community Edition) Update 3
OS: Windows 10 Pro, English

Thank you!

René

 65 
 on: March 05, 2018, 07:47:22 AM 
Started by AmitElhanan - Last post by AmitElhanan
Thank you Derek,

I'll give these suggestions a shot.

 66 
 on: March 01, 2018, 05:22:17 PM 
Started by AmitElhanan - Last post by Derek Read
This somewhat related idea might also be useful:
http://forums.xmetal.com/index.php/topic,738.0.html

 67 
 on: March 01, 2018, 01:31:58 PM 
Started by AmitElhanan - Last post by Derek Read
Popping something up in Normal view in the same way it appears in Tags On view would tend to get in the way I think, at least if the same gesture was used.

The only thing I can think of that might give you some bit of similar functionality immediately using existing functionality and that wouldn't get in the way would be to display something in the status bar. There isn't a lot of room in there though, so I think you'd want to limit which attributes are being displayed to one or two.

The following would give you that functionality, provided it doesn't conflict with another macro already in your customization(s) that is displaying information in there:

Code:
<MACRO name="On_Update_UI" lang="JScript" hide="false"><![CDATA[

//add attributes to the following array to include them in the status bar display
var attrs = ["id","href"];

var msg = "";
for(i=0;i<attrs.length;i++) {
msg += attrs[i] + "=\"";
msg += Selection.ContainerAttribute(attrs[i]) + "\"  ";
}
Application.SetStatusText(msg);
]]></MACRO>

I don't think that is much better than having the Attribute Inspector open but you might feel otherwise. One benefit might be that displaying this information in the status bar kind of makes sense because you don't really know exactly what you have selected in Normal view unless you look at the mini-context to see which element you are in (and that appears just above the status bar, so you're looking in the same place).

 68 
 on: March 01, 2018, 09:42:17 AM 
Started by AmitElhanan - Last post by AmitElhanan
Is there a way to get the attribute hover that works on the "Tags On View" to work in the "Normal View"?

Using XMetaL Author Enterprise 10.0

 69 
 on: February 26, 2018, 03:43:56 AM 
Started by anton - Last post by anton
Thank you, Derek, that's exactly what we need!

 70 
 on: February 21, 2018, 02:26:03 PM 
Started by anton - Last post by Derek Read
When you use addElement() you are modifying the in-memory model of the DTD (which is why it is used in the event On_DTD_Open_Complete). That change is permanent until the DTD is reloaded. There is no equivalent API for removing such definitions from the in-memory model of the DTD.

If the only issue is that you don't want the user to insert the element using the Element List you can modify what appears in the Element List using the On_Update_ElementList event and the API ElementList.RemoveItem(elemname). This event fires each time the element list is updated which gives you the flexibility to include logic that decides whether or not to remove an item under specific circumstances. If you want it to never be listed then your logic would just always remove it.

This will not stop a user from pasting the element into a document or typing it into Plain Text view. That would require the DTD to be reloaded.

Pages: « 1 2 3 4 5 6 7 8 9 10 »
email us