Recent Posts

Pages: 1 [2] 3 4 ... 10
11
SlickEdit 2018 v23 Beta Discussion / Re: Very weird hang
« Last post by Clark on August 20, 2018, 06:28:50 pm »
Yes, you do need to hold those keys down for a while. Do you remember if this hang happened when you pressed Enter. I'm just wonder if that piece of the debug information was correct since some globals were missing for me to verify it.
12
SlickEdit 2018 v23 Beta Discussion / Re: Minimap font selection
« Last post by jporkkahtc on August 20, 2018, 06:18:45 pm »
Actually, it appears like the minimap doesn't use any font I choose - at least when the font size is > 2.
Maybe it does for size 1 and 2, but its kind of hard to tell.
13
SlickEdit 2018 v23 Beta Discussion / Re: Very weird hang
« Last post by jporkkahtc on August 20, 2018, 06:17:23 pm »
Yes, I tried Ctrl+Alt+Shift+F2, though I didn't know that holding it down for awhile made a difference - I'll try that in the future.

I can't remember for sure if I pressed enter or not when it hung - wasn't expecting a hang!
14
SlickEdit 2018 v23 Beta Discussion / Minimap font selection
« Last post by jporkkahtc on August 20, 2018, 06:14:42 pm »
#1 I tried using "MS Outlook" font for minimap, but Slick doesn't appear to use it.
MSOutlook is all blocks - no actual letters.
But, when I zoom in a few times the text is quite readable - definitely not using this font.

I suspect that using a simple block font will make  a 1 or 2 pt font work well in the minimap.
No point in trying to draw letters - just blank or not blank.

#2
Also, in Tools > Options > Appearance > Fonts, the "Sample" doesn't work for minimap fonts when you set the font size > 2.
15
SlickEdit® / Re: References does not show function definition...
« Last post by joecar on August 20, 2018, 06:07:43 pm »
I can not reproduce this with just those two files.  Perhaps you have a C/C++ tag file with another definition of this same symbol?
I searched (text search) for qla27xx_skip_entry and it shows up here only:

Code: [Select]
Find all "qla27xx_skip_entry", Regular expression (Perl), "<Workspace>", "*.*"
File C:\Users\jcarnuccio\Working\Linux\qla2xxx\qla2xxx-v2632-devel\qla2xxx\qla_tmpl.c
 Function qla27xx_skip_entry(struct qla27xx_fwdt_entry *ent, void *buf) : 124
  125 1:qla27xx_skip_entry(struct qla27xx_fwdt_entry *ent, void *buf)
 Function qla27xx_fwdt_entry_t0(struct scsi_qla_host *vha, struct qla27xx_fwdt_entry *ent, void *buf, ulong *len) : 138
  144 2:        qla27xx_skip_entry(ent, buf);
 Function qla27xx_fwdt_entry_t255(struct scsi_qla_host *vha, struct qla27xx_fwdt_entry *ent, void *buf, ulong *len) : 149
  155 2:        qla27xx_skip_entry(ent, buf);
 Function qla27xx_fwdt_entry_t262(struct scsi_qla_host *vha, struct qla27xx_fwdt_entry *ent, void *buf, ulong *len) : 259
  300 3:                qla27xx_skip_entry(ent, buf);
  308 3:                qla27xx_skip_entry(ent, buf);
 Function qla27xx_fwdt_entry_t263(struct scsi_qla_host *vha, struct qla27xx_fwdt_entry *ent, void *buf, ulong *len) : 322
  362 3:                qla27xx_skip_entry(ent, buf);
  368 4:                        qla27xx_skip_entry(ent, buf);
 Function qla27xx_fwdt_entry_t264(struct scsi_qla_host *vha, struct qla27xx_fwdt_entry *ent, void *buf, ulong *len) : 375
  397 3:                qla27xx_skip_entry(ent, buf);
 Function qla27xx_fwdt_entry_t268(struct scsi_qla_host *vha, struct qla27xx_fwdt_entry *ent, void *buf, ulong *len) : 443
  461 4:                        qla27xx_skip_entry(ent, buf);
  466 3:                qla27xx_skip_entry(ent, buf);
 Function qla27xx_fwdt_entry_t274(struct scsi_qla_host *vha, struct qla27xx_fwdt_entry *ent, void *buf, ulong *len) : 570
  605 3:                qla27xx_skip_entry(ent, buf);
  611 4:                        qla27xx_skip_entry(ent, buf);
 Function qla27xx_fwdt_entry_t275(struct scsi_qla_host *vha, struct qla27xx_fwdt_entry *ent, void *buf, ulong *len) : 618
  632 3:                qla27xx_skip_entry(ent, buf);
 Function qla27xx_fwdt_entry_t276(struct scsi_qla_host *vha, struct qla27xx_fwdt_entry *ent, void *buf, ulong *len) : 647
  664 4:                        qla27xx_skip_entry(ent, buf);
 Function qla27xx_fwdt_entry_t279(struct scsi_qla_host *vha, struct qla27xx_fwdt_entry *ent, void *buf, ulong *len) : 705
  724 4:                        qla27xx_skip_entry(ent, buf);
 Function qla27xx_fwdt_entry_t280(struct scsi_qla_host *vha, struct qla27xx_fwdt_entry *ent, void *buf, ulong *len) : 731
  749 4:                        qla27xx_skip_entry(ent, buf);
 Function qla27xx_fwdt_entry_other(struct scsi_qla_host *vha, struct qla27xx_fwdt_entry *ent, void *buf, ulong *len) : 756
  764 2:        qla27xx_skip_entry(ent, buf);
