Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - alex

Pages: 1 2 [3] 4 5 ... 133
31
General Discussion / Re: Disabling template parameters & Windows tabs
« on: March 19, 2017, 04:15:48 pm »
Hi Greg,

code templates are defined for every language in Tools->Options->Syntax Settings->[Syntax, for Example HTML]->Code Templates:
http://wiki.hippoedit.com/options/syntax/code-templates

Here you can modify the template in a way you need. The reason why you get a popup asking for a parameter, is [%Variable name%] tag, which brings prompt to enter a "Variable name" value during expansion: http://wiki.hippoedit.com/general/built-in-variables

If you do not like the default code for the template, just take out the tag (probably it is "%Link URL%") and press OK/Apply.
So for this code template as an example:
Code: [Select]
<a href="%Link URL%">%Link Text%</a>%|%it may be something like this:
Code: [Select]
<a href="">%|%</a>
For Document Tabs preview, there is no UI setting, but there is an XML flag:
http://wiki.hippoedit.com/options/xml/taskbar-thumbnails

Best regards,
Alex.

32
Syntax Files / Re: Apply Keyword to first byte only
« on: March 15, 2017, 10:29:09 am »
Hi,

for me was important to know, what is a common instruction set/syntax for Freescale 68HC11 and what is an extension for your special case. Because I can only publish most common part.
That was a reason for my questions. I can not be an expert in all syntaxes, so for preparation/validation of syntax scheme, I need someone who has a deep knowledge in the language specification.

But OK, now it is done, I have published the common syntax, hope it is OK.
And, as mentioned, your extensions for common subset of Freescale 68HC11 instructions you can find in "ASM68HC11X" on GitHub.

BR, Alex.

33
Syntax Files / Re: Apply Keyword to first byte only
« on: March 15, 2017, 12:53:53 am »
Hi,

while I did not get any response and clarification from you, I have stripped from the scheme instructions I have not found in the official documentation, comment style with {} and registers and have published the scheme in that way in the on-line repository. Now other users can benefit from it.
http://asm68hc11-editor.hippoedit.com

But to still keep your extension, I have moved them in new "specialized" scheme, which inherits from base ASM68HC11 and extend it with additional styles and keywords. You can find it on GiHub:
https://github.com/hippoedit/syntax/blob/master/Assembler/asm68HC11X_spec.xml
If you want to use it, you need to install base ASM68HC11 and extension. Then you can disable the base scheme in settings to not get it selected/suggested.

BR, Alex.

34
Hi Steve,

Hm. I was expecting that your file would not contain any keymap, but there are some. But the list of commands is less than in standard keymap (or at least size of the file: yours is 15K and mine is 24K).  Maybe something was initialized not completely and then persisted...

I am really interesting in getting it fixed!

Also, please update to newest HippoEDIT build.

BR, Alex.

35
Hello Stephen,

this is an old problem that I can not catch... I have tried the way with ending of HippoEDIT with End Task, but by me, after a restart, commands are still working. Have tried to do some modifications for shortcuts before, still works. With open Options dialog - it still works.

Can you please attach here file %TEMP\hekeymap.tmp - I assume it is corrupted. Maybe I can find out something from it... This a cache file used, for storing keyboard map between sessions - to not parse XML every time.

To correct the situation, close HippoEDIT, delete the hekeymap.tmp and start once more.

But I would appreciate very much if you recreate the state once more :) In a way I can recreate it and fix ;)

BR, Alex.

36
Syntax Files / Re: Apply Keyword to first byte only
« on: February 20, 2017, 11:42:38 am »
OK, I see...

It makes no sense to release to others some syntax schema that they can not use because the compiler is proprietary.
But we can try to release some more generic for 68HC11 and you will do specialization of it, by inheriting the generic schema. If it will work.

Please provide a more extended version of you sample file, with labels and block comments (better with all syntax constructions that may appear) that we can verify if generic scheme fits.
As I wrote, you used @ for defining a label and {} for comments. And I do not know if it was a mistake in a scheme definition, or is a real part of the syntax - then I need to see an example that can validate that it works.

In addition, I have found several keywords that are in the scheme but not in the data sheet you have provided, as:
Code: XML
  1. <Keyword text="ABDA"/>
  2. <Keyword text="ADC A" descr="Add with Carry to A"/>
  3. <Keyword text="ADC B" descr="Add with Carry to B"/>
  4. <Keyword text="ADMMUX1"/>
  5. <Keyword text="ADREAD"/>
  6. <Keyword text="ASL A" descr="Arithmetic Shift Left A"/>
  7. <Keyword text="ASL B" descr="Arithmetic Shift Left B"/>
  8. <Keyword text="ASL D" descr="Arithmetic Shift Left D"/>
  9. <Keyword text="ASR A" descr="Arithmetic Shift Right A"/>
  10. <Keyword text="ASR B" descr="Arithmetic Shift Right B"/>
  11. <Keyword text="DEC A" descr="Decrement Accumulator A"/>
  12. <Keyword text="DEC B" descr="Decrement Accumulator B"/>
  13. <Keyword text="EOR A" descr="Exclusive OR A with Memory"/>
  14. <Keyword text="EOR B" descr="Exclusive OR B with Memory"/>
  15. <Keyword text="LD D"/>
  16. <Keyword text="LD S"/>
  17. <Keyword text="LD X"/>
  18. <Keyword text="LD Y"/>
  19. <Keyword text="LDA A"/>
  20. <Keyword text="LDA B"/>
  21. <Keyword text="LDA D"/>
  22. ....
  23.  
Can you please verify the list of keywords (in updated scheme from me) against of datasheet you have provided and tell, if the list is OK. What is missing, what is incorrect, and where is your personal additions (if they are in). Check if descriptions of instructions are OK - this what will be displayed in auto completion list.
I assume all instructions with spaces inside like "PSH X" etc are alternatives to instructions without space e.g. "PSHX"?

Also, I would like to know, what means are "registers" on the first column. Are they works as labels? While in all other samples I have found, it was a place for labels. Is it required that first "column" is always filled?
And for what means a second column where numbers are used? This actually was a problem for extending the definition of number to support also HEX because I need rules to distinguish it from instruction in the text, e.g. "ADCD".

Let us do it well ;)

BR, Alex.

37
Syntax Files / Re: Apply Keyword to first byte only
« on: February 17, 2017, 07:03:21 pm »
Hi,

can you try the version from GitHub?

You need these files:
https://github.com/hippoedit/syntax/blob/master/Assembler/asm_base_spec.xml
https://github.com/hippoedit/syntax/blob/master/Assembler/asm68HC11_spec.xml
https://github.com/hippoedit/syntax/blob/master/Assembler/asm68HC11_user.xml

I publish new schemes with a pleasure, but I need to be sure, that it has the best quality ;) And it is completely correct (at least in a way syntax rules may allow).
That is why I always verify schemes before publishing, checking in live examples.

On your example (screenshot):
- everything after ";" is not recognized as a comment
- numbers are not properly highlighted
- you have in scheme {} for comment, but I do not see this in your sample file
- you have in scheme @ for a label, but I do not see it in your sample file

Are example from here (a first match from google for "68hc11 example code"):
http://azug.minpet.unibas.ch/~lukas/68hc11/hc11lib/index.html
Is same assembler you are using?

Here, how it looks with an adapted scheme for 68hc11 assembler I have uploaded to GitHub and plan to add to the repository:


It is still not perfect, 1AA7 shall be also highlighted as a number.

BR, Alex.

38
Syntax Files / Re: Apply Keyword to first byte only
« on: February 17, 2017, 01:54:20 am »
Hi,

checking your sample, and also other samples I have found on the Internet, I saw that the scheme was rather incomplete. Even in your example comments were not properly syntax highlighted :/
So, I have spent some time on correcting it and extending based on information from the Internet. Also adding descriptions for instructions.
Resulted scheme may be found in GitHub: https://github.com/hippoedit/syntax/tree/master/Assembler
Please validate, if it is OK (you can find attached examples or find some other samples in Web).