Total found: 17     Matching files: 1     Total files searched: 29

Quote
When you initiate the references search, are you prompted to select from multiple symbol definitions/declarations? (Select a Symbol dialog)
No, I am not.



The Find Symbol gui finds the definition of this symbol.

Can I send you a tarball of the whole project...?
16
SlickEdit® / Re: References does not show function definition...
« Last post by joecar on August 20, 2018, 06:01:35 pm »
joecar: Try giving Slick team your configuration file - user.cfg.xml in your config directory - that may be needed to reproduce the issue. Also provide them with your workspace/project of your standalone workspace. Upload to support.slickedit.com.
Ok, I can do this... it has a space for a case number...
17
SlickEdit 2018 v23 Beta Discussion / Re: Minimap zoom-out limit
« Last post by Clark on August 20, 2018, 05:56:19 pm »
Here's what I can tell you from some trial and error I did. A 1 pixel high font looks bad (might as well stick with the Document Overview Bar which SlickEdit already has and close the minimap). 2 pixels can look good when done right. Line drawing doesn't look as good as some sort of font drawing (although it's bright because there's no anti-aliasing). The way to force a 2 pixel font is to do some sampling of say a 3 pixel font and remove 1 pixel. On Windows, you can choose a proportional font for the minimap like "Arial" (not sure about other fixed fonts), and it will be 2 pixels high when you choose a 1 point font size. Not a great solution when the edit window is using a fixed font but just though I'd let you know. Choosing a 1 point font on macOS will give you a 2 pixel high font (on my machine that's what it does).

Originally I thought doing line drawing would be the way to go but it doesn't look as good as I thought. No other products I know of do pure line drawing for a minimap (but they do for document overview bar like stuff). Line drawing won't help speed because the line drawing MUST be done base on some font. There is some additional caching SlickEdit could do but it would cause other performance issues. If it did, then you could cache some font results for say line drawing. The real problem here is that Qt is pretty slow with font calculation stuff. I'd say about 4-10x slower than native code. On Mac, SlickEdit bypasses Qt for edit window font drawing. On Windows, this same optimization is not possible (and we are more proficient with Win32 code) due to how Qt was engineered. There really should'nt be a need for caching anything unless we wanted better support for Softwrap which requires storing the edit window softwrap offsets (unlikely we'll ever bother with that).  Note that even though there are WAAAAAAY more extra optimizations for macOS, Windows text drawing is still faster. macOS text drawing graphics is quite slow compared to Windows. Small fonts on macOS look great (better than Windows for sure)! Linux performance is somewhere in the middle but small fonts looks the worst of all the platforms.

Some built-in font generation would be useful. Especially one that takes a 3 point font and reduces it to 2. I suspect if we do that, it might make sense to also support 1 pixel line drawing even though it doesn't really look good.

I hope all this make sense. I've gotten in the weeds a bit.
18
SlickEdit 2018 v23 Beta Discussion / Re: Very weird hang
« Last post by Dennis on August 20, 2018, 05:38:57 pm »
Did you try interrupting the interpreter?  In CUA mode, the key combination is Ctrl+Alt+Shift+F2  (Halt Slick-C macro that is executing. Use this to terminate infinite loops).  Look in the Emulations tables in the Help to find what it key combination to use in your emulation/platform.  Sometimes you need to hold these keys down for a while before the break is caught by the interpreter.
19
SlickEdit 2018 v23 Beta Discussion / Re: Minimap zoom-out limit
« Last post by Tim Kemp on August 20, 2018, 05:21:01 pm »
On my Windows machine, the code font I'm using is 8 pixels high. The minimap lines are 3 pixels high. The minimap does show a little more than twice as many lines as my actual code window, but it could show 8 times as many lines if it used graphics instead of a font. I'll bet the rendering would be a lot faster too.
20
SlickEdit 2018 v23 Beta Discussion / Re: Extent of Java 10 support in SE 23 beta
« Last post by Dennis on August 20, 2018, 05:19:56 pm »
v22 added suppport for Java modules (.jmod) to support Java 9.  The suppport only applies to tagging and code-completion.  They are treated a lot like Jar files in that respect.

Local Variable Type Inference is something I will look at for a future v23 beta.  We have done type inference for several languages now, so this should be easy to add.  I will also have to look at what other language changes Oracle has made for Java 10.  Clearly supporting type inference would be the most important item, long overdue for Java to add this.  Slick-C has had it for years and years.
Pages: 1 [2] 3 4 ... 10