Also for me was confusing, that you have used for comments {} and @ for labels. Have not found any example with that.
Do you have a link to syntax specification for Freescale 68HC11?

BR, Alex.

39
Syntax Files / Re: Apply Keyword to first byte only
« on: February 16, 2017, 01:43:12 am »
Hi,

can you attach here (or send to supportbox at hippoedit com) a test file Motorolla 68HC11 file?
I would use it for further validation and we can also check if something can be added.

Do you have ideas about what can be:
- default file template for Motorolla 68HC11 file
- standard Code Templates that can be added to the scheme
- Some internet links to documentation, instruction documentation that can be added as syntax contextual help and reference?

BR, Alex.

40
Syntax Files / Re: Apply Keyword to first byte only
« on: February 15, 2017, 10:42:42 am »
Hi the1,

try this
Code: XML
  1. <Style name="Registers" image="13" bold="0" italic="0" underline="0" clr="Keyword3" bkclr="#FFFFFFFF">
  2.   <Keywords lead="$">
  3.     <Keyword text="1A"/>
  4.     ....
  5.   </Keywords>
  6. </Style>
  7.  
You can find documentation about defining keywords here: http://wiki.hippoedit.com/syntax/styles/keywords

You may try also replace Keywords by Regexp or Block definition if registered are all combinations of hex from 00 to FF, but in this case, you will not get them suggested in auto-completion list (if a register is not yet typed in a document).

BR, Alex.
P.S: If you would like to share your syntax schema and get it available in the repository for download, you may send it to me when it is done - I will validate and publish it. It also qualify for free license, if you need it http://hippoedit.com/free_licensed_copy.php

41
General Discussion / Re: Clearing MRUs
« on: February 04, 2017, 02:26:15 pm »
No, the only way is to modify your workspace file directly.
It is possible to initialize all settings, by using command line flag, or start in a mode when recent items are not persisted, but nothing to selectively clean up history.

But I would say, this is not a very often request. More critical is the question: "How I can reset my "Do not Ask" preferences?" (when you set in message box, to not ask again and used selected) ;)
For this is also the only way to modify settings file directly.

42
Hi,

thanks for the report!
A copy-paste error -> fixed and uploaded.

BR, Alex.

43
Solved / Re: [Solved] Data Loss
« on: January 31, 2017, 10:43:49 am »
NP. I am always happy to fix bugs if I can reproduce them ;)

44
Beta Version Test (minor) / HippoEDIT 1.60.41 released
« on: January 30, 2017, 01:33:17 am »
HippoEDIT 1.60 for Win 32 bit (Unicode)
HippoEDIT 1.60 for Win 64 bit (Unicode)
HippoEDIT 1.60 for Win 32 bit (Non-Unicode)

*All installers contain PDB files for better crash reporting, so sizes are rather big (approx 24 mb), but this does not influence performance.

HippoEDIT 1.60.41 is out: bug fixes and small features.

  • Fixed. Boundaries of words with characters from extended Ascii set (e.g. umlauts) determined incorrectly.
  • Fixed. An original file is deleted after Cancel is pressed in Encoding Check dialog when saving files with Unicode data not presented in the current code page. More details...
  • Fixed. Enter (insert of a line break) on Virtual spaces line inserts unnecessary spaces.
  • Fixed. An infinite processing for search with invalid regular expression in not-opened files.
  • Fixed. Crash on installing of 1.60 on top of HippoEDIT 2.0 alpha version.
  • Fixed. Duplicated entries in hippoedit.config file for recent workspaces.
  • Fixed. The online repository does not use original timestamps for installed files.
  • Fixed. Installer contains old syntax files and English Spell Checker dictionary.
  • Fixed. Information about installed bundles is lost in Portable mode or when switching between different architectures, or when deleting HippoEDIT cache files in %TEMP%\he.*.tmp.
  • Fixed. Several UX related optimization for Start Page.
  • New. "Replace in Files" command and menu entry added.

45
Solved / Re: Data Loss
« on: January 25, 2017, 10:38:54 am »
OK, then it is already fixed ;)
I will release new build today/tomorrow, after doing tests.

Pages: 1 2 [3] 4 5 ... 133